# x207 (remote · mcp.x207.boxd.sh)

Read-only tools for x207 circles on NEAR: members, epochs, clearing simulation, listings.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.x207.boxd.sh`: 73/100 (this document), [markdown](https://verifymcp.io/servers/x207-labs-x207-mcp/mcp.md), [page](https://verifymcp.io/servers/x207-labs-x207-mcp/mcp)
- npm · `@x207/mcp`: 28/100, [markdown](https://verifymcp.io/servers/x207-labs-x207-mcp/x207-mcp.md), [page](https://verifymcp.io/servers/x207-labs-x207-mcp/x207-mcp)

## Channel facts

- Endpoint: `https://mcp.x207.boxd.sh/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.6`

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

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1200 tokens (~200/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: 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 x207 MCP server?

x207 is a hosted endpoint at https://mcp.x207.boxd.sh/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 x207-labs-x207-mcp 'https://mcp.x207.boxd.sh/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "x207-labs-x207-mcp": {
      "url": "https://mcp.x207.boxd.sh/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "x207-labs-x207-mcp": {
      "type": "http",
      "url": "https://mcp.x207.boxd.sh/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.x207-labs-x207-mcp]
url = "https://mcp.x207.boxd.sh/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "x207-labs-x207-mcp": {
      "type": "remote",
      "url": "https://mcp.x207.boxd.sh/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add x207-labs-x207-mcp --url 'https://mcp.x207.boxd.sh/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  x207-labs-x207-mcp:
    url: "https://mcp.x207.boxd.sh/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "x207-labs-x207-mcp": {
      "Transport": "http",
      "Url": "https://mcp.x207.boxd.sh/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add x207-labs-x207-mcp -t streamable-http -u 'https://mcp.x207.boxd.sh/mcp'
```

### Other

```json
{
  "mcpServers": {
    "x207-labs-x207-mcp": {
      "type": "http",
      "url": "https://mcp.x207.boxd.sh/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-11-05 (score 73)

First indexed and scored.

## MCP tools (6)

### `x207_circle_overview` (~199 tokens)

x207 circle overview

Start here: the circle itself, i.e. its record and rules (get_circle, get_params) plus a page of its members (read API GET /members, or the contract view list_members when no read API is set). Use x207_member_inspect for one member in detail and x207_epoch_report for one epoch. Returns {contract, circleId, circle, params, members, membersSource, warnings}; amounts are strings in the smallest unit (6 decimals). If the members part fails it shows up in `warnings` and the rest is still returned; an unreachable contract RPC is an error.

Input parameters:

- `members_limit` (integer): Size of the members page, 1 to 200 (default 20); the circle may have more members than this.
- `members_status` (string): Keep only members with this status, e.g. active, suspended or exiting. Read API only; ignored on the contract fallback.

### `x207_member_inspect` (~162 tokens)

Inspect a circle member

One member of the circle: status, stake, outstanding debt and credit limit (read API GET /members/{account} and /limits, or the contract views member and limit when no read API is set). Use it after x207_circle_overview has shown the account ids, or before paying a member; for epoch-level amounts use x207_epoch_report. Returns {account, member, limits|limit, source, warnings}. An account that is not a member is an error ("not a member" or a 404 from the read API); a failed limits lookup is only a warning.

Input parameters:

- `account` (string, required): The member to look up: its NEAR account id, or for an EVM agent its lower-case 0x address.

### `x207_epoch_report` (~210 tokens)

Epoch report (report 207)

One epoch of the circle: its phase and deadlines from the contract (get_epoch), and from the read API the summary, the metrics (cleared ratio: the share of debt that netting removed, so only the net cash moves) and the settlements, i.e. who owes whom what in cash. Use it after an epoch closed; use x207_simulate_clearing to test a proposal before it is submitted. Returns {epoch, contract, summary, metrics, settlements, source, warnings}. An epoch that does not exist is an error; if the read API is down the contract record is still returned, with the failures in `warnings`.

Input parameters:

- `epoch` (integer): Epoch number, 0 or more. Leave out for the current epoch, which is still open and has no settlements yet.
- `settlements_limit` (integer): How many settlement rows to return, 1 to 200 (default 20). A busy epoch has more; raise it to see them all.

### `x207_simulate_clearing` (~163 tokens)

Simulate a clearing proposal

Dry run of a netting proposal: asks the contract (view simulate_clearing) whether the edges would be accepted for an epoch and how much debt they would cancel. Use it to check a proposal before a solver submits it; to see what a finished epoch actually netted use x207_epoch_report. Returns {epoch, edgeCount, result}. An invalid proposal (unknown member, amount above the debt, wrong epoch phase) comes back as an error text from the contract. Read-only, sends nothing.

Input parameters:

- `edges` (array, required): 1 to 300 debt edges; a cycle of edges nets to zero cash.
- `epoch` (integer, required): The epoch the proposal is for; it must be one that can still accept a clearing.

### `x207_search_listings` (~268 tokens)

Search marketplace listings

Find offers on the circle's marketplace (read API GET /listings): what an account offers and what it wants. Use it to discover who sells a service; for an order that already exists use x207_order_status. Returns {items, nextCursor}; pass nextCursor as `cursor` for the next page. No match gives an empty list, not an error. Needs the read API (X207_BACKEND_URL) and fails with a clear message without it.

Input parameters:

- `account` (string): Only listings of this account.
- `cursor` (string): The nextCursor of the previous page; leave out for the first page.
- `limit` (integer): Page size, 1 to 200 (default 20).
- `offerClass` (string): Settlement class of the offered asset (A to D, X for other); keep only listings of this class.
- `offerType` (string): Asset type the lister offers, e.g. service:summary; exact match.
- `status` (string): Listing state to match; open when left out, all for every state.
- `wantClass` (string): Same, for the wanted asset.
- `wantType` (string): Asset type the lister wants in return, same form as offerType.

### `x207_order_status` (~198 tokens)

Order status

Orders of the circle's marketplace (read API GET /orders). With a hash: one order with its parties, budget, milestones and status. Without a hash: a page of orders, filtered by party and status. Use x207_search_listings to find offers before an order exists. An unknown hash is an error ("no order ... in circle"); an empty list is a normal result. Needs the read API (X207_BACKEND_URL).

Input parameters:

- `cursor` (string): The nextCursor of the previous page; listing only.
- `hash` (string): The order hash. Leave out to list orders.
- `limit` (integer): Page size, 1 to 200 (default 20); listing only.
- `party` (string): Only orders where this account is buyer or seller (listing only).
- `status` (string): Only orders in this state, e.g. open, delivered or disputed (listing only).

## Diagnostics

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

## Score history

- 2026-11-05: 73

## Common questions

### What is the x207 MCP server?

x207 is an MCP server listed in the public MCP registry as io.github.x207-labs/x207-mcp. Read-only tools for x207 circles on NEAR: members, epochs, clearing simulation, listings. This page covers its hosted endpoint (https://mcp.x207.boxd.sh/mcp).

### Is the x207 MCP server safe to use?

x207 scores 73 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 x207 MCP server expose?

x207 exposes 6 tools: x207_circle_overview, x207_member_inspect, x207_epoch_report, x207_simulate_clearing, x207_search_listings, x207_order_status. Their descriptions and schemas cost roughly 1,200 tokens of context every time the server is loaded.

### Does the x207 MCP server require authentication?

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

### Is the x207 MCP server still maintained?

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

## Links

- Remote endpoint: https://mcp.x207.boxd.sh/mcp
- Repository: https://github.com/x207-labs/sdk
- Website: https://github.com/x207-labs/x207#readme
- Changelog RSS feed: https://verifymcp.io/servers/x207-labs-x207-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/x207-labs-x207-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/x207-labs-x207-mcp/mcp