Action firewall for AI agents: blocks the wrong action before it runs, every verdict Ed25519-signed.
MCPpedia last refreshed this data
io.github.lucaslubi/fidacy-mcp is an MCP server that action firewall for AI agents: blocks the wrong action before it runs, every verdict Ed25519-signed. Its tool list has not been published yet over sse, requires no API key, and scores 61/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-lucaslubi-fidacy-mcp": {
"args": [
"-y",
"@fidacy/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Open verification + SDK for Fidacy — the external, signed trust layer for agent payments.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@fidacy/mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @fidacy/mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / security
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
An autonomous agent that conducts deep research on any data using any LLM providers
The official MCP server implementation for the Perplexity API Platform
1000+ scientific tools for AI scientists: life science, reserach, literature, and more.
MCP Security Weekly
Get CVE alerts and security updates for io.github.lucaslubi/fidacy-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Open verification + SDK for Fidacy — the external, signed trust layer for agent payments.
Verify any Fidacy verdict yourself, against our public JWKS. Don't trust us — check.
Every verdict Fidacy issues is signed. These packages let you fetch our public keys and cryptographically verify that a risk payload or webhook genuinely came from Fidacy and was not tampered with — entirely client-side, with no need to call back to us.
"Anyone can verify" is a testable claim here, not a slogan: a
conformance corpus ships signed fixtures plus
expected outcomes, so a port of the verifier in any language proves
compatibility offline (node packages/verify/conformance/run.mjs from the repo
root, 8/8 or it is not compatible).
| Package | Description |
|---|---|
@fidacy/verify | Isomorphic signature verification against Fidacy's public JWKS. Zero trust in the SDK transport — verify the verdict itself. |
@fidacy/sdk | Thin, typed client for the public Fidacy API. Calls the API and verifies every response via @fidacy/verify. |
fidacy-spec | The open specification for Fidacy's signed payloads, JWKS, and webhook formats. See spec/. |
Run it in 30 seconds (assess + verify a real signed verdict):
git clone https://github.com/fidacy/fidacy-open && cd fidacy-open/quickstart
npm install
FIDACY_API_KEY=fky_test_… node quickstart.mjs # a TEST key from app.fidacy.com (mode: test)
Output: a signed verdict and signature valid: true — cryptographically verified against
the public JWKS, client-side, with no call back to Fidacy. See quickstart/.
Or add the packages to your own project (published on npm, Apache-2.0):
npm i @fidacy/sdk @fidacy/verify
Python? Same flow, two dependencies — see quickstart-python/:
cd fidacy-open/quickstart-python && pip install -r requirements.txt
FIDACY_API_KEY=fky_test_… python3 quickstart.py
import { Fidacy } from '@fidacy/sdk';
import { verifyRiskPayload } from '@fidacy/verify';
const fidacy = new Fidacy({ apiKey: process.env.FIDACY_API_KEY! });
// Assess a payment mandate (AP2 intent/cart).
const result = await fidacy.assess({
mandate: {
vct: 'mandate.payment.1',
payee: { id: 'merchant_demo', name: 'Demo Store' },
payment_amount: { amount: 4299, currency: 'EUR' },
payment_instrument: { id: 'pi_demo', type: 'card' },
},
});
console.log('decision:', result.decision);
// Don't trust us — verify the signed verdict yourself, against the public JWKS:
const verified = await verifyRiskPayload(result.riskPayloadJws);
console.log('signature valid:', verified.valid);
console.log('decisions match:', verified.claims.decision === result.decision);
Runnable end-to-end example: examples/quickstart-node.
spec/Home: the canonical repository is https://github.com/fidacy/fidacy-open. Packages are published under the npm scope @fidacy (Apache-2.0).
@fidacy/verify runs in Node 18+, the browser, and edge runtimes.
No Node-only globals.Apache-2.0 © 2026 ZEEPCODE GROUP LLC