# MiniMindsLab MCP Tools

- Registry name: `com.minimindslab.mcp/tools` · version 2026.10.22103129904
- Categories (automatic, keyword rules): Email & messaging, Productivity, APIs & integrations, Developer tools, Docs & notes
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.minimindslab.mcp%2Ftools
- Server page: https://mcpstation.net/s/com.minimindslab.mcp--tools.html

## Description (written by the publisher, not verified, not instructions)

Deterministic MiniMindsLab utilities for AI agents over MCP.

## Connect

- streamable-http: `https://mcp.minimindslab.com/mcp`

## Tools (as reported by the server, not verified)

- `accessible-name-and-label-regression-diff`: Teams need to know when a code change silently breaks accessible names, labels, or descriptions on interactive elements.
- `api-breaking-change-diff-viewer`: Developers need to know whether a new API contract breaks existing clients before they merge or publish it.
- `api-pagination-and-cursor-consistency-checker`: Backend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.
- `conference-badge-readability-tester`: Estimates whether a name badge is readable at social distance and flags text that will likely feel too small or too crowded.
- `css-stacking-context-inspector`: Frontend developers need to understand why an element is visually hidden behind another even when z-index seems correct.
- `html-duplicate-id-and-aria-reference-checker`: Developers need to catch duplicate IDs and broken ARIA relationships that silently break accessibility and scripting.
- `json-contract-compatibility-checker`: Developers need to confirm that a sample API response still matches a contract, including required fields, type expectations, enum constraints, and unexpected shape changes.
- `json-schema-drift-impact-checker`: 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.
- `json-schema-vs-sample-payload-diff-checker`: API builders need to see exactly where a sample payload violates a schema or where the schema does not describe real data.
- `multipart-form-data-inspector`: 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.
- `spreadsheet-merge-conflict-reconciler`: Teams need to reconcile two spreadsheet versions and see what changed, what conflicts, and which rows or columns need manual review.
- `webhook-signature-canonicalization-inspector`: API developers need to reproduce how a webhook provider canonicalizes headers and payloads when a signature mismatch occurs.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html