Home / MCP registry index / io.github.ParallaxProtocol/parallax-mcp

Parallax Protocol

io.github.ParallaxProtocol/parallax-mcp in the official MCP registry. Endpoint https://mcp.parallaxprotocol.org/mcp. Source: github.com/ParallaxProtocol/parallax-mcp.

The registry describes it as: Read-only Parallax PoW chain data: blocks, transactions, mining, supply, explorer and network health

We read its 36 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http parallax-mcp https://mcp.parallaxprotocol.org/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "parallax-mcp": {
      "url": "https://mcp.parallaxprotocol.org/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"parallax-mcp","type":"http","url":"https://mcp.parallaxprotocol.org/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

audit_token_approvals block_reward call_contract chain_info estimate_gas explorer_address explorer_charts explorer_contract explorer_internal_transactions explorer_search explorer_stats explorer_token explorer_token_balances explorer_token_holders explorer_token_transfers explorer_transactions gas_price get_balance get_block get_code get_logs get_proof get_receipt get_storage_at get_transaction mempool_status mining_stats network_health network_incidents network_nodes network_propagation network_trends read_doc search_docs supply_info wait_for_new_block

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-parallaxprotocol-parallax-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-parallaxprotocol-parallax-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Health MCP servers

Good Turn Studio (all tools)
io.github.GoodTurnStudio/all
162 tools, nothing matched
2026-10-27
com.medigami/mcp
com.medigami/mcp
87 tools, nothing matched
2026-10-27
ch.swisslivingindex/swiss-living-index
ch.swisslivingindex/swiss-living-index
72 tools, nothing matched
2026-10-26
Fda Devices
io.github.pipeworx-io/fda-devices
53 tools, nothing matched
2026-10-27
Framezone
app.framezone/framezone
50 tools, nothing matched
2026-10-22
Hsa Singapore
io.github.pipeworx-io/hsa-singapore
48 tools, nothing matched
2026-10-27