mcp-registry/eu.iban-test.www/iban-validation · v1.0.0
As of 2026-10-27 02:28 UTC, the Iban Test Iban Validation MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
Validate IBANs in 111 countries; bank directory checks for DE, AT, BE, FR, LU, NL, PT and ES.
Point your MCP client at this streamable-http endpoint: https://www.iban-test.eu/mcp
4 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
4 of 4 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. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
2 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Feu.iban-test.www%2Fiban-validation/fixes
{
"name": "quiqqer_mcp_skill_get",
"description": "Returns the skill metadata and full instruction body by name. Read the instructions before performing the matching task.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "quiqqer_mcp_skill_list",
"description": "Lists AI skills provided by installed QUIQQER packages. Use at the start of non-trivial QUIQQER tasks when package-specific instructions may apply. Match the returned descriptions to the task and load the relevant skills with quiqqer_mcp_skill_get before making changes.",
"inputSchema": {
"type": "object",
"properties": {
"category": {
"type": [
"null",
"string"
],
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "quiqqer_skill_get",
"description": "Returns the skill metadata and full instruction body by name. Read the instructions before performing the matching task.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/eu.iban-test.www/iban-validation"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/eu.iban-test.www/iban-validation"}) over MCP.
quiqqer_mcp_skill_list ~117 tokensquiqqer_skill_list ~115 tokensquiqqer_mcp_skill_get ~73 tokensquiqqer_skill_get ~72 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, 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%2Feu.iban-test.www%2Fiban-validation?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Feu.iban-test.www%2Fiban-validation?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Feu.iban-test.www%2Fiban-validation.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Feu.iban-test.www%2Fiban-validation.svg :target: https://glimind.com/server/mcp-registry%2Feu.iban-test.www%2Fiban-validation?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:46781e55730c0ebe…, first seen 2026-10-17, included at leaf 4239 of 76,839. Version history · verify what your client received.
Compare: most reliable knowledge 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-27 02:28 UTC, the Iban Test Iban Validation MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 2 minutes.
Iban Test Iban Validation MCP server advertises 4 tools, including quiqqer_mcp_skill_get, quiqqer_mcp_skill_list, quiqqer_skill_get, quiqqer_skill_list.
Point your MCP client at this streamable-http endpoint: https://www.iban-test.eu/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
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. Maintainers: alerts, deploy attestation and monthly reports.
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.