paired.exchange
REMOTE · PAIRED.EXCHANGE · 2 COMPONENTS
Launch coins quoted in tokenized stocks on Robinhood Chain; the user signs at a launch link.
Available components
Last scanned (1 hour ago)
Scores higher than 6% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Crypto and Web3
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 23 Oct 26 −55
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 23 to 33. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 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.
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 25 Oct 2026 · Probed https://paired.exchange/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=paired.exchange | CN=WR3,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 2048 | SHA256-RSA | b34ec3921254861d0926c864f8c3655f |
| SANs: paired.exchange, www.paired.exchange | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of paired.exchange. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| exchange. | present | 46084 | 8 | Verified |
| paired.exchange. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://paired.exchange/mcp | HTTP error | 404 | |
| http (plaintext) | http://paired.exchange/mcp | HTTPS enforced | 301 | https://paired.exchange:443/mcp |
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 →
claimable_fees Claimable fees ~39
Creator fees a wallet can claim right now, per stock. Claiming is one transaction on the portfolio page.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | – |
No output schema declared.
No examples provided.
fee_schedule Fees ~30
The launch fee, the swap fee, and the creator share of swap fees, read live from the contract.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_coin Coin details ~43
One coin: its price and curve in every paired market, how much each curve has raised, its creator and where it was launched from.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
launch_status Check a planned launch ~35
Whether a planned launch has been signed yet, and the coin address and links once it has.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_id | string | yes | – |
No output schema declared.
No examples provided.
list_coins Coins ~68
Launched coins, newest first, with their stock pairings. Optionally only coins launched from an assistant, or only coins in one market.
| Name | Type | Req | Description |
|---|---|---|---|
| from_assistant | boolean | – | – |
| limit | number | – | – |
| market | string | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
list_markets Stock markets ~29
The tokenized stocks a coin can be paired against, with their token addresses on Robinhood Chain.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
plan_launch Plan a coin launch ~123
Validate a new coin and return a launch link. The user signs and pays the launch fee from their own wallet at that link; this tool never deploys or spends anything.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| dev_buy | string | – | – |
| fee_wallet | string | – | – |
| image_url | string | – | – |
| markets | array | yes | – |
| name | string | yes | – |
| symbol | string | yes | – |
| telegram | string | – | – |
| string | – | – | |
| website | string | – | – |
| weights | array | – | – |
No output schema declared.
No examples provided.
quote_trade Price a trade ~64
Price a buy or sell against one of a coin's stock markets before committing. A buy spends the stock; a sell spends the coin.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| amount | string | yes | – |
| market | string | – | – |
| side | string | yes | – |
No output schema declared.
No examples provided.
How do I install the paired.exchange MCP server?
paired.exchange is a hosted endpoint at https://paired.exchange/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 · paired.exchange
claude mcp add --transport http nirholas-paired 'https://paired.exchange/mcp'
What is the paired.exchange MCP server?
paired.exchange is an MCP server listed in the public MCP registry as io.github.nirholas/paired. Launch coins quoted in tokenized stocks on Robinhood Chain; the user signs at a launch link. This page covers its hosted endpoint (https://paired.exchange/mcp).
Is the paired.exchange MCP server safe to use?
paired.exchange scores 23 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 paired.exchange MCP server expose?
paired.exchange exposes 8 tools: list_markets, fee_schedule, list_coins, get_coin, quote_trade, and 3 more. Their descriptions and schemas cost roughly 431 tokens of context every time the server is loaded.
Does the paired.exchange MCP server require authentication?
Its publisher declares no required credentials for paired.exchange. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the paired.exchange MCP server still maintained?
paired.exchange is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.