NullClear Arbiter
REMOTE · API.NULLCLEAR.DEV · 2 COMPONENTS
Autonomous x402 payment schema-escrow arbiter, spend firewall, failover & ERC-8004 Sybil oracle
Available components
Last scanned (8 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 494 tokens (~98/item across 5 items; 3 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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 +10
- Authorization: unverified → partial ▲ security
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fail → pass ▲ functional
- First check of Schema quality: 100 functional
- Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
- New prompt “audit-erc8004-agent” functional
- New prompt “safe-x402-payment” functional
- New resource “NullClear Live Protocol Telemetry” functional
- New resource “NullClear Quickstart Guide” functional
- “nullclear_check_reputation” reworded the description of “agentId” cosmetic
- 16 Oct 26 54
First indexed and scored.
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 · Probed https://api.nullclear.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nullclear.dev | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 36da5ca293471c7d136653d0997c930f |
| SANs: nullclear.dev, api.nullclear.dev, *.api.nullclear.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.nullclear.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| nullclear.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.nullclear.dev/mcp | Verified | 200 | |
| http (plaintext) | http://api.nullclear.dev/mcp | Served over HTTP | 200 |
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 →
nullclear_check_reputation ~92
Inspect an AI agent's trust score (0-100), clearing reliability, Sybil wash-trade penalty flags, and corporate KYA backing on Base
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | The ERC-8004 agent token ID or registered identifier (e.g. '124595') |
| chainId | number | – | Base chain ID (8453 for Mainnet, 84532 for Sepolia) |
No output schema declared.
No examples provided.
nullclear_escrow_x402_call ~255
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fallbacks | array | – | Ordered fallback candidates for autonomous multi-seller failover routing (max 3) |
| invariants | array | – | Deep value invariants (numeric bounds, regex, forbidden substrings, timestamp freshness) |
| jsonSchema | object | – | JSON Schema draft-07 contract that response must strictly satisfy |
| method | string | – | – |
| minTrustScore | number | – | Minimum acceptable trust score for seller (0-100, default 50) |
| rejectRefusals | boolean | – | Reject canonical LLM refusal strings (default: true) |
| requiredFields | array | – | Field paths that must exist in response |
| sellerAgentId | string | – | Seller's agent ID for reputation check and Sybil wash-trade gating |
| spendPolicy | object | – | Outbound spend firewall limits (maxPerCallAtomic, maxDailyWalletAtomic) |
| targetUrl | string | yes | Upstream 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
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | The ERC-8004 agent token ID |
| chainId | number | – | Base chain ID (default 8453) |
| transactionAmountUsd | number | yes | Amount in USD intended to spend in the transaction |
No output schema declared.
No examples provided.
How do I install the NullClear Arbiter MCP server?
NullClear Arbiter is a hosted endpoint at https://api.nullclear.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.nullclear.dev
claude mcp add --transport http mithgalalfayez-nullclear 'https://api.nullclear.dev/mcp'
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 hosted endpoint (https://api.nullclear.dev/mcp).
Is the NullClear Arbiter MCP server safe to use?
NullClear Arbiter scores 64 out of 100 on VerifyMCP. 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 440 tokens of context every time the server is loaded.
Does the NullClear Arbiter MCP server require authentication?
No. We connected to NullClear Arbiter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.