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.

Rizon

REMOTE · RIZON.MARKETS

A paper-money exchange: read live order books, place practice trades, test a bot. No sign-up.

Available components

+5 this week 72 Trust /100

Last scanned (22 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 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 Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 832 tokens (~83/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 19 Nov 26 +3
    • HSTS header: fail → pass ▲ security
  • 17 Nov 26 +1

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

  • 14 Nov 26 +1

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

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 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.

  • 7 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://rizon.markets/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rizon.markets CN=YE2,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA384 588d88e8ab97c4e09348084fa40929e5161
SANs: rizon.markets
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of rizon.markets. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
markets. DS published 64757 8 Verified
rizon.markets. No DS 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=31536000; includeSubDomains
content-security-policy default-src 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://rizon.markets/mcp Verified 200
http (plaintext) http://rizon.markets/mcp HTTPS enforced 301 https://rizon.markets/mcp
MCP tools · 10 exposed · ~755 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
cancel_orders ~65

Cancels your resting orders, on one market or side if you name it.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.
marketstring–A market id
sidestring–up or down

No output schema declared.

No examples provided.

create_account ~64

A new paper account with $1,000 and its API key, shown once. Pass the key to the tools below, or set it as this server’s bearer token.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.

No output schema declared.

No examples provided.

get_account ~46

Your balance, what’s in orders and positions, realised PnL and rank.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.

No output schema declared.

No examples provided.

get_book ~75

One market’s order book: up to 30 levels a side, and its midpoint, the market’s forecast of the number. No key needed.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.
marketstringyesA market id, like BTC-15s

No output schema declared.

No examples provided.

get_leaderboard ~69

Every account that has traded, ranked by realised PnL, people and bots alike. No key needed.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.
limitnumber–1 to 100, default 20

No output schema declared.

No examples provided.

get_orders ~57

Your orders. Open ones by default.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.
marketstring–A market id
statusstring–open or all

No output schema declared.

No examples provided.

get_positions ~59

Your positions. Open ones by default.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.
marketstring–A market id
statusstring–open, settled or all

No output schema declared.

No examples provided.

get_prices ~98

An underlying’s price history as [time, price] pairs. No key needed.

NameTypeReqDescription
fromnumber–Start, ms since the epoch
keystring–Your rz_ API key, if this server has no bearer token set.
stepnumber–Bucket size, ms
tonumber–End, ms since the epoch
underlyingstringyesAn underlying id, like BTC-USD

No output schema declared.

No examples provided.

list_markets ~59

Every market: its number, spot, best bid and ask (strikes), one-sigma move, rules and status. No key needed.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.

No output schema declared.

No examples provided.

place_order ~163

Places an order with paper money. side up buys Higher: it wins if the number finishes above the strike. side down sells: it holds Lower. A win pays 2× size. Leave out strike for a market order.

NameTypeReqDescription
keystring–Your rz_ API key, if this server has no bearer token set.
marketstringyesA market id, like BTC-15s
sidestringyesup or down
sizenumberyesPaper dollars, 1 to 100,000
strikenumber–Makes it a limit order, on the market’s strike grid
tifstring–gtc (rests), ioc (takes what it can) or post (only ever rests)

No output schema declared.

No examples provided.

Install

How do I install the Rizon MCP server?

Rizon is a hosted endpoint at https://rizon.markets/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 · rizon.markets

# add to Claude Code
claude mcp add --transport http markets-rizon-exchange 'https://rizon.markets/mcp'
Common questions

What is the Rizon MCP server?

Rizon is an MCP server listed in the public MCP registry as markets.rizon/exchange. A paper-money exchange: read live order books, place practice trades, test a bot. No sign-up. This page covers its hosted endpoint (https://rizon.markets/mcp).

Is the Rizon MCP server safe to use?

Rizon 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 Rizon MCP server expose?

Rizon exposes 10 tools: list_markets, get_book, get_prices, get_leaderboard, create_account, and 5 more. Their descriptions and schemas cost roughly 755 tokens of context every time the server is loaded.

Does the Rizon MCP server require authentication?

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

Is the Rizon MCP server still maintained?

Rizon is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Rizon MCP server?

VerifyMCP ran 12 checks on Rizon, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Rizon: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.