# Online Web Directory (remote · onlinewebdirectory.net)

How websites treat AI agents: bot walls, JS needs, robots rules, llms.txt. Look up before you fetch.

- Trust score: 72/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `onlinewebdirectory.net`: 72/100 (this document), [markdown](https://verifymcp.io/servers/net-onlinewebdirectory-registry/onlinewebdirectory.md), [page](https://verifymcp.io/servers/net-onlinewebdirectory-registry/onlinewebdirectory)

## Channel facts

- Endpoint: `https://onlinewebdirectory.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http net-onlinewebdirectory-registry 'https://onlinewebdirectory.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-onlinewebdirectory-registry": {
      "url": "https://onlinewebdirectory.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-onlinewebdirectory-registry": {
      "type": "http",
      "url": "https://onlinewebdirectory.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-onlinewebdirectory-registry]
url = "https://onlinewebdirectory.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-onlinewebdirectory-registry": {
      "type": "remote",
      "url": "https://onlinewebdirectory.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-onlinewebdirectory-registry --url 'https://onlinewebdirectory.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-onlinewebdirectory-registry:
    url: "https://onlinewebdirectory.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-onlinewebdirectory-registry": {
      "Transport": "http",
      "Url": "https://onlinewebdirectory.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-onlinewebdirectory-registry -t streamable-http -u 'https://onlinewebdirectory.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-onlinewebdirectory-registry": {
      "type": "http",
      "url": "https://onlinewebdirectory.net/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 72, +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.

### 2026-10-21 (score 71, +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.

### 2026-10-19 (score 70, +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.

### 2026-10-17 (score 69, +2)

- [security] Tool “report_observation” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 153 → 391
- [functional improvement] Tool coverage: 30% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: fair → good
- [cosmetic] “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”

### 2026-10-16 (score 67)

First indexed and scored.

## MCP tools (2)

### `lookup_origin` (~186 tokens)

Look up how a website treats agents

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.

Input parameters:

- `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, required): Hostname to look up, for example example.com. No scheme or path; www. and case are normalised.

### `report_observation` (~525 tokens)

Report what a website did

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}.

Input parameters:

- `client_class` (string, required): 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, required): Hostname you fetched, for example example.com. No scheme or path.
- `kind` (string, required): 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, required): 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, required): Your registered base64 Ed25519 public key. It identifies you; there is no other account.
- `signature` (string, required): Base64 Ed25519 signature, by the key below, over host, kind, value, client_class and observed_at joined with newlines in that order.
- `value` (string, required): 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-onlinewebdirectory-registry/onlinewebdirectory#diagnostics

## Score history

- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://onlinewebdirectory.net/mcp
- Website: https://onlinewebdirectory.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-onlinewebdirectory-registry/onlinewebdirectory.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-onlinewebdirectory-registry/onlinewebdirectory.json
- HTML version of this page: https://verifymcp.io/servers/net-onlinewebdirectory-registry/onlinewebdirectory