Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Deterministic MiniMindsLab utilities for AI agents over MCP.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using MiniMindsLab MCP Tools
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http minimindslab-mcp-tools https://mcp.minimindslab.com/mcpCapabilities
Teams need to know when a code change silently breaks accessible names, labels, or descriptions on interactive elements.
DiscoveredDevelopers need to know whether a new API contract breaks existing clients before they merge or publish it.
DiscoveredBackend and frontend teams need to confirm that paginated API response samples keep page, offset, and cursor behavior consistent across endpoints and edge cases.
DiscoveredEstimates whether a name badge is readable at social distance and flags text that will likely feel too small or too crowded.
DiscoveredUI developers need to know why an element is behind another element, clipped unexpectedly, or trapped inside a stacking context.
DiscoveredFrontend developers need to understand why an element is visually hidden behind another even when z-index seems correct.
DiscoveredDevelopers need to catch duplicate IDs and broken ARIA relationships that silently break accessibility and scripting.
DiscoveredDevelopers need to confirm that a sample API response still matches a contract, including required fields, type expectations, enum constraints, and unexpected shape changes.
DiscoveredAPI and frontend engineers need to know whether a JSON schema change will break real payloads, generated clients, or form bindings before they ship it.
DiscoveredAPI builders need to see exactly where a sample payload violates a schema or where the schema does not describe real data.
DiscoveredFrontend 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.
DiscoveredTeams need to reconcile two spreadsheet versions and see what changed, what conflicts, and which rows or columns need manual review.
DiscoveredDevelopers need to verify that webhook events preserve required fields, nesting, and array shapes across example payloads before wiring integrations.
DiscoveredAPI developers need to reproduce how a webhook provider canonicalizes headers and payloads when a signature mismatch occurs.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 274 ms | 14 |