Fidren
REMOTE · API.FIDREN.NET
Checks a counterparty before an AI agent pays: what the evidence supports, and for how much.
Available components
Last scanned (10 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 488 tokens (~488/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
- Server version: 1.13.0 → 1.14.0 functional
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 80. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 63 to 73. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 63. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 76
- Server version: 1.8.0 → 1.13.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.fidren.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fidren.net | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | bb5dc502445fd3f60e680876be56f101 |
| SANs: fidren.net, *.fidren.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.fidren.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| fidren.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.fidren.net/mcp | Verified | 200 | |
| http (plaintext) | http://api.fidren.net/mcp | HTTPS enforced | 301 | https://api.fidren.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fidren_check_counterparty Check a counterparty before paying ~397
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The counterparty you are about to pay. 0x-prefixed, 20 bytes. |
| amount_cents | integer | yes | The amount you actually intend to pay, in cents. Not a cap and not a filter: the same counterparty can warrant a different action at a different amount. |
| chain | string | yes | Which chain the address is on. Evidence exists for "base" only. |
| currency | string | – | Optional. Defaults to USD. |
| service_identifier | string | – | Optional. Your own label for the operation. |
No output schema declared.
No examples provided.
How do I install the Fidren MCP server?
Fidren is a hosted endpoint at https://api.fidren.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.fidren.net
claude mcp add --transport http net-fidren-counterparty 'https://api.fidren.net/mcp'
What is the Fidren MCP server?
Fidren is an MCP server listed in the public MCP registry as net.fidren/counterparty. Checks a counterparty before an AI agent pays: what the evidence supports, and for how much. This page covers its hosted endpoint (https://api.fidren.net/mcp).
Is the Fidren MCP server safe to use?
Fidren scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Fidren MCP server expose?
Fidren exposes 1 tool: fidren_check_counterparty. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.
Does the Fidren MCP server require authentication?
No. We connected to Fidren without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fidren MCP server still maintained?
Fidren is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.