mcp-registry/ai.corduroy-labs/updates · v1.28.1
As of 2026-10-26 18:46 UTC, the Corduroy Labs Updates MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
Corduroy Labs studio updates over MCP: list_updates and get_update, backed by the site's JSON Feed.
Point your MCP client at this streamable-http endpoint: https://corduroy-labs.ai/mcp
2 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 →
2 of 2 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.corduroy-labs%2Fupdates/fixes
{
"name": "get_update",
"description": "Fetch one Corduroy Labs update in full by its slug.\n\n Args:\n slug: the update's slug (e.g. \"the-studio-machine-readable\").\n Obtain slugs from list_updates().\n\n Returns:\n A dict with slug, title, url, date_published, summary,\n content_html, and optionally tags, location, image.\n ",
"inputSchema": {
"type": "object",
"title": "get_updateArguments",
"required": [
"slug"
],
"properties": {
"slug": {
"type": "string",
"title": "Slug"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "list_updates",
"description": "List Corduroy Labs blog updates, newest first.\n\n Args:\n limit: optional maximum number of items to return.\n\n Returns:\n A list of update summaries with: slug, title, url,\n date_published, summary, and optionally tags, location, image.\n ",
"inputSchema": {
"type": "object",
"title": "list_updatesArguments",
"properties": {
"limit": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"title": "Limit",
"default": null
}
}
},
"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/ai.corduroy-labs/updates"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/ai.corduroy-labs/updates"}) over MCP.
get_update ~141 tokenslist_updates ~133 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%2Fai.corduroy-labs%2Fupdates?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fai.corduroy-labs%2Fupdates?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.corduroy-labs%2Fupdates.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.corduroy-labs%2Fupdates.svg :target: https://glimind.com/server/mcp-registry%2Fai.corduroy-labs%2Fupdates?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:fbbddfea8b093497…, first seen 2026-10-17, included at leaf 3919 of 74,822. Version history · verify what your client received.
Compare: 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-26 18:46 UTC, the Corduroy Labs Updates MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 6 minutes.
Corduroy Labs Updates MCP server advertises 2 tools, including get_update, list_updates.
Point your MCP client at this streamable-http endpoint: https://corduroy-labs.ai/mcp
Glimind scanned all 2 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.