Home / MCP registry index / io.github.mithgalalfayez/nullclear

NullClear Arbiter

io.github.mithgalalfayez/nullclear in the official MCP registry. Endpoint https://api.nullclear.dev/mcp. Source: github.com/Nullclear-Protocol/nullclear.

The registry describes it as: Autonomous x402 payment schema-escrow arbiter, spend firewall, failover & ERC-8004 Sybil oracle

We read its 13 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules.

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 nullclear https://api.nullclear.dev/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "nullclear": {
      "url": "https://api.nullclear.dev/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"nullclear","type":"http","url":"https://api.nullclear.dev/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.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

scan_token_forensics inspect_contract_abi_and_proxy decode_calldata_or_failed_tx simulate_transaction_preflight read_url_clean_markdown nullclear_discover_verified_x402_apis nullclear_token_security_audit nullclear_wallet_risk_score nullclear_crypto_market_oracle nullclear_safe_fetch nullclear_escrow_x402_call nullclear_check_reputation nullclear_verify_kya_mandate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

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

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.

Crypto and Web3 MCP servers