servers / com-fidacy-mcp

com.fidacy/mcp

communitystdiolocalwrite capablehealthy

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


01Tools · 7
ToolRiskSide effectsApproval
verify_mandate
Return the active mandate envelope (caps, allowed payees/categories, window, revocation) and Fidacy's Ed25519 public key for grant verification.
unknownunknownunknown
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`. 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.
unknownunknownunknown
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 anonymous usage is preserved and migrated to the new account.
unknownunknownunknown
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 MUST require the grant. Call this before any payment; never pay without it.
writetrueunknown
assess_action
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.
unknownunknownunknown
anchor_artifact
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).
readfalseunknown
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.
readunknownunknown

02Install & source
npx -y @fidacy/mcp
npx

03Access granted
Process payments · write

The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.


05Provenance & freshness
sourcesOfficial MCP Registry [p1]
last_checked2026-07-07 09:06Z
next_check2026-07-08 13:30Z
cadenceevery 29h
verifiedtools_list:passed handshake:passed metadata:passed
index_statusindex9 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. com.fidacy/mcp MCP — as seen on mcpexplorer.com

[![com.fidacy/mcp MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/com-fidacy-mcp.svg)](https://mcpexplorer.com/servers/com-fidacy-mcp)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →