fixledger-mcp server
io.github.imsrvstv/fixledger-mcpimsrvstvstreamable-httpv0.4.0Scanned
Free <50ms Peek-Before-Pay error-to-fix & breaking-change oracle (MCP + x402 Base USDC).
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
Anlyon alternative
4 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 fixledger-mcp server can do
The fixledger-mcp server is published by the GitHub account imsrvstv. It has 5 tools. It can create or change data (4 tools: diagnose_peek, unlock_verified_fix, check_upstream_pulse and contribute_verified_fix), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 31, 2026, version 0.4.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.
5 tools
Changes things 4Claude Code: ask
check_upstream_pulseFREE ($0.00, <50ms) via MCP ($0.002 via REST; $0.00 during active outages).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.
Description, as the server wrote it FREE ($0.00, <50ms) via MCP ($0.002 via REST; $0.00 during active outages). Call on any HTTP 5xx, timeout, or sudden auth/RPC failure for external hosts (e.g. api.openai.com, api.stripe.com, mainnet.base.org). Combines official Statuspage feeds + 5-minute agent swarm error velocity so you halt destructive local edits during upstream outages.
contribute_verified_fixFREE ($0.00, <50ms) + EARNS 5 FREE CREDITS & 40% USDC ROYALTIES.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.
Description, as the server wrote it FREE ($0.00, <50ms) + EARNS 5 FREE CREDITS & 40% USDC ROYALTIES. Call after solving any MISS error locally with a verified passing build (exit_code === 0). Submits your minimal diff to the isolated Docker verification queue so your agent wallet earns automatic credits and passive micro-royalties.
diagnose_peekFREE ($0.00, <50ms).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.
Description, as the server wrote it FREE ($0.00, <50ms). Call FIRST on any build/compiler/runtime error, SDK exception, or HTTP 4xx/5xx API failure BEFORE running web searches or guessing code edits. Checks FixLedger for a Docker-verified fix (96%+ pass rate) or active upstream outage alert, saving ~18,000+ retry tokens ($0.18+). Zero cost on hits or misses.
unlock_verified_fix$0.005 (<50ms) via x402 Base USDC or 1 prepaid credit.No findings
Why it is in this group
- The name "unlock_verified_fix" says "unlock": a word for a change.
Description, as the server wrote it $0.005 (<50ms) via x402 Base USDC or 1 prepaid credit. Call immediately when diagnose_peek returns VERIFIED_MATCH (confidence >= 0.85). Unlocks the Docker-verified root cause, surgical code diff (<350 tokens), and anti-patterns, saving ~15,000-25,000 retry tokens (~36x ROI). Strictly Pay-on-Proof ($0.00 on NOT_FOUND).
Only reads 1Show 1 read-only tool
get_breaking_deltaFREE ($0.00) catalog list or $0.003 (<40ms) full unlock.No findings
Why it is in this group
- The name "get_breaking_delta" says "get": a word for reading.
Description, as the server wrote it FREE ($0.00) catalog list or $0.003 (<40ms) full unlock. Call BEFORE writing code against post-cutoff SDKs or selecting LLM model IDs (e.g. 'llm-models:active-2026', 'x402:eip3009-base-spec', 'tailwindcss:v3-to-v4', 'nextjs:v14-to-v15-async-apis'). Prevents deprecated parameter hallucinations (~15,000 tokens saved). Zero charge on unknown keys.
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 15, 2026, 13:21 UTC, unchanged since Nov 8, 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
- Nov 8, 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: 4 to 0
- Protocol version: 2025-03-26 to none
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
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: 4 -> 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: 4 to 0
- Protocol version: 2025-03-26 to none
Install
Pinned to version 0.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http fixledger https://fixledger-iota.vercel.app/api/mcpclaude mcp add --transport http fixledger https://fixledger-iota.vercel.app/api/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": [
"mcp__fixledger__get_breaking_delta"
],
"ask": [
"mcp__fixledger__diagnose_peek",
"mcp__fixledger__unlock_verified_fix",
"mcp__fixledger__check_upstream_pulse",
"mcp__fixledger__contribute_verified_fix"
],
"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 fixledger. 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.imsrvstv/fixledger-mcp/verify?hash=3608e4ec734c6fedd1ff3626a180db8542ae22c4c2dd90b47f4e6989c21de688" | jq -e '.changed == false'Pinned hash 3608e4ec734c, from Oct 31, 2026, 20: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.imsrvstv/fixledger-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.imsrvstv/fixledger-mcp)Source: MCP Registry · repository. Synced Oct 31, 2026, 20:17 UTC.
fixledger-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the fixledger-mcp server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the fixledger-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the fixledger-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 fixledger-mcp server have?
- 5 tools: 4 write, 1 read. diagnose_peek, unlock_verified_fix, check_upstream_pulse, contribute_verified_fix and get_breaking_delta.
Does the fixledger-mcp server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the fixledger-mcp server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the fixledger-mcp server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 31, 2026.