Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

NullClear Arbiter

NPM · @NULLCLEAR/MCP · 2 COMPONENTS

Autonomous x402 payment schema-escrow arbiter, spend firewall, failover & ERC-8004 Sybil oracle

67 Trust /100

Last scanned (1 hour ago)

Scores higher than 38% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 524 tokens (~174/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.Unverified
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "nullclear_escrow_x402_call" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 3 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: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 17 Oct 26 +28
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.00 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 94 functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: good functional
  • 16 Oct 26 39

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Analysed npm/@nullclear/mcp@1.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 111 packages
Packages resolved 111
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~524 tokens

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 →

Tool Tokens
nullclear_check_reputation ~85

Inspect an AI agent's trust score (0-100), clearing reliability, Sybil wash-trade penalty flags, and corporate KYA backing on Base

NameTypeReqDescription
agentIdstringyesThe ERC-8004 agent token ID or registered identifier
chainIdnumber–Base chain ID (8453 for Mainnet, 84532 for Sepolia)

No output schema declared.

No examples provided.

nullclear_escrow_x402_call ~346

Execute an x402-gated HTTP API call through NullClear deferred schema escrow. The arbiter guarantees payment is only settled if upstream returns valid data matching your schema contract. If the seller hallucinates or crashes, $0 is spent. Users can test immediately against https://api.nullclear.dev/v1/sandbox/market-feed (or fail over from https://api.nullclear.dev/v1/sandbox/hallucinating-seller to https://api.nullclear.dev/v1/sandbox/market-feed) with zero wallet setup.

NameTypeReqDescription
buyerPrivateKeystring–Optional buyer private key (defaults to BUYER_PRIVATE_KEY environment variable)
fallbacksarray–Ordered fallback candidates for autonomous multi-seller failover routing (max 3)
invariantsarray–Deep value invariants (numeric bounds, regex, forbidden substrings, timestamp freshness)
jsonSchemaobject–JSON Schema draft-07 contract that response must strictly satisfy
methodstring––
minTrustScorenumber–Minimum acceptable trust score for seller (0-100, default 50)
rejectRefusalsboolean–Reject canonical LLM refusal strings (default: true)
requiredFieldsarray–Dot-notation field paths that must exist in response (e.g. ['data.price'])
sellerAgentIdstring–Seller's agent ID for reputation check and Sybil wash-trade gating
spendPolicyobject–Outbound spend firewall limits (maxPerCallAtomic, maxDailyWalletAtomic)
targetUrlstringyesUpstream API endpoint demanding x402 payment

No output schema declared.

No examples provided.

nullclear_verify_kya_mandate ~93

Verify an agent's Know Your Agent (KYA) corporate liability mandate, active validity, and whether a proposed transaction amount is within corporate limits

NameTypeReqDescription
agentIdstringyesThe ERC-8004 agent token ID
chainIdnumber–Base chain ID (default 8453)
transactionAmountUsdnumberyesAmount in USD intended to spend in the transaction

No output schema declared.

No examples provided.

Install

How do I install the NullClear Arbiter MCP server?

NullClear Arbiter runs locally as an npm package, launched with npx -y @nullclear/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @nullclear/mcp

# add to Claude Code
claude mcp add mithgalalfayez-nullclear -- npx -y @nullclear/mcp
Common questions

What is the NullClear Arbiter MCP server?

NullClear Arbiter is an MCP server listed in the public MCP registry as io.github.mithgalalfayez/nullclear. Autonomous x402 payment schema-escrow arbiter, spend firewall, failover & ERC-8004 Sybil oracle. This page covers its npm package (@nullclear/mcp).

Is the NullClear Arbiter MCP server safe to use?

NullClear Arbiter scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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 NullClear Arbiter MCP server expose?

NullClear Arbiter exposes 3 tools: nullclear_check_reputation, nullclear_escrow_x402_call, nullclear_verify_kya_mandate. Their descriptions and schemas cost roughly 524 tokens of context every time the server is loaded.

Is the NullClear Arbiter MCP server still maintained?

NullClear Arbiter is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the NullClear Arbiter MCP server under?

NullClear Arbiter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.