MiniMindsLab MCP server

• Registry namecom.minimindslab.mcp/toolsverified in the MCP registry

The registry name sits under minimindslab.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-21
• Tools11
• Server calls itselfminimindslab-tools
• Server version0.3.0
• Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 647 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer626 ms
• Space in an agent's context≈ 3,947 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results11 of 11 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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.