AgentIndex
REMOTE · MCP-AGENTINDEX.CRAFTYOUR.SITE
Trust scores and on-chain payment receipts for x402 services.
Available components
Last scanned (21 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 Nov 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 305 tokens (~76/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 12 Oct 26 +1
- Stability: 0.93 → pass security
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 73 to 93. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 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.
- 2 Oct 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Sept 26 0
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 4 Nov 2026 · Probed https://mcp-agentindex.craftyour.site/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agentindex.craftyour.site | CN=YE2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5cef89453198ecd9aa635957719c1a4a010 |
| SANs: agentindex.craftyour.site, api-agentindex.craftyour.site, mcp-agentindex.craftyour.site, services-agentindex.craftyour.site | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-agentindex.craftyour.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| craftyour.site. | 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://mcp-agentindex.craftyour.site/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-agentindex.craftyour.site/mcp | HTTPS enforced | 301 | https://mcp-agentindex.craftyour.site/mcp |
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 →
check_trust ~78
Full trust report for one service: score, delivery/honesty rates, latency, and recent probes with chain-aware payment receipts. Accepts a label ("weatherpro") or full name ("weatherpro.agentindex.eth").
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Service label or ENS name |
| probes | integer | – | How many recent probes to include |
No output schema declared.
No examples provided.
find_service ~63
Search the AgentIndex registry for x402 services matching a capability, e.g. "weather data" or "token prices". Returns matching services with endpoints, prices and their probed trust scores.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | What the service should do, in plain words |
No output schema declared.
No examples provided.
get_verified_data ~100
One call: pick the most-trusted service for a need, fetch the data from it, and return the data together with that provider's trust score and its latest on-chain probe receipt as proof. Use when you want the answer AND a record of why the source was trusted. Scam / low-trust providers are never selected.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | The data you want, e.g. "current ETH price" or "weather in Singapore" |
No output schema declared.
No examples provided.
resolve_data_need ~64
End-to-end selection: describe a task, get back the single best service to pay (plus ranked alternatives and any services to avoid). Use this before spending money over x402.
| Name | Type | Req | Description |
|---|---|---|---|
| task | string | yes | The task, e.g. "get current weather for Singapore" |
No output schema declared.
No examples provided.
How do I install the AgentIndex MCP server?
AgentIndex is a hosted endpoint at https://mcp-agentindex.craftyour.site/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 · mcp-agentindex.craftyour.site
claude mcp add --transport http cognivis-agentindex 'https://mcp-agentindex.craftyour.site/mcp'
What is the AgentIndex MCP server?
AgentIndex is an MCP server listed in the public MCP registry as io.github.cognivis/agentindex. Trust scores and on-chain payment receipts for x402 services. This page covers its hosted endpoint (https://mcp-agentindex.craftyour.site/mcp).
Is the AgentIndex MCP server safe to use?
AgentIndex scores 79 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 AgentIndex MCP server expose?
AgentIndex exposes 4 tools: find_service, check_trust, resolve_data_need, get_verified_data. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.
Does the AgentIndex MCP server require authentication?
No. We connected to AgentIndex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AgentIndex MCP server still maintained?
AgentIndex is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.