mcp-registry/com.curlship/directory · v1
As of 2026-10-27 02:37 UTC, the Curlship Directory MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
Read and submit the CurlShip directory. Paid actions return checkout_url.
Point your MCP client at this streamable-http endpoint: https://curlship.com/mcp
16 of 16 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
17 parameter(s) across 8 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 →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.curlship%2Fdirectory/fixes
{
"name": "change_listing_url",
"description": "Point an existing listing at a new URL. One listing per root domain, so this is how a second page replaces the first.",
"inputSchema": {
"type": "object",
"required": [
"listing_id",
"url",
"proof"
],
"properties": {
"url": {
"type": "string"
},
"proof": {
"enum": [
"email",
"domain"
],
"type": "string"
},
"listing_id": {
"type": "integer"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_daily_stats",
"description": "Active listings added per UTC day — the zero-filled series behind the public /stats page. One entry per calendar day from the first listing to today, each with added and the cumulative running total.",
"inputSchema": {
"type": "object",
"properties": {
"range": {
"type": [
"string",
"integer"
],
"description": "\"all\" (default) for the whole series, or a day count 1-3650 for the last N days."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_dr_history",
"description": "The site's Ahrefs Domain Rating over time — the series behind /stats#dr. Every recorded reading, one per UTC day, plus the current value, the last step (change vs the most recent different reading) and the growth since the first reading.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}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/com.curlship/directory"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.curlship/directory"}) over MCP.
list_listings ~291 tokensx402_submit_listing ~270 tokensx402_bid_featured ~252 tokensbid_featured ~140 tokenssubmit_listing ~134 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%2Fcom.curlship%2Fdirectory?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.curlship%2Fdirectory?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.curlship%2Fdirectory.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.curlship%2Fdirectory.svg :target: https://glimind.com/server/mcp-registry%2Fcom.curlship%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:8b2666b6776618fc…, first seen 2026-10-25, included at leaf 65319 of 76,865. Version history · verify what your client received.
Compare: most reliable other servers · most reliable analytics servers · most reliable data servers · most reliable knowledge servers · most reliable web 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-27 02:37 UTC, the Curlship Directory MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
Curlship Directory MCP server advertises 16 tools, including bid_featured, change_listing_url, confirm_edit, get_daily_stats, get_dr_history.
Point your MCP client at this streamable-http endpoint: https://curlship.com/mcp
Glimind scanned all 16 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.