# Fidren (remote · api.fidren.net)

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

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.fidren.net`: 70/100 (this document), [markdown](https://verifymcp.io/servers/net-fidren-counterparty/api.md), [page](https://verifymcp.io/servers/net-fidren-counterparty/api)

## Channel facts

- Endpoint: `https://api.fidren.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http net-fidren-counterparty 'https://api.fidren.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-fidren-counterparty": {
      "url": "https://api.fidren.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-fidren-counterparty": {
      "type": "http",
      "url": "https://api.fidren.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-fidren-counterparty]
url = "https://api.fidren.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-fidren-counterparty": {
      "type": "remote",
      "url": "https://api.fidren.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-fidren-counterparty --url 'https://api.fidren.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-fidren-counterparty:
    url: "https://api.fidren.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-fidren-counterparty": {
      "Transport": "http",
      "Url": "https://api.fidren.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-fidren-counterparty -t streamable-http -u 'https://api.fidren.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-fidren-counterparty": {
      "type": "http",
      "url": "https://api.fidren.net/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-18 (score 69)

First indexed and scored.

## MCP tools (1)

### `fidren_check_counterparty` (~397 tokens)

Check a counterparty before paying

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.

Input parameters:

- `address` (string, required): The counterparty you are about to pay. 0x-prefixed, 20 bytes.
- `amount_cents` (integer, required): 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, required): 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-fidren-counterparty/api#diagnostics

## Score history

- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69

## Common questions

### 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 70 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.fidren.net/mcp
- Website: https://fidren.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-fidren-counterparty/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-fidren-counterparty/api.json
- HTML version of this page: https://verifymcp.io/servers/net-fidren-counterparty/api