x207
REMOTE · MCP.X207.BOXD.SH · 2 COMPONENTS
Read-only tools for x207 circles on NEAR: members, epochs, clearing simulation, listings.
Available components
Last scanned (54 minutes ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 653 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
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.
- 5 Nov 26 72
First indexed and scored.
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://mcp.x207.boxd.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.x207.boxd.sh | CN=WR1,O=Google Trust Services,C=US | 5 Nov 2026 | 3 Feb 2027 | ECDSA 256 | SHA256-RSA | 36593c430dd6c77b19f32bd0a001af83 |
| SANs: *.x207.boxd.sh | ||||||
| CN=WR1,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 | 7fd9e2c2d2048a0474b627a26d0868a7 |
| 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 mcp.x207.boxd.sh. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 34349 | 8 | Verified |
| boxd.sh. | 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=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.x207.boxd.sh/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.x207.boxd.sh/mcp | HTTPS enforced | 301 | https://mcp.x207.boxd.sh/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 →
x207_circle_overview x207 circle overview ~112
Overview of one x207 mutual-credit circle: its record and rules from the contract (get_circle, get_params) and its members (read API GET /members, or the contract view list_members when no read API is configured). Credit amounts are strings in the smallest unit (6 decimals).
| Name | Type | Req | Description |
|---|---|---|---|
| members_limit | integer | – | How many items, 1 to 200 (default 20). |
| members_status | string | – | Only members with this status, e.g. active (read API only). |
No output schema declared.
No examples provided.
x207_epoch_report Epoch report (report 207) ~116
The state and the result of one clearing epoch: the contract record (get_epoch) and, from the read API, the epoch summary (GET /epochs/{n}), its metrics (cleared ratio, GET /epochs/{n}/metrics) and its settlements (GET /epochs/{n}/settlements). Without epoch, the current epoch.
| Name | Type | Req | Description |
|---|---|---|---|
| epoch | integer | – | Epoch number; the current epoch when left out. |
| settlements_limit | integer | – | How many items, 1 to 200 (default 20). |
No output schema declared.
No examples provided.
x207_member_inspect Inspect a circle member ~66
One member of the circle: status, stake, position and credit limit. Uses the read API (GET /members/{account} and /members/{account}/limits), or the contract views member and limit when no read API is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | – |
No output schema declared.
No examples provided.
x207_order_status Order status ~128
A service order of the circle's marketplace: parties, budget, milestones and status (read API GET /orders/{hash}). Without a hash, lists orders; filter by `party` and `status`.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| hash | string | – | The order hash. Leave out to list orders. |
| limit | integer | – | How many items, 1 to 200 (default 20). |
| party | string | – | Only orders where this account is buyer or seller (listing only). |
| status | string | – | Only orders with this status (listing only). |
No output schema declared.
No examples provided.
x207_search_listings Search marketplace listings ~149
Listings of the circle's marketplace (read API GET /listings): what an account offers and what it wants. Filters are optional; `status` defaults to open. Use `cursor` from `nextCursor` for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Only listings of this account. |
| cursor | string | – | – |
| limit | integer | – | How many items, 1 to 200 (default 20). |
| offerClass | string | – | – |
| offerType | string | – | Asset type offered, e.g. service:summary. |
| status | string | – | Default open. |
| wantClass | string | – | – |
| wantType | string | – | – |
No output schema declared.
No examples provided.
x207_simulate_clearing Simulate a clearing proposal ~82
Asks the contract (view simulate_clearing) whether a proposed clearing for an epoch is valid and what it would clear. Each edge nets a debt: debtor owes creditor, `cleared` is the amount to cancel (decimal string, smallest unit). Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| edges | array | yes | – |
| epoch | integer | yes | – |
No output schema declared.
No examples provided.
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.
remote · mcp.x207.boxd.sh
claude mcp add --transport http x207-labs-x207-mcp 'https://mcp.x207.boxd.sh/mcp'
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 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 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 653 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.