# IoMarkets.tech ISO 20022 Test Bench (remote · iomarkets.tech)

Check ISO 20022 messages (pacs.008, pain.001, camt.053, seev.031) against schema and rules.

- Trust score: 75/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `iomarkets.tech`: 75/100 (this document), [markdown](https://verifymcp.io/servers/sergovashakmadze-iomarkets-tech/iomarkets.md), [page](https://verifymcp.io/servers/sergovashakmadze-iomarkets-tech/iomarkets)

## Channel facts

- Endpoint: `https://iomarkets.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2528 tokens (~109/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the IoMarkets.tech ISO 20022 Test Bench MCP server?

IoMarkets.tech ISO 20022 Test Bench is a hosted endpoint at https://iomarkets.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http sergovashakmadze-iomarkets-tech 'https://iomarkets.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sergovashakmadze-iomarkets-tech": {
      "url": "https://iomarkets.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sergovashakmadze-iomarkets-tech": {
      "type": "http",
      "url": "https://iomarkets.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sergovashakmadze-iomarkets-tech]
url = "https://iomarkets.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sergovashakmadze-iomarkets-tech": {
      "type": "remote",
      "url": "https://iomarkets.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sergovashakmadze-iomarkets-tech --url 'https://iomarkets.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sergovashakmadze-iomarkets-tech:
    url: "https://iomarkets.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sergovashakmadze-iomarkets-tech": {
      "Transport": "http",
      "Url": "https://iomarkets.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sergovashakmadze-iomarkets-tech -t streamable-http -u 'https://iomarkets.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sergovashakmadze-iomarkets-tech": {
      "type": "http",
      "url": "https://iomarkets.tech/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-30 (score 72)

First indexed and scored.

## MCP tools (23)

### `get_overview` (~53 tokens)

What IoMarkets.tech is

What IoMarkets.tech is and what is built: the ISO 20022 Test Bench, the Data API (market data for AI agents, paid per request over x402), the main pages, and what comes next.

### `get_guide` (~68 tokens)

How to do something on the site

Step-by-step instructions, with the exact button names, for one task on iomarkets.tech (checking a message, CI, verifying a proof, calling the Data API…). Without a task, lists the tasks.

Input parameters:

- `task` (string): Which task. Leave out to list them all.

### `explain_term` (~102 tokens)

Explain a word or an ISO 20022 tag

A plain-English meaning of a word used on the site (ISO 20022, schema, IBAN, BIC, LEI, ISIN, UETR, CBPR+, x402, signed proof, MCP…) or of an ISO 20022 XML tag abbreviation such as GrpHdr, CdtrAcct or IntrBkSttlmAmt. Without a term, lists the words.

Input parameters:

- `term` (string): The word or tag to explain.

### `list_messages` (~28 tokens)

Messages the Test Bench checks

The ISO 20022 message types and versions the Test Bench checks, with what each is for.

### `validate_message` (~227 tokens)

Check an ISO 20022 message

Check one ISO 20022 XML message (pacs.008.001.08, pacs.009.001.08, pacs.002.001.10, pacs.004.001.09, pain.001.001.09, camt.053.001.08, camt.054.001.08 or seev.031.001.14) against the official base schema, then business rules (check digits, totals, cross-element rules, market practice). Returns valid or not, and every problem with its line, element path, stable code and a plain reason. The message type is read from the namespace. The message is checked and not stored. Same code as https://iomarkets.tech/test-bench.

Input parameters:

- `message` (string): Check as this message type instead of the one its namespace names (optional).
- `schema_only` (boolean): Skip business rules (optional, default false).
- `xml` (string, required): The whole message, as XML text. A <Document> inside an envelope with an AppHdr is fine.

### `explain_issue` (~60 tokens)

Explain a Test Bench issue code

What a Test Bench issue code (such as IBAN_CHECKSUM, BALANCE_MISMATCH or OUT_OF_ORDER) means and how to fix it. Without a code, lists every code.

Input parameters:

- `code` (string): The issue code from a report.

### `list_samples` (~54 tokens)

Sample messages

The Test Bench sample library: a valid message of each type and broken ones, each with the issue code it raises. Use get_sample for the XML.

Input parameters:

- `message` (string): Only samples of this message type (optional).

### `get_sample` (~52 tokens)

One sample message

The XML of one sample message from list_samples, to use as a starting point or in tests. Every party and account in it is made up.

Input parameters:

- `id` (string, required): The sample id, from list_samples.

### `list_data_endpoints` (~55 tokens)

Data API routes and prices

The Data API routes at https://api.iomarkets.tech, what each returns and its price per call in USDC, with how an AI agent pays (x402 on Algorand mainnet, no account).

### `get_api_status` (~33 tokens)

Is the Data API up?

Whether the Data API at https://api.iomarkets.tech is answering right now, from its /health check.

### `estimate_data_api_cost` (~161 tokens)

Estimate Data API spend

What a monthly volume of Data API calls costs at the per-call x402 prices, against the indicative subscription plans. Give calls per month for each route; routes left out count as zero.

Input parameters:

- `candles` (number): Calls a month to /v1/candles (Candles).
- `proof_execution` (number): Calls a month to /v1/proof/execution (Execution proof).
- `proof_price` (number): Calls a month to /v1/proof/price (Price proof).
- `signal_imbalance` (number): Calls a month to /v1/signal/imbalance (Order imbalance).
- `signal_vwap` (number): Calls a month to /v1/signal/vwap (VWAP signal).

### `verify_proof` (~96 tokens)

Check a Data API proof

Check a signed proof (the { payload, signature } JSON a Data API proof route returns): that the ed25519 signature matches the published IoMarkets key, and that its USDC payment is confirmed on Algorand mainnet (looked up on a public indexer IoMarkets does not run).

Input parameters:

- `proof` (string, required): The proof as JSON text: { "payload": {…}, "signature": "…" }.

### `explain_execution_request` (~188 tokens)

How to call the execution-quality audit

Exactly how to call POST https://api.iomarkets.tech/v1/proof/execution, the paid best-execution audit: the body (pair, one of BTC-USDC, ETH-USDC, SOL-USDC, and fills: ts, fill_price, qty, side), the limits (fills per call, how old a fill may be, how close the market trade must be), the price, what comes back, and the answers that are not charged (400 for a bad body or an unsupported pair, 422 when no fill matches a trade). Give a draft body to check it with the API's own validation first. Read from the API's code; this tool calls nothing and pays nothing.

Input parameters:

- `body` (string): A draft request body as JSON text, { "pair": "BTC-USDC", "fills": [...] }, to check before paying (optional).

### `verify_execution_report` (~204 tokens)

Check an execution-quality report

Check the whole JSON that POST https://api.iomarkets.tech/v1/proof/execution returned ({ audit, summary, attestation }): that the ed25519 signature matches the published IoMarkets key, that its USDC payment is confirmed on Algorand mainnet (a public indexer IoMarkets does not run), that the rows hash to the signed audit_sha256, and that every row and the summary recompute with the API's own scoring, against the last trade and against the arrival mid (side-aware cost, qty-weighted averages, spread, matched and unmatched fills). The same checks as the page at https://iomarkets.tech/execution-check. Returns each check, and the recomputed summary as structured data.

Input parameters:

- `report` (string, required): The response body as JSON text, exactly as received: { "audit": [...], "summary": {...}, "attestation": { "payload": {...}, "signature": "…" } }.

### `check_token_contract` (~147 tokens)

Is this the real tokenized security?

Check a token contract against the Tokenized Asset Map: is it the issuer's own contract for a tokenized fund or security on that chain? Verdicts: official, other-chain (the address is listed, but on another chain), impostor (a listed symbol on this chain, a different contract), unknown (not in the map, which says nothing either way).

Input parameters:

- `address` (string, required): The contract: 0x address, Solana mint, Stellar CODE:ISSUER, Aptos/Sui type tag, …
- `chain` (string, required): The chain the contract is on.
- `symbol` (string): The symbol the token shows (optional), to catch impostors.

### `list_tokenized_assets` (~71 tokens)

Tokenized securities in the map

The securities in the Tokenized Asset Map with their identifiers (FIGI, ISIN where the issuer gives it) and the chains they are tokenized on. Optionally filter by issuer, name, symbol, ticker, ISIN or FIGI.

Input parameters:

- `query` (string): Filter text (optional).

### `get_tokenized_asset` (~58 tokens)

One tokenized security

One Asset Map entry in full: the security, every token contract chain by chain, the issuer sources each comes from, and whether its IoMarkets signature verifies.

Input parameters:

- `id` (string, required): The entry id, from list_tokenized_assets.

### `verify_asset_with_issuer` (~66 tokens)

Check an entry against the issuer, live

Fetch the issuer's own sources for one Asset Map entry now (its contracts page, its public API, or its stellar.toml) and confirm every listed contract is still there, so trust needn't rest on IoMarkets.

Input parameters:

- `id` (string, required): The entry id.

### `list_corporate_actions` (~214 tokens)

Dividends, splits and mergers

Corporate actions of US-listed companies from their own SEC EDGAR filings (8-Ks of US companies, 6-Ks of foreign private issuers): cash dividends (amount in the stated currency, per share or per ADS, ex, record and payment dates), stock splits, reverse splits and completed mergers (cash or shares per share). Filter by holdings (tickers, CIKs or FIGIs), by days (any of an event's dates between from and to) and by type. Each event links its filing and the sentence or table row it was read from. Also gives the iCalendar subscription URL for the same holdings and types (calendarUrl in structuredContent).

Input parameters:

- `from` (string): First day, YYYY-MM-DD (optional).
- `holdings` (array): Tickers, SEC CIKs or FIGIs (optional; none means every company).
- `to` (string): Last day, YYYY-MM-DD (optional).
- `types` (array): Kinds of event (optional).

### `holdings_calendar` (~122 tokens)

What affects my holdings this week

For a list of holdings (tickers, CIKs or FIGIs), every ex-date, record date, payment date and effective date in one week, day by day. The week holding `day`, Monday to Sunday; this week by default. Ends with an iCalendar (webcal) subscription URL for those holdings, to give the user for their calendar app.

Input parameters:

- `day` (string): Any day in the week, YYYY-MM-DD (optional; today by default).
- `holdings` (array, required): Tickers, SEC CIKs or FIGIs.

### `get_corporate_action` (~86 tokens)

One corporate action, with its seev.031 message

One event in full: every date and term, the filing and the sentence or table row it came from, tokenized versions in the Asset Map, and the event as an ISO 20022 seev.031.001.14 notification (checked by the Test Bench).

Input parameters:

- `id` (string, required): The event id, from list_corporate_actions or holdings_calendar.

### `token_corporate_actions` (~101 tokens)

What is coming for the stock behind this token

For a token contract that the Asset Map lists as a tokenized stock or ETF (such as an xStock): the security it tracks, and that security's dividends, splits and mergers from the corporate actions feed, each with what it does to the token. Answers 'I hold this token; what is coming?' in one call.

Input parameters:

- `address` (string, required): The token contract.
- `chain` (string, required): The chain the token is on.

### `get_roadmap` (~34 tokens)

What is built and what is next

What IoMarkets.tech has built and is building next, in the same words as iomarkets.org/roadmap.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sergovashakmadze-iomarkets-tech/iomarkets#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72

## Common questions

### What is the IoMarkets.tech ISO 20022 Test Bench MCP server?

IoMarkets.tech ISO 20022 Test Bench is an MCP server listed in the public MCP registry as io.github.SergoVashakmadze/iomarkets-tech. Check ISO 20022 messages (pacs.008, pain.001, camt.053, seev.031) against schema and rules. This page covers its hosted endpoint (https://iomarkets.tech/mcp).

### Is the IoMarkets.tech ISO 20022 Test Bench MCP server safe to use?

IoMarkets.tech ISO 20022 Test Bench scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the IoMarkets.tech ISO 20022 Test Bench MCP server expose?

IoMarkets.tech ISO 20022 Test Bench exposes 23 tools: get_overview, get_guide, explain_term, list_messages, validate_message, and 18 more. Their descriptions and schemas cost roughly 2,280 tokens of context every time the server is loaded.

### Does the IoMarkets.tech ISO 20022 Test Bench MCP server require authentication?

No. We connected to IoMarkets.tech ISO 20022 Test Bench without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the IoMarkets.tech ISO 20022 Test Bench MCP server still maintained?

IoMarkets.tech ISO 20022 Test Bench is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://iomarkets.tech/mcp
- Website: https://iomarkets.tech/start
- Changelog RSS feed: https://verifymcp.io/servers/sergovashakmadze-iomarkets-tech/iomarkets.xml
- Changelog JSON feed: https://verifymcp.io/servers/sergovashakmadze-iomarkets-tech/iomarkets.json
- HTML version of this page: https://verifymcp.io/servers/sergovashakmadze-iomarkets-tech/iomarkets