Mithrandir — free MCP gateway test
io.github.Hyhyr2/mithrandirHyhyr2streamable-httpv0.20.0Scanned
Observe MCP tools, verify repeated reads, then try bounded exact reuse for free.
3 tools: 1 can delete or cancel things and 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Mithrandir — free MCP gateway test can do
The Mithrandir — free MCP gateway test is published by the GitHub account Hyhyr2. It has 3 tools. It can delete or cancel things (1 tool: mithrandir_gateway_trial_start) and create or change data (2 tools: mithrandir_demo and mithrandir_security_profile). None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Last scanned Oct 21, 2026, version 0.20.0.
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
Deletes or cancels 1Claude Code: deny
mithrandir_gateway_trial_startStart a bounded free gateway test.No findings
Why it is in this group
- The name "mithrandir_gateway_trial_start" says "start": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Start a bounded free gateway test. Connect your public HTTPS MCP server, then approve safe reads and verify repetition before free Optimize activation.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 2Claude Code: ask
mithrandir_demoRun a free isolated synthetic Reuse Autopilot demonstration.1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "mithrandir_demo" 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,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
Description, as the server wrote it Run a free isolated synthetic Reuse Autopilot demonstration. No production account, upload, payment or private data is used. Compare unchanged, one-partition-changed and missing-source behavior before onboarding.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
mithrandir_security_profileFree machine-readable description of the v17 Cognitive Membrane trust model: origin-bound authority, task-scoped exact-call capabilities, replay protection, egress control and two-…No 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.
Description, as the server wrote it Free machine-readable description of the v17 Cognitive Membrane trust model: origin-bound authority, task-scoped exact-call capabilities, replay protection, egress control and two-phase effectful actions. This is a security contract description, not proof that a deployment is vulnerability-free.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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 20, 2026, 18:58 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 404
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: initialize answered HTTP 404.
Posture changes
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Warnmithrandir_demo
The server marks "mithrandir_demo" 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,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 404; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 404
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.20.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http mithrandir https://mithrandir-production.up.railway.app/mcpclaude mcp add --transport http mithrandir https://mithrandir-production.up.railway.app/mcpRun 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": [],
"ask": [
"mcp__mithrandir__mithrandir_demo",
"mcp__mithrandir__mithrandir_security_profile"
],
"deny": [
"mcp__mithrandir__mithrandir_gateway_trial_start"
]
}
}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 mithrandir. Review it before you use it.
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.Hyhyr2/mithrandir/verify?hash=1ee872580e7abb7b5dc08341cfada4790e60c851893eb8526217795bf1b28b14" | jq -e '.changed == false'Pinned hash 1ee872580e7a, from Oct 21, 2026, 19:08 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Hyhyr2/mithrandir/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Hyhyr2/mithrandir)Source: MCP Registry. Synced Oct 21, 2026, 18:16 UTC.
Mithrandir — free MCP gateway test: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Mithrandir — free MCP gateway test safe?
- No scan can promise that. What its definitions show: 3 tools, 3 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 Mithrandir — free MCP gateway test delete data?
- Yes. 1 tool can delete, cancel or revoke something: mithrandir_gateway_trial_start.
Can the Mithrandir — free MCP gateway test 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 Mithrandir — free MCP gateway test have?
- 3 tools: 1 destructive, 2 write. mithrandir_gateway_trial_start, mithrandir_demo and mithrandir_security_profile.
Does the Mithrandir — free MCP gateway test need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Mithrandir — free MCP gateway test send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Mithrandir — free MCP gateway test changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.