# com.fidacy/mcp (npm · @fidacy/mcp)

Payment firewall for AI agents: a signed, verifiable verdict on every money-moving action.

- Trust score: 61/100 (medium)
- Change this week: +17
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

> **Deprecated**: this server is marked deprecated in the MCP registry.

## Components

- npm · `@fidacy/mcp`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-fidacy-mcp/fidacy-mcp.md), [page](https://verifymcp.io/servers/com-fidacy-mcp/fidacy-mcp)

## Channel facts

- Registry: `npm`
- Package: `@fidacy/mcp`
- Version: `0.2.7`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 40/100
  - AI-judged instruction clarity (poor).
  - Context-footprint check failed: tool/resource definitions use about 1320 tokens (~120/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
  - Structured output schemas are declared (9% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add com-fidacy-mcp -- npx -y @fidacy/mcp
```

### Codex

```bash
codex mcp add com-fidacy-mcp -- npx -y @fidacy/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fidacy-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@fidacy/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fidacy-mcp --command npx --arg -y --arg @fidacy/mcp
```

### Hermes

```yaml
mcp_servers:
  com-fidacy-mcp:
    command: "npx"
    args: ["-y", "@fidacy/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "com-fidacy-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@fidacy/mcp"
      ]
    }
  }
}
```

## 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-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 60, +40)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] Schema quality: fair → poor
- [functional] Licence: Apache-2.0

### 2026-08-01 (score 20, −8)

- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 28, −42)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 70, +46)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Schema quality: unverified → fair
- [functional improvement] License: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: Apache-2.0

### 2026-07-29 (score 24, −20)

- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 44)

First indexed and scored.

## MCP tools (11)

### `request_payment` (~222 tokens)

Request Payment Authorization

Authorize a payment action against the active Fidacy mandate. Returns an ALLOW with a signed grant, or a DENY with the violated rule. The downstream executor MUST require the grant. Call this before any payment; never pay without it.

Input parameters:

- `amount` (number, required): Amount in the mandate currency
- `category` (string, required): Purpose category (must be allowed by the mandate)
- `currency` (string, required): ISO 4217 currency code
- `idempotencyKey` (string, required): Caller-supplied idempotency key
- `invoiceRef` (string): Optional invoice identity. When set, Fidacy enforces one payment per invoice: a second request for the same invoiceRef is DENIED, at any amount.
- `payee` (string, required): Payee identifier
- `purpose` (string, required): Your stated reason for this payment, in your own words. It is persisted readably on the tamper-evident audit record (ALLOW and DENY alike) and becomes part of the after-the-fact proof, so write the r…

Output parameters:

- `decisionId` (string)
- `grant` (string)
- `status` (string)
- `violatedRule` (string)

### `verify_mandate` (~41 tokens)

Verify Active Mandate

Return the active mandate envelope (caps, allowed payees/categories, window, revocation) and Fidacy's Ed25519 public key for grant verification.

### `get_audit_proof` (~56 tokens)

Get Audit Proof

Return the tamper-evident, hash-chained proof for a decision id, including whether the chain is intact and the public key it verifies against.

Input parameters:

- `decisionId` (string, required): Decision id returned by request_payment

### `spend_summary` (~97 tokens)

Spend Summary (what my agents spent and what was blocked)

Operator report over a time window: how many payment decisions were made, how much was paid and to whom, how much was blocked before executing, and which mandate rules did the blocking. Read-only, works offline against the local audit chain. Use this to answer questions like 'what did my agents spend this week' or 'has anything been blocked'.

Input parameters:

- `days` (integer): Window in days, counting back from now. Default 7.

### `list_decisions` (~87 tokens)

List Recent Payment Decisions

List recent agent payment decisions, newest first, with payee, amount, the agent's stated reason, and for blocked ones the rule that stopped it. Filter by status to answer 'what got blocked' directly. Read-only, works offline.

Input parameters:

- `limit` (integer): How many decisions to return. Default 20.
- `status` (string): Filter by outcome. Default all.

### `explain_decision` (~72 tokens)

Explain a Decision (why was this allowed or blocked)

Explain one decision in plain language: what was requested, what the mandate did about it, why, and the tamper-evident proof for it. Use when an operator asks why a specific payment was blocked.

Input parameters:

- `decisionId` (string, required): Decision id from request_payment, list_decisions or spend_summary

### `sentinel_alerts` (~98 tokens)

Sentinel Alerts (allowed, but outside this agent's pattern)

Predictive pattern alerts from the local audit chain: first-ever payee, amount spikes vs this agent's own history, velocity bursts, payments riding the mandate ceiling, and retries after a denial (the behavior our Model Watch benchmark measures). Deterministic and explainable, no model. Use to answer 'has anything unusual happened' before it becomes a loss.

Input parameters:

- `limit` (integer): How many flagged decisions to return. Default 20.

### `assess_action` (~195 tokens)

Assess Action (Signed Trust Verdict)

Return a SIGNED Fidacy trust verdict from the live engine (default https://api.fidacy.com) for a proposed action. The signed proof is `riskPayloadJws` + `signingKeyId`, verifiable by anyone via @fidacy/verify against the engine JWKS at /.well-known/jwks.json. `kind` is one of ap2_payment, message_send, voice_call, custom, claim_document; `mandate` is the action/mandate object for that kind. This is the verdict (advisory) layer and moves no money; it complements the payment-firewall tools (request_payment et al.) in the same install.

Input parameters:

- `a2a` (object)
- `idempotencyKey` (string)
- `kind` (string)
- `mandate` (object, required)
- `mandateType` (string)
- `spendingMandate` (object)

### `anchor_artifact` (~185 tokens)

Anchor Artifact (Bitcoin-anchored integrity proof)

Prove an artifact existed exactly as-is at this moment, and make any later tampering detectable. Give a file `path` (hashed locally with SHA-256 — the file itself is NEVER uploaded) or a precomputed `sha256`. The hash is registered on Fidacy's tamper-evident audit chain, which is checkpointed to the Bitcoin blockchain, and you get a signed receipt (JWS) verifiable offline against the engine JWKS. Use it for contracts, invoices, medical prescriptions, insurance claims, images, audio, video. `kind` defaults to document; optional `label` is a short reference (an invoice number, a case id — no PII).

Input parameters:

- `kind` (string)
- `label` (string)
- `path` (string)
- `sha256` (string)
- `subject` (string)

### `check_artifact` (~94 tokens)

Check Artifact (was this hash anchored?)

Check whether an artifact was anchored by this account and the state of its Bitcoin checkpoint. Give a file `path` (hashed locally, never uploaded) or a `sha256`. If the current hash of a file does NOT match any anchored record that you expected to match, the file changed since anchoring — that is exactly the tampering signal.

Input parameters:

- `path` (string)
- `sha256` (string)

### `upgrade` (~49 tokens)

Upgrade to a Fidacy account

Start upgrading this local install to a real Fidacy account (server-backed signed verdicts, anchored proof, higher volume). Returns a link to open; your anonymous usage is preserved and migrated to the new account.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-fidacy-mcp/fidacy-mcp#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 20
- 2026-07-31: 28
- 2026-07-30: 70
- 2026-07-29: 24
- 2026-07-28: 44
- 2026-07-27: 44

## Links

- npm package: https://www.npmjs.com/package/@fidacy/mcp
- Socket report: https://socket.dev/npm/package/@fidacy/mcp
- Repository: https://github.com/lucaslubi/fidacy-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-fidacy-mcp/fidacy-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fidacy-mcp/fidacy-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-fidacy-mcp/fidacy-mcp