# paired.exchange (remote · paired.exchange)

Launch coins quoted in tokenized stocks on Robinhood Chain; the user signs at a launch link.

- Trust score: 23/100 (low)
- Change this week: −54
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `paired.exchange`: 23/100 (this document), [markdown](https://verifymcp.io/servers/nirholas-paired/paired.md), [page](https://verifymcp.io/servers/nirholas-paired/paired)
- npm · `paired-mcp`: 43/100, [markdown](https://verifymcp.io/servers/nirholas-paired/paired-mcp.md), [page](https://verifymcp.io/servers/nirholas-paired/paired-mcp)

## Channel facts

- Endpoint: `https://paired.exchange/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-10-25.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http nirholas-paired 'https://paired.exchange/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nirholas-paired": {
      "url": "https://paired.exchange/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nirholas-paired": {
      "type": "http",
      "url": "https://paired.exchange/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nirholas-paired]
url = "https://paired.exchange/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nirholas-paired": {
      "type": "remote",
      "url": "https://paired.exchange/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nirholas-paired --url 'https://paired.exchange/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nirholas-paired:
    url: "https://paired.exchange/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nirholas-paired": {
      "Transport": "http",
      "Url": "https://paired.exchange/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nirholas-paired -t streamable-http -u 'https://paired.exchange/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nirholas-paired": {
      "type": "http",
      "url": "https://paired.exchange/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-10-23 (score 23, −55)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.73 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-21 (score 78, +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.

### 2026-10-18 (score 77, +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.

### 2026-10-16 (score 76, +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.

### 2026-10-14 (score 75, +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.

### 2026-10-12 (score 74, +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.

### 2026-10-10 (score 73, +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.

### 2026-10-06 (score 71, +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.

## MCP tools (8)

### `list_markets` (~29 tokens)

Stock markets

The tokenized stocks a coin can be paired against, with their token addresses on Robinhood Chain.

### `fee_schedule` (~30 tokens)

Fees

The launch fee, the swap fee, and the creator share of swap fees, read live from the contract.

### `list_coins` (~68 tokens)

Coins

Launched coins, newest first, with their stock pairings. Optionally only coins launched from an assistant, or only coins in one market.

Input parameters:

- `from_assistant` (boolean)
- `limit` (number)
- `market` (string)
- `offset` (number)

### `get_coin` (~43 tokens)

Coin details

One coin: its price and curve in every paired market, how much each curve has raised, its creator and where it was launched from.

Input parameters:

- `address` (string, required)

### `quote_trade` (~64 tokens)

Price a trade

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.

Input parameters:

- `address` (string, required)
- `amount` (string, required)
- `market` (string)
- `side` (string, required)

### `claimable_fees` (~39 tokens)

Claimable fees

Creator fees a wallet can claim right now, per stock. Claiming is one transaction on the portfolio page.

Input parameters:

- `wallet` (string, required)

### `plan_launch` (~123 tokens)

Plan a coin launch

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.

Input parameters:

- `description` (string)
- `dev_buy` (string)
- `fee_wallet` (string)
- `image_url` (string)
- `markets` (array, required)
- `name` (string, required)
- `symbol` (string, required)
- `telegram` (string)
- `twitter` (string)
- `website` (string)
- `weights` (array)

### `launch_status` (~35 tokens)

Check a planned launch

Whether a planned launch has been signed yet, and the coin address and links once it has.

Input parameters:

- `draft_id` (string, required)

## Diagnostics

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

## Score history

- 2026-10-25: 23
- 2026-10-24: 23
- 2026-10-23: 23
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 74
- 2026-10-12: 74
- 2026-10-10: 73
- 2026-10-07: 71
- 2026-10-06: 71
- 2026-10-04: 70
- 2026-10-03: 70
- 2026-10-02: 69
- 2026-10-01: 69
- 2026-09-30: 68

## Common questions

### 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.

## Links

- Remote endpoint: https://paired.exchange/mcp
- Repository: https://github.com/nirholas/paired.exchange
- Changelog RSS feed: https://verifymcp.io/servers/nirholas-paired/paired.xml
- Changelog JSON feed: https://verifymcp.io/servers/nirholas-paired/paired.json
- HTML version of this page: https://verifymcp.io/servers/nirholas-paired/paired