Name: MiniMindsLab MCP Tools
Author: minimindslab

MiniMindsLab MCP Tools

Deterministic MiniMindsLab utilities for AI agents over MCP.

not scanned Remote · Streamable HTTP No auth needed 10 tools v2026.10.3082654087

No reviews yet by minimindslab The publisher’s own endpoint — this marketplace is not in the path

tools declared

—

trust score

remote

at its publisher

—

calls last 7d

What it does

Deterministic MiniMindsLab utilities for AI agents over MCP.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http minimindslab-mcp-tools https://mcp.minimindslab.com/mcp

# 2 — ask your agent for something these tools do
#   accessible-name-and-label-regression-diff, api-breaking-change-diff-viewer, api-pagination-and-cursor-consistency-checker and 7 more

MiniMindsLab MCP Tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

minimindslab1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Teams need to know when a code change silently breaks accessible names, labels, or descriptions on interactive elements.

Parameter	Type	Required	Notes
old_dom_snippet	string	yes	Required. Must contain a non-empty HTML or DOM fragment. Plain text is treated as literal markup input, not rendered content.
new_dom_snippet	string	yes	Required. Must contain a non-empty HTML or DOM fragment. Plain text is treated as literal markup input, not rendered content.
include_description	boolean	yes	When true, compare accessible descriptions in addition to accessible names and labels.
match_by_selector	boolean	yes	When true, element matching prefers stable CSS-like selector identity when available; otherwise fallback matching is used.
show_element_paths	boolean	yes	When true, output includes deterministic element path strings for matched and problematic nodes.

Developers need to know whether a new API contract breaks existing clients before they merge or publish it.

Parameter	Type	Required	Notes
old_contract_json	string	yes	Must be valid JSON text representing the previous contract version. The tool must reject empty input and invalid JSON with a parse error.
new_contract_json	string	yes	Must be valid JSON text representing the proposed contract version. The tool must reject empty input and invalid JSON with a parse error.
strict_mode	boolean	yes	When true, treat type changes, removed required fields, removed paths, enum narrowing, and object-to-non-object changes as breaking. When false, still report them but additive changes may be separated
show_path_details	boolean	yes	When true, include full normalized JSON paths for every finding. When false, keep messages concise while preserving path references in structured results.
ignore_additive_changes	boolean	yes	When true, do not include new optional fields, new array members in additive-only contexts, or other non-breaking additions in the visible change lists.

Backend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.

Parameter	Type	Required	Notes
response_samples	string	yes	Must contain one or more API response samples in JSON text form. Each sample must parse as an object or array. Empty input is invalid.
pagination_mode	string	yes	Select the intended pagination contract. 'mixed' means samples may contain more than one pagination style and the checker will verify consistency within each style.
sort_key	string	no	Optional. If provided, must be a non-empty field path such as 'created_at' or 'data.items[].id'. Used as the expected stable ordering key across samples.
page_size	number	no	Optional. If provided, must be a positive integer. Used to verify per-page item counts and boundary transitions.
show_item_paths	boolean	no	When true, output item path references for duplicates, gaps, and boundary findings when they can be inferred from the samples.

Estimates whether a name badge is readable at social distance and flags text that will likely feel too small or too crowded.

Parameter	Type	Required	Notes
badge_width_mm	number	yes	Must be a finite number between 20 and 300. Values outside the range are invalid.
company_text	string	yes	Text is required. Leading and trailing whitespace are trimmed. Empty after trimming is invalid.
font_size_pt	number	yes	Must be a finite number between 6 and 72. Non-numeric or out-of-range values are invalid.
name_text	string	yes	Text is required. Leading and trailing whitespace are trimmed. Empty after trimming is invalid.
role_text	string	no	Optional text. If provided, it is trimmed. Empty string is treated as blank.
viewing_distance_cm	number	yes	Must be a finite number between 20 and 500. Values outside the range are invalid.

Frontend developers need to understand why an element is visually hidden behind another even when z-index seems correct.

Parameter	Type	Required	Notes
css_snippet	string	yes	Required. Must contain one or more CSS rules. Trim leading and trailing whitespace. If empty, show a validation error and do not compute results.
html_snippet	string	yes	Required. Must contain HTML markup for the inspected layout. Trim leading and trailing whitespace. If empty, show a validation error and do not compute results.
selected_element	string	yes	Required. Must be a CSS selector or element reference token that matches at least one element in the provided HTML snippet. If no match is found, return a selection error.
show_paint_order	boolean	yes	Boolean flag. When true, include a paint order trace. When false, omit the detailed trace but still compute the main layering explanation.
show_stacking_context_chain	boolean	yes	Boolean flag. When true, include the ancestry of stacking context creators from root to selected element. When false, include only the summarized cause.

