Symbol (XYM) runs on your own machine — the client starts it, so there is no endpoint to ping. 204 installs a week from npm. Last commit 26 Oct 2026.
Read-only MCP server for the Symbol blockchain (XYM): node health, harvesting, voting keys.
We read the source, 6 d ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
r = subprocess.run(["git", "--no-pager", "-c", "core.fsmonitor=", "-c", "core.hooksPath=/dev/null"] + args,
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
r = subprocess.run(["git", "--no-pager", "-c", "core.fsmonitor=", "-c", "core.hooksPath=/dev/null"] + args,
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Symbol (XYM) and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add symbol -e 'SYMBOL_NODE_URL=<SYMBOL_NODE_URL>' -- npx -y symbol-mcp-server
{
"mcpServers": {
"symbol": {
"command": "npx",
"args": [
"-y",
"symbol-mcp-server"
],
"env": {
"SYMBOL_NODE_URL": "<SYMBOL_NODE_URL>"
}
}
}
}
[mcp_servers.symbol]
command = "npx"
args = ["-y", "symbol-mcp-server"]
env = { SYMBOL_NODE_URL = "<SYMBOL_NODE_URL>" }
{
"mcpServers": {
"symbol": {
"command": "npx",
"args": [
"-y",
"symbol-mcp-server"
],
"env": {
"SYMBOL_NODE_URL": "<SYMBOL_NODE_URL>"
}
}
}
}
{
"servers": {
"symbol": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"symbol-mcp-server"
],
"env": {
"SYMBOL_NODE_URL": "<SYMBOL_NODE_URL>"
}
}
}
}
Put your own value in place of
<SYMBOL_NODE_URL> (REST URL of the Symbol node to query, e.g. https://<node-host>:3001; https:// is required (http:// only for localhost / 127.0.0.1 / [::1]) and the port is used exactly as given).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
SYMBOL_NETWORK (mainnet or testnet; when set, start-up fails if the node reports a different network), SYMBOL_TIMEZONE (IANA zone such as Asia/Tokyo that adds a local time next to every UTC timestamp), SYMBOL_REFERENCE_NODES (Comma-separated https:// node URLs that symbol_network_compare and symbol_version_drift check against; no other host is ever contacted), SYMBOL_REQUEST_TIMEOUT_MS (Per-request timeout in milliseconds, 100 to 600000 (default 10000)), SYMBOL_STATE_DIR (Absolute directory where symbol_harvesting_status keeps one snapshot file per node (unlocked harvester public keys, heights and times; no secrets) when it is asked to compare or save, created on first save with mode 0700; when unset, the tool reports the current list without a comparison).
MCP server for the Chia blockchain. Read-only full-node access via Coinset hosted nodes, 36 tools.
MCP server for the Chia blockchain. Read-only Q&A via the public coinset.org API.
Read-only MCP server for querying the live NOVAI blockchain over its public JSON-RPC endpoint.
MCP server for creating vtimestamp proofs on the Verus blockchain via a local or remote daemon
MCP server for verifying and querying vtimestamp proofs on the Verus blockchain
Read-only MCP server for UK gym search using the LocalGym Agent API.
Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.
MCP Server for Rootstock Blockchain
Answers built from our own checks of this server.