# @fidacy/mcp

Action firewall for AI agents: blocks the wrong action before it runs, every verdict Ed25519-signed.

- **Type:** MCP server
- **Trust:** 80/100 (A), scored on the package rubric
- **Verification:** verified (publisher, @lucaslubi)
- **Version:** 0.13.1
- **Author:** io.github.lucaslubi
- **License:** Apache-2.0
- **npm:** @fidacy/mcp
- **Source:** https://github.com/fidacy/fidacy-open
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

80/100 (A), scored on the package rubric
- Publisher verified: yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-28T18:10:13.775Z
- **Version scanned:** 0.18.4
- **CVEs:** none found by OSV at scan time

## Tools

13 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `fidacy-ai-agent-firewall`
- `request_payment` — 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 MU
- `verify_mandate` — Return the active mandate envelope (caps, allowed payees/categories, window, revocation) and Fidacy's Ed25519 public key for grant verification.
- `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.
- `spend_summary` — 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 mandat
- `list_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 statu
- `explain_decision` — 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 w
- `sentinel_alerts` — 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 
- `assess_action`
- `anchor_artifact`
- `check_artifact` — 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
- `upgrade` — Start upgrading this local install to a real Fidacy account (server-backed signed verdicts, anchored proof, higher volume). Returns a link to open; your anonymo
- `register_email` — Register the operator's email so their agent's protection history can attach to a real Fidacy account and Fidacy can reach them. ONLY call this when the human o

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@fidacy/mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40fidacy%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/%40fidacy%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40fidacy%2Fmcp
- HTML page: https://forgeregistry.com/registry/%40fidacy%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.