Registry Lag — how fast MCP directories reflect a new server MCP Server

by rowb-registry-lag Your server? Claim it

answering

Registry Lag — how fast MCP directories reflect a new server is answering right now. Last checked 11 min ago. It exposes 2 tools.

Checks whether an MCP server is listed in MCP directories right now, and how long the listing took.

Uptime history 15 days of history

15 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

620 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Registry Lag — how fast MCP directories reflect a new server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add reflection --transport http https://registry-lag.rowb.app/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "reflection": {
      "url": "https://registry-lag.rowb.app/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.reflection]
url = "https://registry-lag.rowb.app/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "reflection": {
      "url": "https://registry-lag.rowb.app/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "reflection": {
      "url": "https://registry-lag.rowb.app/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.

Endpoints

URL	Transport	State	Latency	Checked
https://registry-lag.rowb.app/mcp	streamable-http	answering	594 ms	11 min ago

Alternatives to Registry Lag — how fast MCP directories reflect a new server

same job, measured the same way

MCP health — MCP directory health check diagnostics

by rowb-mcp-health

Diagnoses whether an MCP server is reachable, by live HTTP probe.

2 tools answering

Agent Nexus

by agentnexus

Agent-native registry to discover APIs, MCP servers and CLIs, with live health checks.

6 tools answering

Erc8004 Agent Liveness

by nexus-mcp-infra

Checks whether an ERC-8004-registered agent is actually alive right now via a real MCP handshake

1 tools answering

New MCP Server Directory (Agent Tools Index)

by a2awire

MCP server index: newest agent tools listed. $0.01/query. Register in-session — free testnet funds.

16 tools answering

Preflight

by evanfollis

Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm.

1 tools answering

MCP Skills Server

by srprasanna

MCP server that loads and serves skills from a mounted directory with hot reload.

local only

MCP Skills Server

by srprasanna

MCP server that loads and serves skills from a mounted directory with hot reload.

local only

ManyCP MCP server

by dayyad

Submit an MCP server to many MCP directories and track each listing from an AI assistant

8 tools answering

Registry Lag — how fast MCP directories reflect a new server — questions

Answers built from our own checks of this server.

What can Registry Lag — how fast MCP directories reflect a new server do?

It exposes 2 tools, read directly from the server on our last check. Among them: check_directory_lag, get_report. 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 Registry Lag — how fast MCP directories reflect a new server 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 620 ms. The bar chart above shows every period we have measured.

How do I connect Registry Lag — how fast MCP directories reflect a new server?

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 Registry Lag — how fast MCP directories reflect a new server need an API key?

No. Registry Lag — how fast MCP directories reflect a new server 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 Registry Lag — how fast MCP directories reflect a new server?

It answers our handshake in 620 ms on average, which is faster than 18% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.