Cleared Index
# @n747ai/clearedindex-mcp-server
<a href="https://glama.ai/mcp/servers/N747AI/clearedindex-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/N747AI/clearedindex-mcp/badge" alt="Cleared Index MCP server" />
</a>
[](https://glama.ai/mcp/servers/N747AI/clearedindex-mcp)
MCP server for [ClearedIndex](https://clearedindex.com) — index before you pay a merchant.
**Related MCP:** [x402 Endpoint Trust & Reputation (gold-402)](https://github.com/Haustorium12/gold-402/blob/main/directory/security.md) — Cleared Index is listed on that shelf; set the same link under Glama admin → Related servers when pairing complementary trust MCPs.
## Default agent sandwich (step 1)
```text
lookup_merchant(origin) # free — Cleared Index
→ ei.fetch_pre_settle_stamp()
→ ei.get_regime_clock(slug)
→ external.spend(...)
→ ei.verify_settlement_bind()
```
## Tools
| Tool | Description |
|------|-------------|
| `lookup_merchant` | **DEFAULT before pay** — origin/slug → tier, score, profile |
| `get_cleared_status` | Same payload as lookup (status alias) |
| `route_gateway` | Category router — best verified endpoint + cost |
| `check_domain_status` | Legacy alias of get_cleared_status |
| `get_trust_score` | Detailed trust score breakdown |
| `list_cleared_services` | List verified services by category/tier |
| `submit_for_review` | Submit a new service for verification |
| `get_badge` | Embeddable trust badge URL |
## Install
### Smithery
```bash
smithery install @n747ai/clearedindex-mcp-server
```
### Manual (stdio)
```bash
npx @n747ai/clearedindex-mcp-server
```
### Claude Desktop / Cursor config
```json
{
"mcpServers": {
"clearedindex": {
"command": "npx",
"args": ["-y", "@n747ai/clearedindex-mcp-server"]
}
}
}
```
## Environment
| Variable | Default | Description |
|----------|---------|-------------|
| `CLEARED_API_URL` | `https://clearedindex.com` | API base URL |
## What is ClearedIndex?
ClearedIndex is the merchant graph for x402 — agents look up merchants before they pay; operators claim and attest for preferred Gateway routing.
**Tiers:**
- `listed` — indexed, not yet verified
- `cleared` — passed trust checks (score >= 70)
- `spotlight` — cleared + editorially featured
## License
MIT
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.