# MiniMindsLab MCP Tools

> Deterministic MiniMindsLab utilities for AI agents over MCP.

- name: com.minimindslab.mcp/tools
- version: 2026.10.17082813809
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 89/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.minimindslab.mcp%2Ftools
- tools: https://api.protogrid.dev/v1/servers/com.minimindslab.mcp%2Ftools/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "tools": {
      "type": "http",
      "url": "https://mcp.minimindslab.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 97
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-94% +updated-3d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 11 of 11 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: html-duplicate-id-and-aria-reference-checker (destructiveHint); json-contract-compatibility-checker (destructiveHint); json-schema-drift-impact-checker (destructiveHint); …
- pass `tools.token_cost`: about 4,001 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 3 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 11, about 4,001 tokens to load them all
- tool set hash: af0c8bf85a7d1d10865e0a582aa69fd1
- tools last changed: 2026-10-17T09:59:03.015Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.minimindslab.mcp/tools.svg)](https://protogrid.dev/servers/com.minimindslab.mcp/tools)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-17 `multipart-form-data-inspector` added
  - 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.
- 2026-10-03 `json-schema-drift-impact-checker` added
  - 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.
- 2026-09-27 `api-pagination-and-cursor-consistency-checker` added
  - Backend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.

Full history: https://api.protogrid.dev/v1/servers/com.minimindslab.mcp%2Ftools/changes

## Remotes

- https://mcp.minimindslab.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.93636364)

## Packages

_none_

## Tools (11)

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