MCP servercom.minimindslab.mcp/tools

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

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

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

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

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

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

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

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.

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

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