ai-agent-firewall
ai-agent-firewall is an MCP server published by fidacy.com, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.
Does ai-agent-firewall support the current MCP specification (2026-07-28)?
Not yet confirmed. ai-agent-firewall is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
Is ai-agent-firewall a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for ai-agent-firewall (as of 2026-08-20).
How do I connect to ai-agent-firewall?
ai-agent-firewall is available via the package npm:@fidacy/mcp, the official MCP Registry under com.fidacy/ai-agent-firewall, the source repository at https://github.com/lucaslubi/fidacy-mcp. Authentication: unknown. Transports: stdio.
Does ai-agent-firewall support MCP revision 2025-11-25?
Yes. ai-agent-firewall supports MCP revision 2025-11-25 (checked 2026-08-20).
Does ai-agent-firewall support MCP revision 2026-07-28?
No. ai-agent-firewall was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were ai-agent-firewall's facts last verified?
2026-08-20. Each fact on this page links to the sources used to verify it.
Every agent action watched, every money-moving one gated, every verdict independently verifiable.
Which MCP spec revisions does ai-agent-firewall support?
ai-agent-firewall has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is ai-agent-firewall?
Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.
Repository and package signals for ai-agent-firewall
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Stars
- 1
- Forks
- 0
- Last pushed
- (59 days ago)
- Created
- Open issues
- 0
- Primary language
- JavaScript
- License (repository)
- Apache-2.0
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: ai-agents, bitcoin, ed25519, firewall, mcp, mcp-server, model-context-protocol, payments, prompt-injection, security — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.18.2- Last published
- First published
- Releases
- 80
- License (package)
- Apache-2.0
- Maintainers
- 1
- Direct dependencies
- 2
- Unpacked size
- 503 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· confidence 0.85 (Good).
- Official MCP Registry record for com.fidacy/ai-agent-firewall at version 0.7.1 - lists package npm:@fidacy/mcp and repository https://github.com/lucaslubi/fidacy-mcp - accessed
- npm registry metadata for @fidacy/mcp at published version 0.18.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed