mcpbeat Sign in

Fidren MCP Server

answering

Fidren is answering right now. Last checked 15 min ago. It exposes 1 tools.

Checks a counterparty before an AI agent pays: what the evidence supports, and for how much.

Uptime history 4 days of history · worst day 95%
4 days agonow
97.8%
Uptime 24h
89 of 91 checks
1
Tools
read from the server
671 ms
Response time
average over 24h
open, no key
Access
streamable-http

Fidren does not always answer

Over the last week it answered 97.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add counterparty --transport http https://api.fidren.net/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "counterparty": {
      "url": "https://api.fidren.net/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.counterparty]
url = "https://api.fidren.net/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "counterparty": {
      "url": "https://api.fidren.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "counterparty": {
      "url": "https://api.fidren.net/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fidren
fidren_check_counterparty
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.

Endpoints

URLTransportStateLatencyChecked
https://api.fidren.net/mcp streamable-http answering 682 ms 15 min ago

Alternatives to Fidren

same job, measured the same way
Frisk
by tryfrisk

Screen the counterparty of an x402 payment before an agent pays it. Runs offline by default.

23 installs/wk local only
Vouch
by notifuturo

Check if a counterparty is safe to pay: trust/risk score for AI agents. Scam/phishing screen.

2 tools answering
Payment Guard MCP
by mlawsonking

Pre-send risk check for AI agents that move money — screen an address or payment URL before sending.

40 installs/wk local only
NEUS MCP
by neus

The trust harness for AI agents. Set what an agent can do before it acts.

12 tools answering
Clarity by Health AI
by healthai

Condition-aware ingredient and product checks for agents, with evidence tiers and citations.

9 tools answering
The Agent Lounge
by kphatak001

A guestbook for AI agents: read what other agents wrote, sign it yourself, and check the counters.

3 tools answering
Feason Context
by feason-com

Christian source evidence for AI agents, with provenance, tradition coverage, and citation checks.

answering
SolvScore
by solvscore

Credit scores for AI agents. Underwrite an unknown counterparty before extending credit.

18 tools answering

Fidren — questions

Answers built from our own checks of this server.

What can Fidren do?
It exposes 1 tools, read directly from the server on our last check. Among them: fidren_check_counterparty. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Fidren working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 671 ms. The bar chart above shows every period we have measured.
How do I connect Fidren?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Fidren need an API key?
No. Fidren completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Fidren?
It answers our handshake in 671 ms on average, which is faster than 19% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.