Fidacy MCP server

Read from the package source without running it. The installed server may list more.

• anchor_artifact
• assess_action
• 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 \u2014 that is exactly the tampering signal.

• 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 why a specific payment was blocked.

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

• 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 status to answer 'what got blocked' directly. Read-only, works offline.

• register_emailwrite action

  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 operator has explicitly given their email and agreed to be contacted \u2014 it is consent-based. Does not create an account or move money.

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

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

• 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 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'.

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

• verify_mandate

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

• Code scan58 source files scanned15/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 47 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Fidacy: common questions

Is Fidacy MCP server safe?

With care: it is graded C, so read the findings first (63/100). Read the Fidacy safety report

How do I install Fidacy?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Fidacy need an API key?

Yes. The registry entry asks for FIDACY_ENGINE_API_KEY.

Is Fidacy maintained?

The last commit was 47 days ago (2026-08-04). The latest release is v0.19.0.

What can I use instead of Fidacy?

Servers from other publishers that do the same job: MCP server, Agent-Native Chat MCP server and Dvalincode MCP server. Compare all Fidacy alternatives.