mcpbeat

Updates MCP Server

ai.corduroy-labs/updates
answering

Updates is answering right now. Last checked 2 min ago. It exposes 2 tools.

Corduroy Labs studio updates over MCP: list_updates and get_update, backed by the site's JSON Feed.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
423 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add updates --transport http https://corduroy-labs.ai/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "updates": {
      "url": "https://corduroy-labs.ai/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.updates]
url = "https://corduroy-labs.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "updates": {
      "url": "https://corduroy-labs.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "updates": {
      "url": "https://corduroy-labs.ai/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

get
get_update
Fetch one Corduroy Labs update in full by its slug. Args: slug: the update's slug (e.g. "the-studio-machine-readable"). Obtain slugs from list_updates(). Returns: A dict with slug, title, url, date_published, summary, content_html, and optionally tags, location, image.
updates
list_updates
List Corduroy Labs blog updates, newest first. Args: limit: optional maximum number of items to return. Returns: A list of update summaries with: slug, title, url, date_published, summary, and optionally tags, location, image.

Endpoints

URLTransportStateLatencyChecked
https://corduroy-labs.ai/mcp streamable-http answering 403 ms 2 min ago

Updates — questions

Answers built from our own checks of this server.

What can Updates do?
It exposes 2 tools, read directly from the server on our last check. Among them: get_update, list_updates. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Updates working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 423 ms. The bar chart above shows every period we have measured.
How do I connect Updates?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Updates need an API key?
No. Updates completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Updates?
It answers our handshake in 423 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.