Desvela ARD Registry — free preflight(domain)
REMOTE · REGISTRY.DESVELA.DEV
What a domain publishes for AI agents: ai-catalog.json, llms.txt, agents.md, robots.txt rules. Free.
Available components
Last scanned (15 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 608 tokens (~152/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- 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.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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 →
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.
- 18 Nov 26 −1
- Tool “search” rewrote its description, which is the text the model reads security
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- 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
- Tool “crawler_block_test” rewrote its description, which is the text the model reads security
- 30 Sept 26 0
- Tool “preflight” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
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.desvela.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=registry.desvela.dev | CN=YE1,O=Let's Encrypt,C=US | 6 Nov 2026 | 4 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 5c7f44ca07fe5056f167ad4093ca04eabb2 |
| SANs: registry.desvela.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of registry.desvela.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| desvela.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://registry.desvela.dev/mcp | Verified | 200 | |
| http (plaintext) | http://registry.desvela.dev/mcp | HTTPS enforced | 308 | https://registry.desvela.dev/mcp |
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 →
crawler_block_test Test what a domain actually serves AI crawlers ~211
What the domain's CDN really does, as opposed to what its robots.txt says. Sends each AI crawler's real user-agent at the homepage and compares the response against a browser: a site can allow GPTBot in robots.txt and still have its CDN answer it a 403, and robots.txt cannot tell you that. Verdicts per crawler: ok, blocked (refused, or redirected off the site while the browser got the page), throttled (429, which is "too fast" and not "not you"), degraded (a 200 with a fraction of the bytes, the shape of a JS-gated page), or error. When `measurable` is false there is no verdict to give: the site refused or redirected away the control request too, or it opted out of our crawling (`optedOut`, no requests sent). Live probe, ~6 requests. Free. Use preflight for the declared policy; use this for the observed one.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
preflight Preflight a domain ~119
What a domain publishes for AI agents before you touch it: ai-catalog.json (ARD), llms.txt, agents.md, and its robots.txt directives for AI bots (GPTBot, ClaudeBot, Google-Extended…). Includes a visibility receipt: surface-by-surface state, the words that would find the domain in search (or the honest fact that none would), what is missing and where to publish it. Served from the Desvela ARD index when fresh (<7 days), live-checked otherwise. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
search Search the agent-readable web ~150
Natural-language search over what Desvela has indexed: agents, MCP servers, registries — the same index as POST /search. Returns catalog entries per the ARD spec. When nothing matches, returns referrals (other ARD-conformant registries you can query the same way) and listing (how a domain gets into this index: publish ai-catalog.json, then preflight it), instead of an empty answer. Any language works, but most entries are in English; an empty answer to a Chinese, Japanese, Korean or Thai query carries queryHint, because search matches whole words between spaces.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | natural-language query, e.g. "find an MCP server for weather data" |
No output schema declared.
No examples provided.
watch Watch a domain for agent-surface changes ~128
Subscribe to a domain: get a signed webhook (X-Desvela-Signature, HMAC-SHA256) when what it publishes for AI agents changes — ai-catalog.json entries added/changed/gone, llms.txt or agents.md edited or removed, robots.txt AI-bot directives changed. Checked weekly against the Desvela ARD index. Returns a manage_token (GET/DELETE https://registry.desvela.dev/watch/{id}) and the signing secret — store both.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| webhook_url | string | yes | HTTPS endpoint that will receive signed change notifications |
No output schema declared.
No examples provided.
How do I install the Desvela ARD Registry — free preflight(domain) MCP server?
Desvela ARD Registry — free preflight(domain) is a hosted endpoint at https://registry.desvela.dev/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.desvela.dev
claude mcp add --transport http dev-desvela-registry 'https://registry.desvela.dev/mcp'
What is the Desvela ARD Registry — free preflight(domain) MCP server?
Desvela ARD Registry — free preflight(domain) is an MCP server listed in the public MCP registry as dev.desvela/registry. What a domain publishes for AI agents: ai-catalog.json, llms.txt, agents.md, robots.txt rules. Free. This page covers its hosted endpoint (https://registry.desvela.dev/mcp).
Is the Desvela ARD Registry — free preflight(domain) MCP server safe to use?
Desvela ARD Registry — free preflight(domain) scores 75 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 Desvela ARD Registry — free preflight(domain) MCP server expose?
Desvela ARD Registry — free preflight(domain) exposes 4 tools: preflight, watch, crawler_block_test, search. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.
Does the Desvela ARD Registry — free preflight(domain) MCP server require authentication?
No. We connected to Desvela ARD Registry — free preflight(domain) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Desvela ARD Registry — free preflight(domain) MCP server still maintained?
Desvela ARD Registry — free preflight(domain) 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 Desvela ARD Registry — free preflight(domain) MCP server?
VerifyMCP ran 12 checks on Desvela ARD Registry — free preflight(domain), covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Desvela ARD Registry — free preflight(domain): Authorization. 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.