NestDaddy

Online Web Directory

net.onlinewebdirectory/registry · v1.1.0

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

Connect Remote server

Terminal
claude mcp add --transport http registry https://onlinewebdirectory.net/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "registry": {
      "url": "https://onlinewebdirectory.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "registry": {
      "type": "http",
      "url": "https://onlinewebdirectory.net/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://onlinewebdirectory.net/mcp

Tools 2 found in our last check

  • lookup_origin

    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 de…

  • report_observation

    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 with POST https:…

Details

Endpointhttps://onlinewebdirectory.net/mcp (Streamable HTTP)
First published16 Oct 2026
Last updated16 Oct 2026
Registry namenet.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.