com.fidacy/mcp

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.

Call this BEFORE the agent does something on a human's behalf that is not a payment and cannot be taken back: sending a message or email a person will act on, placing a voice call, filing a claim, committing to a promise. Ask first, then act on the answer — a verdict fetched after the message is sent is a record, not a control. Returns a SIGNED Fidacy trust verdict from the live engine (default https://api.fidacy.com). 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. It moves no money and holds nothing: it decides and signs, and the payment-firewall tools (request_payment et al.) cover the money side in the same install.

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.

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.

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 — it is consent-based. Does not create an account or move money.

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.

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

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.

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

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.

Call this the MOMENT a document that someone could later dispute is created or received — a contract, an invoice, a claim, a prescription, a report you generated, a file you were given. Do not wait to be asked and do not do it later: the proof is worth exactly what its timestamp says, and a hash registered after the argument starts proves nothing. It proves the artifact existed exactly as-is at this moment and makes 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. Also works for images, audio and video. `kind` defaults to document; optional `label` is a short reference (an invoice number, a case id — no PII). Tell the operator the sha256 you registered, so they can verify it themselves at fidacy.com/verify.

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