Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IoMarkets.ai guide

REMOTE · IOMARKETS.AI

Guide to IoMarkets.ai Federated Computing: receipt checks, runs, costs and evaluation requests.

Available components

+1 this week 72 Trust /100

Last scanned (4 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 625 tokens (~89/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management12
  • Stability check failed: schema churn in the 11 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.

  • 28 Oct 26 −1
    • Stability: 0.07 → fail ▼ security
    • Tool “get_api_status” was removed ▼ security
    • Tool “list_data_endpoints” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “explain_term” rewrote its description, which is the text the model reads security
    • Tool “get_overview” rewrote its description, which is the text the model reads security
    • Schema quality: 80 → 89 ▼ functional
    • Server version: 1.0.0 → 1.1.0 functional
  • 27 Oct 26 +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.

  • 26 Oct 26 0
    • Schema quality: 72 → 80 ▼ functional
    • Tool coverage: 80% → 86% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “estimate_cost” functional
  • 25 Oct 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://iomarkets.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=iomarkets.ai CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 63cc6073670ad9870e845c5a1d946a94
SANs: iomarkets.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of iomarkets.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
iomarkets.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=300

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://iomarkets.ai/mcp Verified 200
http (plaintext) http://iomarkets.ai/mcp HTTPS enforced 301 https://iomarkets.ai/mcp
MCP tools · 7 exposed · ~552 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
draft_evaluation_request ~155

Turn what someone wants to evaluate, in their own words, into a Federated Computing evaluation request. Returns the message and a link that opens it in their email app; nothing is sent for them, and they can also use the form. Ask for anything missing, one question at a time, before calling it.

NameTypeReqDescription
assetsstring–The kind of model or data (optional).
constraintsstring–Regions, confidentiality, timing (optional).
emailstringyesWhere the reply should go.
goalstringyesWhat they want to evaluate, in a sentence or two.
namestringyes–
organisationstringyes–
rolestringyesTheir role.

No output schema declared.

No examples provided.

estimate_cost ~143

What Federated Computing runs cost in confidential cloud time, at Google Cloud list prices, for the machines and run times the real runs used, plus key services. Same numbers as the cost estimator page. An estimate, not a quote.

NameTypeReqDescription
key_servicesnumber–Key services, one per data or model owner. Default 2.
kindstringyestabular-cpu (credit, fraud, risk models), tabular-tdx, gpu-small, or gpu-llm-14b.
monthsnumber–Months the key services stay up. Default 3.
runsnumber–How many runs. Default 1.

No output schema declared.

No examples provided.

explain_term ~61

A plain-English meaning of a word used on the site: digital signature, invoice, Federated Computing, confidential hardware, attestation, receipt, AI agent, MCP. Without a word, lists them all.

NameTypeReqDescription
termstring–The word to explain.

No output schema declared.

No examples provided.

get_guide ~53

Step-by-step instructions, with the exact button names, for one task on iomarkets.ai. Without a task, lists the tasks.

NameTypeReqDescription
taskstring–Which task. Leave out to list them all.

No output schema declared.

No examples provided.

get_overview ~41

What IoMarkets.ai is and what is built: Federated Computing (private computing across organisations on confidential hardware), with the main pages and what is a demonstration.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_run ~65

One Federated Computing run in detail: what it showed, the model and data, hardware, location, result, payment, and whether its receipt verifies (checked now, with the same code as the receipt checker).

NameTypeReqDescription
idstringyesThe run id, from list_runs.

No output schema declared.

No examples provided.

list_runs ~34

Every Federated Computing run done on confidential hardware, newest first: its id, what it showed and the hardware it ran on.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the IoMarkets.ai guide MCP server?

IoMarkets.ai guide is a hosted endpoint at https://iomarkets.ai/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.

remote · iomarkets.ai

# add to Claude Code
claude mcp add --transport http sergovashakmadze-iomarkets-ai 'https://iomarkets.ai/mcp'
Common questions

What is the IoMarkets.ai guide MCP server?

IoMarkets.ai guide is an MCP server listed in the public MCP registry as io.github.SergoVashakmadze/iomarkets-ai. Guide to IoMarkets.ai Federated Computing: receipt checks, runs, costs and evaluation requests. This page covers its hosted endpoint (https://iomarkets.ai/mcp).

Is the IoMarkets.ai guide MCP server safe to use?

IoMarkets.ai guide scores 72 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.ai guide MCP server expose?

IoMarkets.ai guide exposes 7 tools: get_overview, get_guide, explain_term, list_runs, get_run, and 2 more. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.

Does the IoMarkets.ai guide MCP server require authentication?

No. We connected to IoMarkets.ai guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the IoMarkets.ai guide MCP server still maintained?

IoMarkets.ai guide 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.