mcpbeat Sign in

x207 MCP Server

by x207-labs Your server? Claim it
answering

x207 is answering right now. Last checked moments ago. 1 114 installs a week from npm. It exposes 6 tools.

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

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 572 · avg 37
a month agotoday
Uptime history 4 days of history · worst day 0%
4 days agonow
49.7%
Uptime 24h
91 of 183 checks
6
Tools
read from the server
430 ms
Response time
average over 24h
1 114
Installs / week
npm and PyPI

x207 does not always answer

Over the last week it answered 40.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add x207-mcp --transport http https://mcp.x207.boxd.sh/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.x207.boxd.sh/mcp
~/.codex/config.toml
[mcp_servers.x207-mcp]
url = "https://mcp.x207.boxd.sh/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "x207-mcp": {
      "url": "https://mcp.x207.boxd.sh/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "x207-mcp": {
      "type": "http",
      "url": "https://mcp.x207.boxd.sh/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

x207
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.
x207_epoch_report
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`.
x207_member_inspect
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.
x207_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).
x207_search_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.
x207_simulate_clearing
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.

Endpoints

URLTransportStateLatencyChecked
https://x207-mcp-production.up.railway.app/mcp streamable-http answering 357 ms 0 min ago
https://mcp.x207.boxd.sh/mcp streamable-http answering 471 ms 14 min ago

Alternatives to x207

same job, measured the same way
A2me MCP Server
by kinnectd

Read-only A2Me family context tools for AI assistants (members, dates, activity, relationships)

answering
MVisionPro Engineering Tools
by mvisionpro

Read-only machine-vision calculations for optics, interfaces, line scan, sensors, and models.

6 tools answering
Etsy MCP Server
by profplum700

A local read-only MCP server for Etsy shops, active listings, and listing variation inventory.

61 installs/wk local only
ObraAberta
by com-obraaberta

Read-only MCP tools for public works, builders, ratings, timelines and nearby services in Brazil.

11 tools answering
Hostaway
by uncfreak1255-code

Read-only MCP server for Hostaway PMS — guest conversations, reservations, and listings

45 installs/wk local only
LION Trend Intent MCP
by lionmaster20

Read-only x402-paid trend-intent MCP tools for JSON and CSV signals.

5 tools answering
PortDock MCP
by portdock

Read-only tools for COM ports, Modbus, MC and SCPI on Windows, plus writes to local simulators only

local only
Driverfile
by artificl

DOT driver qualification file tracking for small motor carriers — read-only demo tools.

5 tools answering

x207 — questions

Answers built from our own checks of this server.

What can x207 do?
It exposes 6 tools, read directly from the server on our last check. Among them: x207_circle_overview, x207_epoch_report, x207_member_inspect, x207_order_status, x207_search_listings, x207_simulate_clearing. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is x207 working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 183 checks got a reply (49.7%), average response time 430 ms. The bar chart above shows every period we have measured.
Is x207 still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect x207?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does x207 need an API key?
No. x207 completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is x207?
It answers our handshake in 430 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use x207?
The npm package @x207/mcp was installed 1 114 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.