Fidren MCP server
net.fidren/counterpartyfidren.netstreamable-httpv1.14.0Scanned
Checks a counterparty before an AI agent pays: what the evidence supports, and for how much.
1 tool: 1 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- 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 Fidren MCP server can do
The Fidren MCP server is published by fidren.net, a domain the MCP Registry verified. It has 1 tool. It can create or change data (1 tool: fidren_check_counterparty), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (fidren_check_counterparty).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.14.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.
1 tool
Changes things 1Claude Code: ask
fidren_check_counterpartyBefore an AI agent pays an unfamiliar counterparty, Fidren returns what payment action the observed evidence supports, how much exposure that evidence supports for the amount actua…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 Before an AI agent pays an unfamiliar counterparty, Fidren returns what payment action the observed evidence supports, how much exposure that evidence supports for the amount actually requested, and why. Same counterparty, same evidence, a different requested amount: potentially a different payment action. The amount is an input to the decision, not a filter applied to a fixed score. Call this before sending a payment to a counterparty address the agent has not paid before. Or before raising the amount it is willing to send to a counterparty it has paid before. Or when a counterparty requests more than a previously approved exposure. Cost: 100 free decisions per day, per IP. None. No account, no API key, no card, no wallet. After that, $0.01 USDC per decision over x402 on eip155:8453. Coverage: observed settlement history is indexed on base (eip155:8453) only. An address on any other chain answers from no history rather than from evidence — which is a statement about coverage, not a verdict about the counterparty. Fidren never holds, transmits, settles, signs, escrows or intermediates funds. It returns an advisory decision; the caller’s own infrastructure enforces it. A returned verdict is advice; it moves nothing and blocks nothing on its own.
Annotations the server declares
- title: Check a counterparty before paying
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- 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, 19:16 UTC, unchanged since Nov 13, 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
- 1
- Protocol version
- 2025-06-18
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.fidren.net/mcp: tools/list returned 1 tool to an anonymous client, including fidren_check_counterparty (write)
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 530 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
- Nov 6, 2026
- HTTP status of an anonymous initialize: 200 to 530
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 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: 530 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 1 more).View diff
- HTTP status of an anonymous initialize: 530 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 530; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 530
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.14.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http counterparty https://api.fidren.net/mcpclaude mcp add --transport http counterparty https://api.fidren.net/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__counterparty__fidren_check_counterparty"
],
"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 counterparty. Review it before you use it.
Capability tags behind 1 rule
- mcp__counterparty__fidren_check_counterparty untrusted-input
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/net.fidren/counterparty/verify?hash=082620bad1d51c2e5cb550b3ba5567fb605f6d210fcd714bdd8a750474686924" | jq -e '.changed == false'Pinned hash 082620bad1d5, from Nov 18, 2026, 19:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.fidren/counterparty/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.fidren/counterparty)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
Fidren MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Fidren MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, 1 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 Fidren MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Fidren 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 Fidren MCP server have?
- 1 tool: 1 write. fidren_check_counterparty.
Does the Fidren MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Fidren MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Fidren MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.