Endpoints: 76,849MCP servers: 32,730Payout addresses: 3,825Paid calls: 6,157Letters: 84Defects: 3,894counted 2 min ago
teppi

Server definition

Hash
sha256:86354a34393e64df97835a00d2d49599113bca0edb531e8613881dcfcccc8923
What it is
What a remote MCP server returned when asked what it offers: 3 tools

The blob, as servednamed by its sha256

{ "instructions": "Knocklog: analytics for AI agents. Use scan_site on a website's domain to see how it treats AI agents (robots.txt rules for each agent, content readable without JavaScript, llms.txt, markdown) and what to fix. Use classify_request to identify one HTTP request (User-Agent, IP, URL, headers) and verify whether the agent is who it claims to be. Use list_known_agents for the directory of AI agents with operator, type, robots.txt token and how each one can be verified. To measure a site's real agent traffic over time, the site owner creates a free project at https://knocklog.ai.", "tools": [ { "description": "Identifies 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://knocklog.ai/agents). Pass the client IP, the full request URL and all request headers for the most complete check.", "inputSchema": { "additionalProperties": false, "properties": { "headers": { "additionalProperties": { "type": "string" }, "description": "Request headers", "type": "object" }, "ip": { "description": "Client IP as seen by the server", "type": "string" }, "method": { "description": "HTTP method of the request (default GET)", "type": "string" }, "url": { "description": "Full request URL", "type": "string" }, "user_agent": { "description": "The User-Agent header of the request, exactly as received", "type": "string" } }, "type": "object" }, "name": "classify_request", "outputSchema": null }, { "description": "Returns 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.", "inputSchema": { "additionalProperties": false, "properties": { "agent_class": { "description": "Only agents of this kind, e.g. training_crawler, ai_search_crawler or user_action_agent", "enum": [ "training_crawler", "ai_search_crawler", "user_action_agent", "agentic_browser", "coding_agent", "search_engine", "preview_fetcher", "ads_checker", "automation_client", "scraper" ], "type": "string" } }, "type": "object" }, "name": "list_known_agents", "outputSchema": null }, { "description": "Checks 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 grade and prioritised findings with recommendations. Takes a few seconds.", "inputSchema": { "additionalProperties": false, "properties": { "domain": { "description": "Domain or URL, e.g. example.com", "type": "string" } }, "required": [ "domain" ], "type": "object" }, "name": "scan_site", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:86354a34393e64df97835a00d2d49599113bca0edb531e8613881dcfcccc8923 | sha256sum