inam-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inam_check_reputationA | 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 independent check) or 'independently_verified' (at least one receipt verified by an operator-authorized verifier, components.attestedReceipts > 0). flags include attestation_rejected (a verifier rejected one of the agent's receipts), in_dispute, nonperformance_reported, revoked, concentrated_counterparty: and unanchored_counterparty_volume. |
| inam_search_agentsA | 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_contentA | 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_receiptA | 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_receiptA | 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/outputHash are sha256: + 64 hex; fails on pre-v0.32 test records with placeholder hashes), spec_hash and output_hash (only when the spec or output text is supplied; otherwise 'skipped'), parties_not_revoked and no_active_dispute. Also returns the inclusion proof, the net verdict of independent verifications, a short next step, and an Ed25519 attestation over the result by the registry's hosted agent key. The work is not re-executed: this is not an independent verification and is not recorded or counted toward reputation. |
| inam_checkA | 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 directory, HTTPS and the domain's registration age. Works when INAM has no data on the target. Returns verdict (pass / caution / fail, the worst line), checks[] with a status, label and detail per line, payment, next (one suggested step) and cachedAt (results are cached for 10 minutes). |
| inam_whoamiA | Returns this MCP server's own INAM identity (did:key), the registry URL it is connected to, and whether signed writes (register / post job / submit receipt) are enabled. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools target distinct operations: search_agents (discovery), get_receipt (fetch), verify_receipt (integrity checks), hash_content (local hashing), whoami (self-identity). However, inam_check overlaps with inam_check_reputation since it also surfaces an INAM ID's reputation for a target, and search_agents vs check_reputation both concern agent lookups, creating mild boundary confusion.
All names use a consistent inam_ snake_case prefix with readable verb_noun forms (search_agents, hash_content, get_receipt, check_reputation, verify_receipt). Minor deviations are inam_check (no explicit noun) and inam_whoami (no verb_noun split), but the pattern is largely predictable.
Seven tools is a well-scoped set that covers discovery, lookup, hashing, verification, external checks, and self-identity without redundancy. Each tool clearly earns its place in a focused read/verify workflow.
The surface is read/verify-oriented: search, get, check, verify, hash, whoami. inam_whoami's description references signed writes (register agent, post job, submit receipt), yet no tools expose those lifecycle operations, so the create/post side of the domain is a notable gap.