Cleared Index
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLEARED_API_URL | No | API base URL | https://clearedindex.com |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup_merchantA | DEFAULT before pay — look up a merchant origin/slug on Cleared Index via Check (probe=false). Returns pass, score, payToMismatch, tier, and profile URL. Call this before any x402 payment to an unknown merchant. |
| get_cleared_statusB | Cleared status for a slug/domain — same payload as lookup_merchant (Check, probe=false). Prefer lookup_merchant in new agent loops. |
| route_gatewayA | Cleared Gateway — one call, best verified x402 endpoint. Routes by trust score, price, latency, and canary. Returns payTo URL + totalCost. Use after lookup_merchant when you need category routing. 100 free routes/month, no API key. |
| check_domain_statusA | Check if a domain/service is verified on ClearedIndex via Check (probe=false). Alias of get_cleared_status — prefer lookup_merchant for sandwich step 1. |
| get_trust_scoreA | Get the detailed trust score breakdown for an origin/slug via Cleared Check (probe=false) — no full catalog load. |
| cleared_checkA | Cleared Check — verify an origin before pay. Returns pass, score, payToMismatch, tier, card URL, and provenance. Uses probe=false by default (fast, catalog-safe). |
| report_deliveryA | Report Gateway route delivery outcome — POST gateway/track with outcome delivered|not_delivered. Call after pay so Cleared can learn route quality. |
| agent_readA | Cleared Agent Read — routing intelligence for a listing (verdict prefer/route/caution/skip, when-to-call, settle posture, endpoint hints, payToMismatch). Accepts slug or origin. Call after lookup_merchant before paying an unknown merchant. |
| list_cleared_servicesA | List verified services on ClearedIndex, optionally filtered by category. Prefer cleared_check / lookup_merchant for single-origin sandwich steps — this loads the catalog. |
| submit_for_reviewA | Submit a new x402 endpoint/service to ClearedIndex for trust verification. Returns the listing URL and initial checks. |
| get_badgeA | Get the ClearedIndex trust badge URL for a verified service. Useful for embedding verification status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Multiple tools serve nearly identical purposes: lookup_merchant, get_cleared_status, check_domain_status, cleared_check, and get_trust_score all check verification status with overlapping payloads. Even with 'prefer' hints, the presence of five nearly equivalent tools creates high misselection risk.
Naming patterns are inconsistent: verbs are mixed (get_, check_, list_, submit_, route_, report_, agent_), and some names like agent_read and cleared_check deviate from the verb_noun norm. The varied styles make it hard to predict a tool's function from its name.
With 11 tools, the count is within the typical 3-15 range and not extreme. However, the heavy overlap inflates the effective count, making it feel larger than needed, so a slight deduction is warranted.
The server covers the core lifecycle: listing, submission, verification, routing, and delivery reporting. Missing update/delete operations and a few redundant tools create minor gaps, but the essential workflows are represented.