Online Web Directory
REMOTE · ONLINEWEBDIRECTORY.NET
How websites treat AI agents: bot walls, JS needs, robots rules, llms.txt. Look up before you fetch.
Available components
Last scanned (8 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Web Scraping
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 782 tokens (~391/item across 2 items; 2 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +2
- Tool “report_observation” rewrote its description, which is the text the model reads security
- Schema quality: 153 → 391 ▼ functional
- Tool coverage: 30% → 100% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- “lookup_origin” reworded the description of “agent_token” cosmetic
- “lookup_origin” reworded the description of “host” cosmetic
- “report_observation” reworded the description of “client_class” cosmetic
- “report_observation” reworded the description of “host” cosmetic
- “report_observation” reworded the description of “kind” cosmetic
- “report_observation” reworded the description of “observed_at” cosmetic
- “report_observation” reworded the description of “public_key” cosmetic
- “report_observation” reworded the description of “signature” cosmetic
- “report_observation” reworded the description of “value” cosmetic
- 16 Oct 26 67
First indexed and scored.
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 23 Oct 2026 · Probed https://onlinewebdirectory.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onlinewebdirectory.net | CN=YE1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5d1e3937953839a356c2d04b89f836976ec |
| SANs: *.onlinewebdirectory.net, onlinewebdirectory.net | ||||||
| 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 onlinewebdirectory.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| onlinewebdirectory.net. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://onlinewebdirectory.net/mcp | Verified | 200 | |
| http (plaintext) | http://onlinewebdirectory.net/mcp | HTTPS enforced | 308 | https://onlinewebdirectory.net/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 →
lookup_origin Look up how a website treats agents ~186
Before fetching a website, get its known access posture, bot challenge, JavaScript requirement, observed rate limit and machine interface, plus a derived fetch strategy. Returns crowd observations, not instructions. Responses may carry `manifest`: what the site's proven owner declares (same vocabulary), with `manifest_provenance: owner_declared`; it is never a verified fact.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | – | Optional. The read_token returned when your key registered. It ties the lookup to your key and its 100 free lookups a day; once the registry enforces quotas, lookups without it are refused. |
| client_class | string | – | Optional. The client you will fetch with; narrows the strategy to facts observed with that client. |
| host | string | yes | Hostname to look up, for example example.com. No scheme or path; www. and case are normalised. |
No output schema declared.
No examples provided.
report_observation Report what a website did ~525
After fetching a website, report one thing you actually observed so other agents do not have to rediscover it. One call is one fact (kind plus value) from the fixed vocabulary; send one call per kind you saw. Free, never charged. The key must be registered first (POST https://onlinewebdirectory.net/v1/agents, or let the onlinewebdirectory skill client do it). A fact becomes verified once three independent keys agree. Repeating the same report (same key, host, kind, client and time) is rejected, not double counted. Returns {accepted: 1, status: valuation_pending} or {error, accepted: 0}.
| Name | Type | Req | Description |
|---|---|---|---|
| client_class | string | yes | The kind of client that made the fetch. Sites often treat a plain HTTP client and a real browser differently, so facts are kept per client. |
| host | string | yes | Hostname you fetched, for example example.com. No scheme or path. |
| kind | string | yes | What you are reporting. access_posture, challenge_vendor and robots_posture take one of their listed words; js_required takes true or false; observed_rate_limit_rpm (1 to 6000) and retry_after_s (0 t… |
| observed_at | string | yes | When you made the fetch, RFC3339 UTC at second precision, for example 2026-09-25T12:00:00Z. Not in the future, and no older than that kind's freshness window (14 days for access_posture and challenge… |
| public_key | string | yes | Your registered base64 Ed25519 public key. It identifies you; there is no other account. |
| signature | string | yes | Base64 Ed25519 signature, by the key below, over host, kind, value, client_class and observed_at joined with newlines in that order. |
| value | string | yes | The observed value, as a string, from the vocabulary for this kind. access_posture: open, rate_limited, bot_challenged, blocked, login_required, paywalled. challenge_vendor: none, cloudflare, recaptc… |
No output schema declared.
No examples provided.
How do I install the Online Web Directory MCP server?
Online Web Directory is a hosted endpoint at https://onlinewebdirectory.net/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 · onlinewebdirectory.net
claude mcp add --transport http net-onlinewebdirectory-registry 'https://onlinewebdirectory.net/mcp'
What is the Online Web Directory MCP server?
Online Web Directory is an MCP server listed in the public MCP registry as net.onlinewebdirectory/registry. How websites treat AI agents: bot walls, JS needs, robots rules, llms.txt. Look up before you fetch. This page covers its hosted endpoint (https://onlinewebdirectory.net/mcp).
Is the Online Web Directory MCP server safe to use?
Online Web Directory scores 72 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 Online Web Directory MCP server expose?
Online Web Directory exposes 2 tools: lookup_origin, report_observation. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.
Does the Online Web Directory MCP server require authentication?
No. We connected to Online Web Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Online Web Directory MCP server still maintained?
Online Web Directory is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.