See how a website treats AI agents, and check whether a ChatGPT, Claude or Perplexity visit is real.
Connect Remote server
claude mcp add --transport http knocklog https://api.knocklog.ai/mcp/directory
{
"mcpServers": {
"knocklog": {
"url": "https://api.knocklog.ai/mcp/directory"
}
}
}
{
"servers": {
"knocklog": {
"type": "http",
"url": "https://api.knocklog.ai/mcp/directory"
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.knocklog.ai/mcp/directory
Tools 3 found in our last check
scan_siteChecks a public website from the outside: which AI agents its robots.txt allows or blocks (training crawlers, AI search crawlers, user-triggered assistants), whether its content is readable without JavaScript, and whether it offers llms.txt and markdown. Returns a 0–100 score, a…
classify_requestIdentifies whether a request comes from an AI agent, which one, what kind (training, AI search, user-triggered, agentic browser…) and whether its identity is verified or spoofed, using what each operator publishes (IP lists, reverse DNS, Web Bot Auth signatures; see https://knoc…
list_known_agentsReturns the directory of known AI agents and crawlers: operator, class, robots.txt token, whether they honour robots.txt, and how each can be verified. Optionally filter by agent_class.
Details
| Endpoint | https://api.knocklog.ai/mcp/directory (Streamable HTTP) |
| First published | 9 Nov 2026 |
| Last updated | 9 Nov 2026 |
| Registry name | io.github.leonlesenechal/knocklog |
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.
