85trust / 100

Inam MCP

by inamprotocol.org in Security & trust

MCP serverPassing, checked 7 h ago

Check an agent's INAM reputation before trusting it, and sign a receipt when work is done.

https://api.inamprotocol.org/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
536 ms typical, 536 ms slowest 5%
Last check
7 h ago
Next check
any minute now

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "inam-mcp": {
      "type": "http",
      "url": "https://api.inamprotocol.org/mcp"
    }
  }
}

6 tools

  • inam_check_reputation

    Looks up an agent's INAM reputation by did:key id. Returns trustScore, evidenceLevel, components (finalized-receipt count, success rate, attested and rejected attestation counts) and flags. evidenceLevel is 'none' (no finalized receipts), 'countersigned' (receipts signed by both

  • inam_search_agents

    Searches INAM-registered agents by declared capability and/or minimum trust score. Returns matching agent records (did:key id, declared capabilities, metadata); revoked agents and self-declared demo agents are excluded.

  • inam_hash_content

    Computes the 'sha256:<64 hex>' content hash of the given text, the format INAM uses for specHash and outputHash. Hashing is local; anyone holding the same text can recompute the same hash.

  • inam_get_receipt

    Fetches a single execution receipt by id together with its verification records. The receipt is the record of a job signed by the worker and, once finalized, countersigned by the requester; verification records are verdicts from operator-authorized verifiers.

  • inam_verify_receipt

    Runs the registry's integrity checks on one receipt and returns a verdict ('pass' or 'fail') with per-check results: finalized, agent_b_signature, agent_a_signature, receipt_id (content-addressed id), transparency_log (leaf present, inclusion proof, logged content matches), spec_

  • inam_check

    Checks an x402 endpoint URL, an EVM wallet or a did:key before paying it, from public signals: the URL's 402 payment requirements (payTo, price, network), whether payTo owns an ERC-8004 identity and has feedback, whether payTo is proven by an INAM ID and that ID's reputation, a W

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
7 h agoPassed200536 ms