Cleared Index
NPM · @N747AI/CLEAREDINDEX-MCP-SERVER · SCANNED SEP 22
Cleared Check before pay: lookup_merchant, cleared_check, route_gateway for x402 agents.
Available components
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 Security98
- 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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1427 tokens (~95/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% 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
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
How do I install the Cleared Index MCP server?
Cleared Index runs locally as an npm package, launched with npx -y @n747ai/clearedindex-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @n747ai/clearedindex-mcp-server
claude mcp add com-clearedindex-mcp -- npx -y @n747ai/clearedindex-mcp-server
{
"mcpServers": {
"com-clearedindex-mcp": {
"command": "npx",
"args": [
"-y",
"@n747ai/clearedindex-mcp-server"
]
}
}
} {
"servers": {
"com-clearedindex-mcp": {
"command": "npx",
"args": [
"-y",
"@n747ai/clearedindex-mcp-server"
]
}
}
} codex mcp add com-clearedindex-mcp -- npx -y @n747ai/clearedindex-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-clearedindex-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@n747ai/clearedindex-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-clearedindex-mcp --command npx --arg -y --arg @n747ai/clearedindex-mcp-server
mcp_servers:
com-clearedindex-mcp:
command: "npx"
args: ["-y", "@n747ai/clearedindex-mcp-server"] {
"McpServers": {
"com-clearedindex-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@n747ai/clearedindex-mcp-server"
]
}
}
} assistant mcp add com-clearedindex-mcp -t stdio -c npx -a -y @n747ai/clearedindex-mcp-server
{
"mcpServers": {
"com-clearedindex-mcp": {
"command": "npx",
"args": [
"-y",
"@n747ai/clearedindex-mcp-server"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Analysed npm/@n747ai/clearedindex-mcp-server@1.4.2
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
agent_read ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Cleared listing slug or origin (e.g. taylor-good-agents) |
No output schema declared.
No examples provided.
check_domain_status ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug or domain to check (e.g. 'coinbase-identity') |
No output schema declared.
No examples provided.
cleared_arena ~56
Cleared Arena — boats-class repeat settle habit. Returns the forced sandwich steps (run_gate → verdict → gateway → pay → witness → repeat) for an origin.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | – | Optional origin to bind arena steps to |
No output schema declared.
No examples provided.
cleared_check ~130
Cleared Check — verify an origin before pay. Returns pass, score, payToMismatch, tier, card URL, provenance, nextAction (route_gateway + fee on PASS), and defaultNextTool=route_gateway. Uses probe=false by default (fast, catalog-safe). ALWAYS call route_gateway next on PASS before pay.
| Name | Type | Req | Description |
|---|---|---|---|
| certify | – | – | Attach Certified Hash receipt (default true — tax_the_tx) |
| origin | string | yes | Merchant origin URL or domain (e.g. https://api.example.com) |
| probe | boolean | – | Live-probe endpoints (default false — prefer false for agent farms) |
No output schema declared.
No examples provided.
cleared_run_gate ~105
Cleared Run Gate — NodeRun-class spend firewall before compute/pay. Returns allow/abort/upgrade with Check + payTo + optional spend caps. Free. On upgrade, point agents at Gateway Pro Stripe.
| Name | Type | Req | Description |
|---|---|---|---|
| maxSpendUsd | number | – | Hard spend ceiling in USD |
| minScore | number | – | Minimum Cleared score (default 70) |
| origin | string | yes | Origin about to receive spend |
| spendUsd | number | – | Planned spend in USD |
No output schema declared.
No examples provided.
cleared_verdict ~129
Cleared Verdict — SwarmX-class 3-panel diligence (trust/settle/risk) before pay. Free preview by default. Set paid=true only after settling $0.10 USDC on /api/x402/verdict (or pass txHash). Call after lookup_merchant / cleared_check.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | Merchant origin URL to evaluate |
| paid | boolean | – | If true, call paid /api/x402/verdict (expects prior settlement). Default false = free preview. |
| txHash | string | – | Optional Base USDC settlement tx hash for paid Verdict |
No output schema declared.
No examples provided.
get_badge ~38
Get the ClearedIndex trust badge URL for a verified service. Useful for embedding verification status.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing slug |
No output schema declared.
No examples provided.
get_cleared_status ~62
Cleared status for a slug/domain — same payload as lookup_merchant (Check, probe=false). Prefer lookup_merchant in new agent loops.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug or domain to check (e.g. 'coinbase-identity') |
No output schema declared.
No examples provided.
get_trust_score ~51
Get the detailed trust score breakdown for an origin/slug via Cleared Check (probe=false) — no full catalog load.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing slug or origin to get score for |
No output schema declared.
No examples provided.
list_cleared_services ~82
List verified services on ClearedIndex, optionally filtered by category. Prefer cleared_check / lookup_merchant for single-origin sandwich steps — this loads the catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category: identity, enrichment, compliance, regime, judgment, workflow, other |
| tier | string | – | Filter by tier: listed, cleared, spotlight |
No output schema declared.
No examples provided.
lookup_merchant ~105
DEFAULT before pay — look up a merchant origin/slug on Cleared Index via Check (probe=false). Returns pass, score, payToMismatch, tier, profile URL, nextAction, and defaultNextTool. On PASS call route_gateway next (fee advisory). Call this before any x402 payment to an unknown merchant.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | yes | Merchant origin URL, domain, or Cleared slug (e.g. https://api.example.com or coinbase-identity) |
No output schema declared.
No examples provided.
report_delivery ~91
Report Gateway route delivery outcome — POST gateway/track with outcome delivered|not_delivered. Call after pay so Cleared can learn route quality.
| Name | Type | Req | Description |
|---|---|---|---|
| origin | string | – | Merchant origin that was paid |
| outcome | string | yes | Whether the paid route delivered usable results |
| requestId | string | – | Gateway request/route id if available |
| source | string | – | Reporter label (default agent_report) |
No output schema declared.
No examples provided.
route_gateway ~182
DEFAULT before pay — Cleared Gateway: one call, best verified x402 endpoint. Routes by trust score, settle-tape tx gravity (Witness/on-chain), price, latency, and canary. Returns payTo URL + totalCost. Call after lookup_merchant / cleared_check. Prefer requireReceiptSettled=true in production. 100 free routes/month, no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | – | Optional capability hint |
| category | string | yes | Capability category to route |
| maxPrice | number | – | Max endpoint price in USD |
| minScore | number | – | Minimum trust score (default 55; 70 recommended for production) |
| requireReceiptSettled | boolean | – | Only route to endpoints with on-chain settlement proof |
| strategy | string | – | Routing strategy (default: auto = market route-share; best_value = score/price) |
No output schema declared.
No examples provided.
submit_for_review ~129
Submit a new x402 endpoint/service to ClearedIndex for trust verification. Returns the listing URL and initial checks.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| contactEmail | string | yes | Contact email for verification |
| description | string | yes | Full description of what the service does |
| endpoints | array | yes | API endpoints the service exposes |
| name | string | yes | Service name |
| operator | string | yes | Company/person operating the service |
| origin | string | yes | Base URL of the service (e.g. https://api.example.com) |
| tagline | string | yes | One-line description |
No output schema declared.
No examples provided.
witness_settlement ~119
Witness an x402 USDC settlement on-chain. Call after pay with the settlement txHash. Returns a Cleared attestation receipt URL. Required sandwich step for verifiable agent spend.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Settlement network (default base) — all Cleared Witness rails |
| notify | boolean | – | Notify operator when possible (default true) |
| origin | string | – | Merchant origin that was paid (helps link Witness to listing) |
| txHash | string | yes | Base 0x… tx hash or Solana signature from the settlement |
No output schema declared.
No examples provided.
What is the Cleared Index MCP server?
Cleared Index is an MCP server listed in the public MCP registry as com.clearedindex/mcp. Cleared Check before pay: lookup_merchant, cleared_check, route_gateway for x402 agents. This page covers its npm package (@n747ai/clearedindex-mcp-server).
Is the Cleared Index MCP server safe to use?
Cleared Index scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 Cleared Index MCP server expose?
Cleared Index exposes 15 tools: lookup_merchant, get_cleared_status, route_gateway, check_domain_status, get_trust_score, and 10 more. Their descriptions and schemas cost roughly 1,427 tokens of context every time the server is loaded.
Is the Cleared Index MCP server still maintained?
Cleared Index is still listed as active in the MCP registry. We last reached this channel on 22 September 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 Cleared Index MCP server under?
Cleared Index declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.