Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Registry Lag — how fast MCP directories reflect a new server

REMOTE · REGISTRY-LAG.ROWB.APP

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

0 this week 81 Trust /100

Last scanned (17 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security71
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 73 tokens (~36/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://registry-lag.rowb.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rowb.app CN=WE1,O=Google Trust Services,C=US 26 Sept 2026 25 Dec 2026 ECDSA 256 ECDSA-SHA256 3d59bc8fbab78817136f2f0725e06b95
SANs: rowb.app, registry-lag.rowb.app, *.registry-lag.rowb.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of registry-lag.rowb.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
rowb.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="registry-lag", resource_metadata="https://registry-lag.rowb.app/.well-known/oauth-protected-resource"

Bearer realm="registry-lag", resource_metadata="https://registry-lag.rowb.app/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://registry-lag.rowb.app/.well-known/oauth-protected-resource
Retrieved Yes
Problem Metadata incomplete
Resource https://registry-lag.rowb.app/mcp

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://registry-lag.rowb.app/mcp Verified 200
http (plaintext) http://registry-lag.rowb.app/mcp Inconclusive 405
MCP tools · 2 exposed · ~73 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_directory_lag ~51

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

NameTypeReqDescription
namestringyesserver name fragment, 3-64 chars

No output schema declared.

No examples provided.

get_report ~22

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

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

Registry Lag — how fast MCP directories reflect a new server is a hosted endpoint at https://registry-lag.rowb.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · registry-lag.rowb.app

# add to Claude Code
claude mcp add --transport http app-rowb-registry-lag-reflection 'https://registry-lag.rowb.app/mcp'
Common questions

What is the Registry Lag — how fast MCP directories reflect a new server server?

Registry Lag — how fast MCP directories reflect a new server is listed in the public MCP registry as app.rowb.registry-lag/reflection. Checks whether an MCP server is listed in MCP directories right now, and how long the listing took. This page covers its hosted endpoint (https://registry-lag.rowb.app/mcp).

Is the Registry Lag — how fast MCP directories reflect a new server server safe to use?

Registry Lag — how fast MCP directories reflect a new server scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Registry Lag — how fast MCP directories reflect a new server server expose?

Registry Lag — how fast MCP directories reflect a new server exposes 2 tools: check_directory_lag, get_report. Their descriptions and schemas cost roughly 73 tokens of context every time the server is loaded.

Does the Registry Lag — how fast MCP directories reflect a new server server require authentication?

Yes. Registry Lag — how fast MCP directories reflect a new server asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Registry Lag — how fast MCP directories reflect a new server server still maintained?

Registry Lag — how fast MCP directories reflect a new server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Registry Lag — how fast MCP directories reflect a new server server?

VerifyMCP ran 12 checks on Registry Lag — how fast MCP directories reflect a new server, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Registry Lag — how fast MCP directories reflect a new server: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.