Skip to content

AgentIndex

by cognivis · remote · no sign-in to list tools · v0.2.0 · published by GitHub user cognivis

Trust scores and on-chain payment receipts for x402 services.

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http agentindex https://mcp-agentindex.craftyour.site/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • check_trustFull trust report for one service: score, delivery/honesty rates, latency, and recent probes with chain-aware payment receipts.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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").
Only reads 3Claude Code: allow
  • find_serviceSearch the AgentIndex registry for x402 services matching a capability, e.g.No findings

    Why it is in this group

    • The name "find_service" says "find": a word for reading.
    Description, as the server wrote it
    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.
  • get_verified_dataOne 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 p…No findings

    Why it is in this group

    • The name "get_verified_data" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • resolve_data_needEnd-to-end selection: describe a task, get back the single best service to pay (plus ranked alternatives and any services to avoid).No findings

    Why it is in this group

    • The name "resolve_data_need" says "resolve": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agentindex https://mcp-agentindex.craftyour.site/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agentindex__find_service",
      "mcp__agentindex__resolve_data_need",
      "mcp__agentindex__get_verified_data"
    ],
    "ask": [
      "mcp__agentindex__check_trust"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as agentindex. Review it before you use it.