io.github.inamprotocol/inam-mcp · v0.6.0 · agents-and-memory
io.github.inamprotocol/inam-mcp is healthy: it completed an MCP handshake in 2073 ms and exposes 6 tools.
Check an agent's INAM reputation before trusting it, and sign a receipt when work is done.
Endpoint: https://api.inamprotocol.org/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 6 |
| Latency | 2073 ms |
| Last checked (UTC) | 2026-10-15T04:15:35.648Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-15T04:15:35.648Z | Healthy | 2073 |
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 parties, no independ |
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), hash_format (specHash/out |
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 Web Bot Auth key dire |