Registry Lag — how fast MCP directories reflect a new server

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
65%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~116Tokens (tool definitions)
~239 BTypical response size
Minimal attention impact (0.09% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://registry-lag.rowb.app/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢check_directory_lag(name)

Check whether an MCP server name is listed in public MCP directories right now, and how long until it appeared (reflection lag).

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "description": "server name fragment, 3-64 chars"
    }
  },
  "required": [
    "name"
  ]
}
🟢get_report

Names checked so far with run counts and first/last seen timestamps.

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools