mcp-registry/io.github.cammac-creator/ibanforge · v1.9.0
As of 2026-10-16 15:36 UTC, the Cammac Creator Ibanforge MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 82.2% of Glimind's liveness checks. It had 47 outages in 90 days, with a median recovery of 25.9 hours.
Check the bank behind an IBAN before you pay: bank-code check, BIC with source, bank-level sanctions
Point your MCP client at this streamable-http endpoint: https://api.ibanforge.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.
Reachable 82.2% of the time over the last 30 days; median recovery 1556 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
Handshake + tools/list takes ~2,102 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
1 of 11 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
send_feedback ~453 tokenscheck_postal_address ~426 tokensvalidate_payment_reference ~286 tokenscheck_swiss_qr_bill ~280 tokensrequest_api_key ~252 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.cammac-creator%2Fibanforge?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.cammac-creator%2Fibanforge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cammac-creator%2Fibanforge.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.cammac-creator%2Fibanforge.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.cammac-creator%2Fibanforge?ref=badge :alt: MCP agent-readiness
Compare: most reliable finance servers · most reliable other servers · most reliable data servers · most reliable database servers · most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-16 15:36 UTC, the Cammac Creator Ibanforge MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 82.2% of Glimind's liveness checks. It had 47 outages in 90 days, with a median recovery of 25.9 hours.
Cammac Creator Ibanforge MCP server advertises 11 tools, including batch_validate_iban, check_compliance, check_postal_address, check_swiss_qr_bill, lookup_bic.
Point your MCP client at this streamable-http endpoint: https://api.ibanforge.com/mcp
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.