Registry Lag — how fast MCP directories reflect a new server

app.rowb.registry-lagPublished by registry-lag.rowb.appOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executable

Overview

AI-generated overview

Lets an assistant check whether an MCP server is listed in public MCP directories and how long the listing took.

What you can do
Two tools: check_directory_lag reports whether a given MCP server name is currently listed in public MCP directories and how long it took to appear (reflection lag); get_report lists the names checked so far with run counts and first and last seen timestamps. It is aimed at observing how quickly directories pick up new servers.
When to use it
Use it when you publish or update an MCP server and want to know whether public directories list it and how long that took. Also useful for periodically tracking several server names.
Requirements
A remote endpoint plus a Bearer API key in the Authorization header; a free key is obtained by signing up and has a monthly check limit.
Before you install
Requires an Authorization Bearer API key, which should be kept private. The free tier caps checks per month, so heavier use may need a paid plan.

Installation

In SourceWeft

  1. Open Registry Lag — how fast MCP directories reflect a new server in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.rowb.registry-lag%2Freflection/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "registry-lag-how-fast-directories-reflec": {
      "type": "http",
      "url": "https://registry-lag.rowb.app/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

2

check_directory_lag

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

Parametersnamerequired

get_report

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

Takes no parameters.

Version history

1
  1. v1.0.0LatestSep 27, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.