MiniMindsLab MCP Tools

Reviewed 43m ago.

• tools: 10 tools scanned
• metadata: scanned

No findings.

Tools (10)

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

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