Knocklog MCP server
io.github.leonlesenechal/knocklogleonlesenechalstreamable-httpv1.0.1Scanned
See how a website treats AI agents, and check whether a ChatGPT, Claude or Perplexity visit is real.
3 tools: 2 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Knocklog MCP server can do
The Knocklog MCP server is published by the GitHub account leonlesenechal. It has 3 tools. It can create or change data (2 tools: scan_site and classify_request), but cannot delete data. 1 tool only reads.
1 tool reads private data (list_known_agents); 2 tools bring in text other people can write (scan_site and classify_request); 1 tool can send data out of your system (classify_request). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
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, u…Reads text others writeCan send data out1 finding
Why it is in this group
- The name "classify_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "classify_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "classify_request" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Identify and verify one HTTP request
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
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…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Scan a site for AI-agent readiness
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
Only reads 1Show 1 read-only tool
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.Reads private dataNo findings
Why it is in this group
- The name "list_known_agents" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "directory": it reads files.
Description, as the server wrote it 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.
Annotations the server declares
- title: List known AI agents
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__knocklog__classify_request"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.knocklog.ai/.well-known/oauth-protected-resource
- Authorization servers
- https://api.knocklog.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.knocklog.ai/mcp/directory: tools/list returned 3 tools to an anonymous client, including scan_site (write), classify_request (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnclassify_request
The server marks "classify_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "classify_request" says "request": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:classify_requestChanges thingsinputSchema
- Changed:list_known_agentsOnly readsinputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http knocklog https://api.knocklog.ai/mcp/directoryclaude mcp add --transport http knocklog https://api.knocklog.ai/mcp/directoryRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__knocklog__list_known_agents"
],
"ask": [
"mcp__knocklog__scan_site",
"mcp__knocklog__classify_request"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as knocklog. Review it before you use it.
Capability tags behind 3 rules
- mcp__knocklog__scan_site untrusted-input
- mcp__knocklog__classify_request untrusted-input, outbound
- mcp__knocklog__list_known_agents private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.leonlesenechal/knocklog/verify?hash=904ff784122cb23b4b2ed1e83e41080cb4eacb2018ea6d65ca016fd63c10cc49" | jq -e '.changed == false'Pinned hash 904ff784122c, from Nov 9, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.leonlesenechal/knocklog/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.leonlesenechal/knocklog)Source: MCP Registry · repository. Synced Nov 9, 2026, 22:18 UTC.
Knocklog MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Knocklog MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Knocklog MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Knocklog MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Knocklog MCP server have?
- 3 tools: 2 write, 1 read. scan_site, classify_request and list_known_agents.
Does the Knocklog MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Knocklog MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): classify_request.
Has the Knocklog MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.