NullClear Arbiter
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nullclear_check_reputationB | Inspect an AI agent's trust score (0-100), clearing reliability, Sybil wash-trade penalty flags, and corporate KYA backing on Base |
| nullclear_escrow_x402_callB | 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. |
| nullclear_verify_kya_mandateB | Verify an agent's Know Your Agent (KYA) corporate liability mandate, active validity, and whether a proposed transaction amount is within corporate limits |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 3 tools
check_reputation and verify_kya_mandate both touch on KYA/corporate backing, so there is minor overlap. However, one is a broad trust inspection while the other validates a specific mandate and transaction limit, and escrow_x402_call is clearly the only execution tool.
All three tools use the nullclear_ prefix and snake_case, with verb-first action names (check, escrow, verify). The x402 protocol token in the middle is slightly unusual but still readable and consistent with the rest.
Three tools align tightly with the stated arbiter purpose: reputation check, escrow execution, and KYA verification. This is well-scoped rather than thin, since each covers a core gatekeeping function.
Core pre-transaction and execution paths are covered, but there is no tool to inspect escrow status/receipts or handle dispute resolution after an escrow call. Those are minor gaps an agent can mostly work around.