# Sergovashakmadze Iomarkets Tech MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.sergovashakmadze%2Fiomarkets-tech
Registry id: `mcp-registry/io.github.sergovashakmadze/iomarkets-tech`
Status: live (checked 2026-11-22T19:38:36.721Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 868
- Outages (90 days): 0

## Install

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

Claude Code:

```sh
claude mcp add --transport http sergovashakmadze-iomarkets-tech-mcp-serv https://iomarkets.tech/mcp
```

## Tools (24)

- `check_token_contract`: 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, othe
- `estimate_data_api_cost`: 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; route
- `explain_execution_request`: 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 
- `explain_issue`: 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.
- `explain_term`: 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 a
- `get_api_status`: Whether the Data API at https://api.iomarkets.tech is answering right now, from its /health check.
- `get_corporate_action`: 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 2002
- `get_guide`: Step-by-step instructions, with the exact button names, for one task on iomarkets.tech (checking a message, CI, reconciling a statement, checking a token…). Wit
- `get_overview`: 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 wh
- `get_roadmap`: What IoMarkets.tech has built and is building next, in the same words as iomarkets.org/roadmap.
- `get_sample`: 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.
- `get_tokenized_asset`: 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
- `holdings_calendar`: 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`, Mo
- `list_corporate_actions`: 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
- `list_data_endpoints`: 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 acc
- `list_messages`: The ISO 20022 message types and versions the Test Bench checks, with what each is for.
- `list_samples`: 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.
- `list_tokenized_assets`: 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 
- `reconcile_statement`: Match an ISO 20022 bank statement (camt.053.001.08) or notification (camt.054.001.08) against the payments you expected (open invoices, a payment run, a ledger 
- `token_corporate_actions`: 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
- `validate_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.0
- `verify_asset_with_issuer`: 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 
- `verify_execution_report`: Check the whole JSON that POST https://api.iomarkets.tech/v1/proof/execution returned ({ audit, summary, attestation }): that the ed25519 signature matches the 
- `verify_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 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
