Categories › AI & Agents › Multi-agent, orchestration & workflows
Deterministic MiniMindsLab utilities for AI agents over MCP.
Remote server: your requests and data go to mcp.minimindslab.com. Claude Code: claude mcp add --transport http minimindslab-mcp-tools https://mcp.minimindslab.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
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 endpconference-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-and-paint-order-inspector — UI developers need to know why an element is behind another element, clipped unexpectedly, or trapped inside a stacking context.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 constrainjson-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 thjson-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, rspreadsheet-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-payload-shape-sanity-checker — Developers need to verify that webhook events preserve required fields, nesting, and array shapes across example payloads before wiring intewebhook-signature-canonicalization-inspector — API developers need to reproduce how a webhook provider canonicalizes headers and payloads when a signature mismatch occurs.Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.