Developers need to catch duplicate IDs and broken ARIA relationships that silently break accessibility and scripting.

Parameter	Type	Required	Notes
html_snippet	string	yes	Accept raw HTML or DOM snippet text. Must be non-empty after trimming. Parse as HTML fragment in document order. Script execution is never allowed.
check_duplicate_ids	boolean	yes	When true, report every duplicated id value with all matching element locations. When false, duplicate-id analysis is skipped and duplicate outputs are empty.
check_aria_references	boolean	yes	When true, scan ARIA ID reference attributes and validate each referenced id against the parsed fragment. When false, aria-reference analysis is skipped and broken-reference outputs are empty.
show_element_paths	boolean	yes	When true, include stable element paths for duplicate and broken-reference findings. When false, path fields are omitted from per-finding detail but summary counts still compute.

Developers need to confirm that a sample API response still matches a contract, including required fields, type expectations, enum constraints, and unexpected shape changes.

Parameter	Type	Required	Notes
contract_json	string	yes	Must be valid JSON text. The contract must be an object. Supported contract keys are name/title, type, required, properties, items, enum, const, additionalProperties, and nested combinations of those.
sample_json	string	yes	Must be valid JSON text. The sample must be a JSON object, array, string, number, boolean, or null. Missing or invalid JSON must produce a parse error.
show_path_details	boolean	yes	When true, mismatch outputs must include explicit JSONPath-like paths such as $.user.name. When false, the report may summarize issues without omitting the required output lists.
strict_mode	boolean	yes	When true, extra paths not allowed by the contract are reported as mismatches whenever additionalProperties is false or omitted for object branches that define properties. When false, extra paths are

API and frontend engineers need to know whether a JSON schema change will break real payloads, generated clients, or form bindings before they ship it.

Parameter	Type	Required	Notes
old_json_schema	string	yes	Must be valid JSON text representing the previous schema version. The schema must parse as an object; if parsing fails, show a parse error and stop comparison.
new_json_schema	string	yes	Must be valid JSON text representing the proposed schema version. The schema must parse as an object; if parsing fails, show a parse error and stop comparison.
sample_payloads	string	no	Optional JSON text. Accept a single JSON value, an array of JSON values, or newline-separated JSON values. Blank input means no sample payload analysis.
show_path_details	boolean	yes	Boolean toggle. When true, path-level findings must include explicit JSON Pointer style paths and short evidence notes.
strict_mode	boolean	yes	Boolean toggle. When true, treat any added required constraint, narrowed type, removed enum option, reduced allowed array/object shape, or newly forbidden property as breaking.

API builders need to see exactly where a sample payload violates a schema or where the schema does not describe real data.

Parameter	Type	Required	Notes
json_schema	string	yes	Must be valid JSON text representing a JSON Schema document. If parsing fails, show a schema parse error and skip comparison.
sample_json	string	yes	Must be valid JSON text representing an instance payload. If parsing fails, show a sample parse error and skip comparison.
additional_properties_mode	string	yes	Controls handling of object properties not declared by the schema. schema_default uses the schema's own additionalProperties / unevaluatedProperties rules where supported by the tool. allow ignores ex
strict_types	boolean	yes	When true, require exact JSON type matches for object, array, string, number, integer, boolean, and null. Integers must still be numbers with no fractional component. When false, permit only JSON Sche
show_paths	boolean	yes	When true, include JSON Pointer-style instance paths for every mismatch. When false, still compute paths internally but present concise grouped results.

Teams need to reconcile two spreadsheet versions and see what changed, what conflicts, and which rows or columns need manual review.

Parameter	Type	Required	Notes
sheet_a	string	yes	Paste or upload the first sheet snapshot as tabular text. Accept CSV-style or TSV-style rows with a header row. Must contain at least one data row and one header row.
sheet_b	string	yes	Paste or upload the second sheet snapshot as tabular text. Accept CSV-style or TSV-style rows with a header row. Must contain at least one data row and one header row.
match_keys	string	yes	Provide one or more column names used to match rows between Sheet A and Sheet B. Separate multiple keys with commas, semicolons, or new lines. Each key must exist in both sheets after normalization.
case_sensitive	boolean	yes	When false, row key matching and field comparisons ignore letter case. When true, comparisons preserve letter case exactly.
trim_whitespace	boolean	yes	When true, leading and trailing whitespace is removed from headers, keys, and cell values before matching and comparison. Internal spaces are preserved.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install MiniMindsLab MCP Tools or to call it, at any volume.

Where are you running it?

Tool surface

Release history

MiniMindsLab MCP Tools

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

Release history

See also