Koskamo

Onchain Agent Intel MCP

An MCP server that provides trust and readiness intelligence for ERC-8004 AI agents on Base and Ethereum. It offers tools to check agent liveness, payment validity, and reputation scores, allowing agents to verify counterparties before engaging in commerce-backed reputation or payments.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Onchain Agent Intel MCP logo, by Onchain Agent IntelVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Onchain Agent Intel
MCP endpoint (Streamable HTTP)
https://api.onchainagentintel.io/mcp
Vendor documentation

What its tools do

8 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

8 of 8 have a description · 0 of 8 declare behavior hints · 0 of 5 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to onchainagentintel.io ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Check if an ERC-8004 agent is live at its advertised endpoint
  • Verify payment-request validity and last payment seen
  • Retrieve readiness and trust scores for agents
  • Access public leaderboards of top agents by capability and liveness

Source and maintenance

Vendor evidenceRegistry 1.9.0

Protocol and capabilities

Server
agent-zero-intel 1.8.0
MCP protocol negotiated in check
2025-11-25
Tools
8 advertised
Resources
0 advertised
Resource templates
0 advertised
Prompts
0 advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  },
  "prompts": {
    "listChanged": false
  },
  "resources": {
    "subscribe": false,
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Agent Zero — free ERC-8004 agent-intelligence tools across Base and Ethereum. Start here: call `get_coverage_stats` with no arguments for a live market overview. Every tool accepts zero arguments — `get_agent_summary` and `agent_trust_teaser` default to Agent Zero itself (chain="base", agent_id=19353), the agent serving this MCP endpoint, so a zero-arg call returns live signals for a real indexed agent. Every response is free and returns counts/coverage only; each response includes an `upgrade` + `paid_upgrade` pointer to the paid x402 endpoint that returns the full enriched data (owner identity, payment history, peers, market map, full graph).

Tools

8 advertised

get_coverage_stats
Advertised by the server during the last successful anonymous check.

Live coverage of the ERC-8004 agent economy across Base and Ethereum. Returns counts only: how many agents are indexed, how many expose a live MCP server / OpenAPI / well-known card, total MCP tools and OpenAPI methods observed, contracts verified, EOAs and owners identified, plus a per-chain breakdown. No names, addresses, or handles. Use this to size the market and see where capability density is growing. Paid counterpart: `GET /v1/intel/market` (x402, USDC on base-mainnet) returns the full capability market map — which capabilities are saturated vs open, per-capability agent lists, and momentum. Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.

get_coverage_stats input schema
{
  "type": "object",
  "title": "get_coverage_statsArguments",
  "properties": {}
}
get_leaderboards
Advertised by the server during the last successful anonymous check.

Top ERC-8004 agents by live capability, plus the most recently indexed. Three ranked lists — top by live MCP tool count, top by OpenAPI method count, and most-recently indexed — each with agent_id, chain, public name, a shareable detail URL, and the relevant count. Names and counts only: no owner wallets, handles, or endpoint URLs. Use this to find the most capable / most active agents to integrate or watch. Paid counterpart: `GET /v1/intel/trending` (x402, USDC on base-mainnet) returns trending intel — top earners, fastest-rising agents, and integration candidates ranked with the signals behind the ranking. Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.

get_leaderboards input schema
{
  "type": "object",
  "title": "get_leaderboardsArguments",
  "properties": {}
}
get_agent_summary
Advertised by the server during the last successful anonymous check.

Objective, counts-only signals for one ERC-8004 agent. Args (BOTH OPTIONAL — call with `{}` to see Agent Zero itself): chain: one of "base", "ethereum". Default: "base". agent_id: the numeric ERC-8004 agent id. Default: 19353 (Agent Zero, the agent serving this MCP endpoint). Example: `{}` returns Agent Zero on base; `{"chain": "base", "agent_id": 19353}` is the explicit form. Returns reachability, TLS validity, x402 support, payments to the agent's own address (booleans only: payments_to_agent_address, payment_attribution; payments_to_owner_wallet and payments_received are deprecated, removed 2026-12-05), MCP tool count, OpenAPI method count, well-known presence, owner-named (boolean), and a neutral status label (status_label_v2: Reachable, payment signals / Reachable, no payment signals / Stub or unreachable; the old status_label is deprecated, sunset 2026-11-07). No owner identity string and no payment amounts — those are paid. Returns an `error` field if the agent is not indexed. Use this to vet a counterparty agent before transacting. Paid counterpart: `GET /v1/intel/agent/{agent_id}?chain={chain}` (x402, USDC on base-mainnet) unlocks trust_verdict (safe_to_transact / caution / avoid / insufficient_data), readiness_score, Sybil-adjusted reputation, the reviews-from-paid-jobs (commerce-backed) breakdown, and for Transact-ready or higher agents a plain-English `brief` (due-diligence summary from our data, with sources and as-of date) — the decision-driving values this free response returns as `null` inside a `locked` map. Every response carries an `unlock` block with the exact paid endpoint, price, and payment discovery.

get_agent_summary input schema
{
  "type": "object",
  "title": "get_agent_summaryArguments",
  "properties": {
    "chain": {
      "type": "string",
      "title": "Chain",
      "default": "base"
    },
    "agent_id": {
      "type": "integer",
      "title": "Agent Id",
      "default": 19353
    }
  }
}
get_network_teaser
Advertised by the server during the last successful anonymous check.

A capped teaser of the on-chain agent-to-agent payment graph. Returns connected agents (nodes) and the value flowing between them (edges), capped to a small connected sample (≤200 nodes). This is a truncated preview, not the full network. Use it to see who pays whom in the agent economy. Paid counterpart: `GET /v1/intel/graph` (x402, USDC on base-mainnet) returns the agent-to-agent payment graph, capped to the top 2,000 agents by payment value plus the edges among them (USDC/ETH amounts; filters chain, min_usd, limit; meta.truncated). Every response from this free tool carries an `unlock` block with the exact paid endpoint, price, and payment discovery.

get_network_teaser input schema
{
  "type": "object",
  "title": "get_network_teaserArguments",
  "properties": {}
}
agent_trust_teaser
Advertised by the server during the last successful anonymous check.

Credit-score-style TEASER for one ERC-8004 agent's trust profile. Args (BOTH OPTIONAL — call with `{}` to see Agent Zero itself): chain: one of "base", "ethereum". Default: "base". agent_id: the numeric ERC-8004 agent id. Default: 19353 (Agent Zero, the agent serving this MCP endpoint). Example: `{}` returns Agent Zero on base; `{"chain": "base", "agent_id": 19353}` is the explicit form. By construction returns ONLY: name, chain, agent_id, public ladder_step / ladder_name (the four-step ladder; readiness_bucket is deprecated), and a 1-line verdict headline. Agents that belong to a platform registering many agents and have no endpoint or activity of their own yet also carry `platform_listed: true` and `platform`. Every decision-driving value — trust_verdict, readiness_score, risk_flags, money-flow details, counterparty list, full score breakdown — is redacted as `null` and enumerated in the `locked` map. The response carries the exact paid endpoint URL (/v1/intel/agent/{agent_id}?chain={chain}), the x402 price as currently configured, and a one-line how-to-pay-via-x402 hint. Returns `error` with the same unlock pointer if the agent is not indexed, so a caller probing an unknown id still sees how to pay for a known one. Paid counterpart: `GET /v1/intel/agent/{agent_id}?chain={chain}` (x402, USDC on base-mainnet) returns the full trust verdict (safe_to_transact / caution / avoid / insufficient_data), readiness_score + sub-scores, Sybil-adjusted reputation, and the reviews-from-paid-jobs (commerce-backed) breakdown, and for Transact-ready or higher agents a plain-English `brief` (sources and as-of date included). Every response from this free tool carries an `unlock` + `paid_upgrade` block with the exact paid endpoint, price, and payment discovery.

agent_trust_teaser input schema
{
  "type": "object",
  "title": "agent_trust_teaserArguments",
  "properties": {
    "chain": {
      "type": "string",
      "title": "Chain",
      "default": "base"
    },
    "agent_id": {
      "type": "integer",
      "title": "Agent Id",
      "default": 19353
    }
  }
}
list_payable_x402_endpoints
Advertised by the server during the last successful anonymous check.

Directory of ERC-8004 agents that answered a well-formed HTTP 402 x402 challenge during our last field probe. OBSERVATION ONLY — not a score, ranking, or endorsement. Args (ALL OPTIONAL — call with `{}` for the top 10 across both chains): chain: one of "base", "ethereum" (omit for both). Default: null. limit: 1..10 rows (free-tier cap). Default: 10. Returns per-row raw probe facts: agent_id, chain, endpoint_url, http_402_ok, network, asset, price_usd as the challenge advertised, payTo_present (boolean — the actual address is paid), sibling_agent_ids (other ERC-8004 ids served by the same gateway row — the 'shared operator' cue), probed_at. Plus `total_endpoints_valid_402` and `total_agents_valid_402` so a caller can see what fraction of the surface this free slice covers. Source: the 0946 field-test one-shot probe (unauthenticated, read-only, no payment signed). See the `field_test_url` field for the full writeup. Paid counterpart: the paid x402 /v1/intel/* endpoints return the same-origin enriched intel on any single agent in this list — owner identity, payment history, peers, trust verdict, Sybil-adjusted reputation. Every response from this free tool carries an `unlock` + `paid_upgrade` block with the exact paid endpoint, price, and payment discovery.

list_payable_x402_endpoints input schema
{
  "type": "object",
  "title": "list_payable_x402_endpointsArguments",
  "properties": {
    "chain": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Chain",
      "default": null
    },
    "limit": {
      "type": "integer",
      "title": "Limit",
      "default": 10
    }
  }
}
check_x402_endpoint
Advertised by the server during the last successful anonymous check.

Find out if agents can actually pay you. Free check of an x402 seller endpoint (Seller Check). Sends only unpaid requests: confirms the route answers HTTP 402, reads the challenge (header and body, v1 or v2), checks every accepts entry (scheme, network, asset, amount, payTo, maxTimeoutSeconds, and extra.name/extra.version against the token's real EIP-712 domain), the named payment service's /supported, and /pricing, /openapi.json, /.well-known/x402 for consistency. Args: url: https URL of the paid route (required). method: "GET" or "POST" (optional; default from the seller's OpenAPI file, else GET). body: optional JSON body for POST routes (max 8 KB). Returns checked_at, overall (pass|warn|fail) and checks[] with status, reason and a fix hint. Never pays. Limits: 10 checks per caller per hour, 3 per host per hour.

check_x402_endpoint input schema
{
  "type": "object",
  "title": "check_x402_endpointArguments",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "title": "Url"
    },
    "body": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Body",
      "default": null
    },
    "method": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Method",
      "default": null
    }
  }
}
seller_check
Advertised by the server during the last successful anonymous check.

Find out if agents can actually pay you. PAID ($0.50 USDC on Base, x402) Seller Check: an independent test of an x402 seller endpoint. Runs the free checks, then makes one real paid call to the seller (only if the seller's price is at most $0.10) and returns a report with every check, both transaction links, pass/warn/fail, findings and fix hints. One free re-run within 7 days. Payment: call once without payment to get the x402 v2 requirements (returned as `payment_required`), then repeat the call with the PAYMENT-SIGNATURE (v2) or X-PAYMENT (v1) header on this MCP HTTP request. The same service is POST https://api.onchainagentintel.io/v1/seller-check. Args: url: https URL of the paid route (required). method: "GET" or "POST" (optional). body: optional JSON body for the paid call (else the seller's own example; we never invent data). route: optional path to test on the url's host. contact_email: optional; stored, never published. public: true lets the result page be indexed (default private).

seller_check input schema
{
  "type": "object",
  "title": "seller_checkArguments",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "title": "Url"
    },
    "body": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Body",
      "default": null
    },
    "route": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Route",
      "default": null
    },
    "method": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Method",
      "default": null
    },
    "public": {
      "type": "boolean",
      "title": "Public",
      "default": false
    },
    "contact_email": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "title": "Contact Email",
      "default": null
    }
  }
}

Prompts

0 advertised

No prompt definitions available.

Resources

0 advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (1 of 1 answered).

  1. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
6941 ms
95th percentile latency
6941 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 6941 ms · metadata changed · 8 tool(s), 0 resource(s), 0 resource template(s), 0 prompt(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http onchain-agent-intel-mcp https://api.onchainagentintel.io/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add onchain-agent-intel-mcp --url https://api.onchainagentintel.io/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable onchain-agent-intel-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "onchain-agent-intel-mcp": {
      "url": "https://api.onchainagentintel.io/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "onchain-agent-intel-mcp": {
      "type": "streamableHttp",
      "url": "https://api.onchainagentintel.io/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start onchain-agent-intel-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "onchain-agent-intel-mcp": {
      "type": "http",
      "url": "https://api.onchainagentintel.io/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http onchain-agent-intel-mcp https://api.onchainagentintel.io/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.onchainagentintel.io/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "onchain-agent-intel-mcp": {
      "serverUrl": "https://api.onchainagentintel.io/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Onchain Agent Intel MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run Onchain Agent Intel MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing