How websites treat AI agents: bot walls, JS needs, robots rules, llms.txt. Look up before you fetch.
Connect Remote server
claude mcp add --transport http registry https://onlinewebdirectory.net/mcp
{
"mcpServers": {
"registry": {
"url": "https://onlinewebdirectory.net/mcp"
}
}
}
{
"servers": {
"registry": {
"type": "http",
"url": "https://onlinewebdirectory.net/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://onlinewebdirectory.net/mcp
Tools 2 found in our last check
lookup_originBefore 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 de…
report_observationAfter 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 with POST https:…
Details
| Endpoint | https://onlinewebdirectory.net/mcp (Streamable HTTP) |
| First published | 16 Oct 2026 |
| Last updated | 16 Oct 2026 |
| Registry name | net.onlinewebdirectory/registry |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
