mcp-registry/so.coreloop/directory · v1.2.1
Verdict. Coreloop Directory MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 40% of MCP servers, with 1811 ms median handshake and 1 outage in 90 days. Its agent-readiness grade is A (93/100) across 7 tools, costing an agent about 3,183 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 40% of MCP servers |
| Median handshake latency | 1811 ms | 7% of MCP servers |
| p95 handshake latency | 4195 ms | — |
| Checks in 30 days | 4,947 | — |
| Outages, 90 days | 1 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 93/100 (A) | 76% of MCP servers |
| Tools | 7 | — |
| Tool-list size for an agent | ~3,183 tokens | 45% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 23:15 UTC, the Coreloop Directory MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Search real businesses, then read profiles, services and hours or contact them, in one endpoint.
Claude Code
claude mcp add --transport http coreloop-directory-mcp-server https://coreloop.so/api/mcp/coreloop-directory
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"coreloop-directory-mcp-server": {
"type": "http",
"url": "https://coreloop.so/api/mcp/coreloop-directory"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~1,811 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/so.coreloop/directory"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/so.coreloop/directory"}) over MCP.
search_businesses ~816 tokensget_business_services ~766 tokenscompare_business_services ~378 tokenssend_business_inquiry ~376 tokenscheck_business_availability ~313 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fso.coreloop%2Fdirectory?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fso.coreloop%2Fdirectory?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fso.coreloop%2Fdirectory.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fso.coreloop%2Fdirectory.svg :target: https://glimind.com/server/mcp-registry%2Fso.coreloop%2Fdirectory?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a85cf4e32304fff3…, first seen 2026-10-17, included at leaf 12042 of 76,030. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 23:15 UTC, the Coreloop Directory MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.
Coreloop Directory MCP server advertises 7 tools, including check_business_availability, compare_business_services, get_business_agent, get_business_info, get_business_services.
Point your MCP client at this streamable-http endpoint: https://coreloop.so/api/mcp/coreloop-directory
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.