ibanforge
ibanforge is an MCP server published by cammac-creator, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-25.
Does ibanforge support the current MCP specification (2026-07-28)?
Not yet confirmed. ibanforge is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-25.
Is ibanforge a first-party (official) MCP server?
Undetermined. We have not verified the publisher relationship for ibanforge (as of 2026-08-25).
How do I connect to ibanforge?
ibanforge is available via a hosted remote endpoint at https://api.ibanforge.com/mcp, the package npm:ibanforge-mcp, the official MCP Registry under io.github.cammac-creator/ibanforge, the source repository at https://github.com/cammac-creator/ibanforge. Authentication: none. Transports: sse-legacy.
Does ibanforge support MCP revision 2025-11-25?
Yes. ibanforge supports MCP revision 2025-11-25 (checked 2026-08-25).
When were ibanforge's facts last verified?
2026-08-25. Each fact on this page links to the sources used to verify it.
Pre-payout IBAN screening for AI agents: validation, sanctions, Swiss clearing, risk scoring
Which MCP spec revisions does ibanforge support?
ibanforge has 1 verified spec-support record. 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 |
How widely adopted is ibanforge?
Ranked #478 in The MCP 500 with Adoption Index 46.37 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 458 | API · |
| GitHub stars | 3 | API · |
| GitHub forks | 4 | API · |
| Last push | 2026-09-15T14:39:33Z | API · |
| Repository archived | no | API · |
Repository and package signals for ibanforge
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
- Created
- Open issues
- 11
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- None
Declared topics: ai-agents, api, banking, bic, compliance, fintech, hono, iban, iban-validation, mcp, mcp-server, micropayments, neobank, sepa, sqlite, swift, typescript, validation, viban, x402 — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
1.4.3- Last published
- First published
- Releases
- 14
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 1
- Unpacked size
- 39 KB
- Registry signature
- Signed
- Build provenance
- No attestation
How was this verified, and what are the sources?
Verified · method: endpoint-probe
· confidence 0.85 (Good).
- Official MCP Registry record for io.github.cammac-creator/ibanforge at version 1.4.3 - lists remote endpoint https://api.ibanforge.com/mcp and repository https://github.com/cammac-creator/ibanforge - accessed
- Endpoint probe of https://api.ibanforge.com/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake - accessed
- Endpoint probe of https://api.ibanforge.com/mcp - declined server/discover; negotiated 2025-11-25 via the legacy initialize handshake - accessed