MiniMindsLab MCP Tools

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Deterministic MiniMindsLab utilities for AI agents over MCP.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "MiniMindsLab MCP Tools": {
      "url": "https://mcp.minimindslab.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (12)

• accessible-name-and-label-regression-diff read-only

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

  Parameters:

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

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• api-breaking-change-diff-viewer read-only

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

  Parameters:

  • old_contract_json (required) — string — 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 (required) — string — 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 (required) — boolean — 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 more prominently.
  • show_path_details (required) — boolean — 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 (required) — boolean — 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.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• api-pagination-and-cursor-consistency-checker read-only

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

  Parameters:

  • response_samples (required) — string — 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 (required) — string — 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 — 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 — Optional. If provided, must be a positive integer. Used to verify per-page item counts and boundary transitions.
  • show_item_paths — boolean — When true, output item path references for duplicates, gaps, and boundary findings when they can be inferred from the samples.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• conference-badge-readability-tester read-only

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

  Parameters:

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

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• css-stacking-context-inspector read-only

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

  Parameters:

  • css_snippet (required) — string — 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 (required) — string — 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 (required) — string — 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 (required) — boolean — 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 (required) — boolean — Boolean flag. When true, include the ancestry of stacking context creators from root to selected element. When false, include only the summarized cause.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• html-duplicate-id-and-aria-reference-checker read-only

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

  Parameters:

  • html_snippet (required) — string — 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 (required) — boolean — 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 (required) — boolean — 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 (required) — boolean — 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.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• json-contract-compatibility-checker read-only

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

  Parameters:

  • contract_json (required) — string — 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. Missing or invalid JSON must produce a parse error.
  • sample_json (required) — string — 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 (required) — boolean — 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 (required) — boolean — 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 still listed in extra_paths but do not change overall compatibility unless another required rule fails.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• json-schema-drift-impact-checker read-only

  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.

  Parameters:

  • old_json_schema (required) — string — 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 (required) — string — 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.
  • show_path_details (required) — boolean — Boolean toggle. When true, path-level findings must include explicit JSON Pointer style paths and short evidence notes.
  • strict_mode (required) — boolean — 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.
  • sample_payloads — string — 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.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• json-schema-vs-sample-payload-diff-checker read-only

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

  Parameters:

  • json_schema (required) — string — Must be valid JSON text representing a JSON Schema document. If parsing fails, show a schema parse error and skip comparison.
  • sample_json (required) — string — Must be valid JSON text representing an instance payload. If parsing fails, show a sample parse error and skip comparison.
  • additional_properties_mode (required) — string — 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 extra-property violations. forbid reports extra-property paths even if the schema is permissive.
  • strict_types (required) — boolean — 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 Schema-compatible numeric coercion is not performed; comparison remains type-based but integer and number mismatches are reported with lower severity in the summary only.
  • show_paths (required) — boolean — When true, include JSON Pointer-style instance paths for every mismatch. When false, still compute paths internally but present concise grouped results.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• multipart-form-data-inspector read-only

  Frontend and API developers need to see exactly what a browser will send as multipart form data, because hidden controls, disabled fields, repeated names, and file inputs often create payload mismatches.

  Parameters:

  • html_form_snippet (required) — string — Must contain a single HTML <form> snippet or a fragment that includes one form element. Empty input is invalid. The tool must parse markup locally only.
  • control_state_overrides (required) — string — Must be valid JSON text describing per-control state overrides such as value, checked, selected, disabled, or files. If empty, treat as an empty object. Invalid JSON must produce a parse error state and no preview.
  • expected_field_list (required) — string — Must be a newline-separated or comma-separated list of expected field names, or an empty string. Names are compared case-sensitively and after trimming surrounding whitespace.
  • selected_submitter (required) — string — Must be a submit control identifier such as a control name, id, or CSS-like path token understood by the parser, or an empty string to indicate no explicit submitter. If the selector matches multiple submitters, this is an error.
  • submission_mode (required) — string — Must be one of the supported deterministic modes. multipart/form-data computes browser-like multipart serialization metadata and field ordering; form-data-preview-only suppresses boundary rendering while preserving field ordering and inclusion rules.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• spreadsheet-merge-conflict-reconciler read-only

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

  Parameters:

  • sheet_a (required) — string — 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 (required) — string — 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 (required) — string — 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 (required) — boolean — When false, row key matching and field comparisons ignore letter case. When true, comparisons preserve letter case exactly.
  • trim_whitespace (required) — boolean — When true, leading and trailing whitespace is removed from headers, keys, and cell values before matching and comparison. Internal spaces are preserved.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• webhook-signature-canonicalization-inspector read-only

  API developers need to reproduce how a webhook provider canonicalizes headers and payloads when a signature mismatch occurs.

  Parameters:

  • headers_text (required) — string — Accept raw HTTP header lines in plain text. Each non-empty line should be in the form Name: value. Leading and trailing whitespace around names and values is trimmed during parsing. Duplicate header names are allowed and are preserved in input order for canonicalization. If empty, the tool must return an input error state.
  • body_text (required) — string — Accept the exact request body as plain text. Preserve all characters exactly as entered, including line breaks and trailing whitespace, before applying the selected signing rule mode. If empty, the body is treated as an empty string, not missing.
  • secret_or_shared_key (required) — string — Accept the webhook signing secret or shared key as text. The tool must not mask, store, transmit, or auto-save it. Empty input is invalid.
  • signing_rule_mode (required) — string — Select one deterministic signing rule mode. The tool must apply the chosen rule exactly and must not infer undocumented provider-specific behavior outside the selected mode.
  • timestamp_tolerance (required) — number — Enter a non-negative whole number of seconds. Used only when the selected signing rule mode requires timestamp verification. Values above 86400 are invalid. A tolerance of 0 means only exact timestamp matches are considered valid.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.