Is the Iso20022generator MCP server down?

mcp-registry/com.iso20022generator/mcp · v1.0.0

grade A

healthy

Last checked 2026-10-24 22:16 UTC · handshake 145ms

As of 2026-10-24 22:16 UTC, the Iso20022generator MCP server is up with a Glimind reliability score of 93/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)

100%

checks observed

4,025

outages (90d)

tools

Generate and validate SEPA ISO 20022 XML (pain.001, pain.008) and SWIFT MT103 payment messages.

Install Iso20022generator MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http iso20022generator-mcp-server https://mcp.iso20022generator.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "iso20022generator-mcp-server": {
      "type": "http",
      "url": "https://mcp.iso20022generator.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

grade C

C (76/100): 0 error(s), 3 warning(s) across 4 tool(s); ~2,979 tokens of tool definitions.

Scores higher than 11% of 15,666 MCP servers Glimind has audited.

Its tool list costs an agent ~2,979 tokens per session — more than 50% of servers.

75 → 76 since 2026-10-17

no tool-poisoning patterns

Schemas100

Descriptions73

Safety hints30

Token cost78

Client compatibility70

Protocol100

Reliability100

Stability100

What to fix (4)

1 tool definition(s) exceed ~1,200 tokens each (largest: generate_sepa_xml, ~2,115).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~1,515 tokens every session. How to fix →

Tools: generate_sepa_xml · saves ~1,515 tokens/session

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 →

Tools: generate_mt103, generate_sepa_xml, list_supported_versions, validate_sepa_xml

3 parameter(s) across 1 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 →

Tools: generate_mt103

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 →

Auto-fix: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.iso20022generator%2Fmcp/fixes

list_supported_versions 1 change

Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "list_supported_versions",
  "description": "List supported ISO 20022 formats and versions.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

validate_sepa_xml 1 change

Added readOnlyHint: true (inferred from the name). (verify)

{
  "name": "validate_sepa_xml",
  "description": "Validate a SEPA XML payload against XSD and business rules.",
  "inputSchema": {
    "type": "object",
    "anyOf": [
      {
        "type": "object",
        "required": [
          "xml_base64",
          "format",
          "version"
        ],
        "properties": {
          "format": {
            "type": "string",
            "const": "pain.001"
          },
          "version": {
            "enum": [
              "001.03",
              "001.09"
            ],
            "type": "string"
          },
          "xml_base64": {
            "type": "string",
            "minLength": 1
          }
        },
        "additionalProperties": false
      },
      {
        "type": "object",
        "required": [
          "xml_base64",
          "format",
          "version"
        ],
        "properties": {
          "format": {
            "type": "string",
            "const": "pain.008"
          },
          "version": {
            "enum": [
              "001.02",
              "001.08"
            ],
            "type": "string"
          },
          "xml_base64": {
            "type": "string",
            "minLength": 1
          }
        },
        "additionalProperties": false
      }
    ],
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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/com.iso20022generator/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.iso20022generator/mcp"}) over MCP.

Passed

Every tool has a well-formed, typed input schema.
No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
Tool names are unique and portable across clients.
Speaks MCP 2025-06-18.
99.98% uptime over 30 days.
No breaking contract changes in 30 days.

Largest tool definitions

generate_sepa_xml ~2,115 tokens
generate_mt103 ~641 tokens
validate_sepa_xml ~182 tokens
list_supported_versions ~41 tokens

Static 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:

Markdown

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.iso20022generator%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.iso20022generator%2Fmcp?ref=badge)

HTML

<a href="https://glimind.com/server/mcp-registry%2Fcom.iso20022generator%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.iso20022generator%2Fmcp.svg" alt="MCP agent-readiness"></a>

reStructuredText

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.iso20022generator%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.iso20022generator%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:2e3095ee0e4497c7…, first seen 2026-10-17, included at leaf 450 of 61,767. Version history · verify what your client received.

Tools (4)

Compare: most reliable finance servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Iso20022generator MCP server down right now?

How many tools does Iso20022generator MCP server provide?

Iso20022generator MCP server advertises 4 tools, including generate_mt103, generate_sepa_xml, list_supported_versions, validate_sepa_xml.

How do I install Iso20022generator MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.iso20022generator.com/mcp

Is the Iso20022generator MCP server safe to connect to an AI agent?

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.

Operator of Iso20022generator MCP server?

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.