Remote MCP · Endpoint
IBAN Validator MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://iban-validated.othmen-mohammadi.workers.dev/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.peonixo147/iban-validated
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 77.8% from 18 checks
- Described by its publisher as
- Validate IBAN bank account numbers (format + mod-97 checksum). Returns whether the IBAN is valid.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 2 days ago | Failed - the server returned an HTTP error | — |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 6 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Handshake completed | 545 ms |
| 9 days ago | Handshake completed | 921 ms |
| 10 days ago | Handshake completed | 566 ms |
| 11 days ago | Handshake completed | 924 ms |
| 14 days ago | Handshake completed | 625 ms |
| 15 days ago | Handshake completed | 445 ms |
| 17 days ago | Handshake completed | 672 ms |
| 18 days ago | Handshake completed | 551 ms |
| 19 days ago | Handshake completed | 507 ms |
| 20 days ago | Handshake completed | 499 ms |
| 21 days ago | Handshake completed | 719 ms |
| 22 days ago | Handshake completed | 648 ms |
| 23 days ago | Handshake completed | 828 ms |
| 24 days ago | Handshake completed | 543 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 18.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with IBAN Validator and makes no claim about it beyond what these checks measured.