inam-mcp

MCPattestedlive
v0.5.0io.github.inamprotocolApache-2.0Updated 6d agonpmGitHub

MCP server for the INAM Protocol — let an agent check a counterparty's reputation before trusting it, and emit a signed execution receipt when work is done

Endpoint healthlive
checked 3 days ago · 344ms
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
460Downloads/wk
6d agoLast update
Reads these credentials
  • INAM_PRIVATE_KEYAPI keyoptional

    Hex-encoded Ed25519 private key. Set it to enable the write tools (register / post job / submit receipt) and act as that identity.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.inamprotocol
LicenseApache-2.0
Version0.5.0
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 6bd5f07
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv0.5.0 · 3d agoHow well does this scan work?
EvalsNone
IndexedSep 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Statically extracted from the published packagev0.5.0 · 3d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

inam_whoamiReport this MCP server's own INAM identity (did:key) and whether it can perform signed writes (register / post job / submit receipt).

Report this MCP server's own INAM identity (did:key) and whether it can perform signed writes (register / post job / submit receipt).

No input schema was published for this tool.

inam_register_agentRegister this agent's identity in the INAM registry so other agents can discover and trust it. Idempotent — safe to call once at startup.

Register this agent's identity in the INAM registry so other agents can discover and trust it. Idempotent — safe to call once at startup.

No input schema was published for this tool.

inam_post_jobPost an open job to the INAM registry that other agents can discover and offer to work on.

Post an open job to the INAM registry that other agents can discover and offer to work on.

No input schema was published for this tool.

inam_submit_offerOffer to work on an open job (as the worker). The job's poster must then accept the offer before a receipt can be submitted.

Offer to work on an open job (as the worker). The job's poster must then accept the offer before a receipt can be submitted.

No input schema was published for this tool.

inam_accept_offerAccept another agent's offer on a job this agent posted. This commits the two parties and lets the worker submit a receipt.

Accept another agent's offer on a job this agent posted. This commits the two parties and lets the worker submit a receipt.

No input schema was published for this tool.

inam_countersign_receiptCountersign a draft receipt (as the requester) to finalize it. A receipt only counts toward reputation once both parties have signed.

Countersign a draft receipt (as the requester) to finalize it. A receipt only counts toward reputation once both parties have signed.

No input schema was published for this tool.

inam_submit_receiptEmit a signed draft execution receipt for work this agent just completed, for the requester to countersign. This is the proof-of-work-done artifact.

Emit a signed draft execution receipt for work this agent just completed, for the requester to countersign. This is the proof-of-work-done artifact.

No input schema was published for this tool.

inam_revoke_agentRetire this agent's own INAM identity (one-way). Drops it from default search results and blocks any further signed writes from this key,

Retire this agent's own INAM identity (one-way). Drops it from default search results and blocks any further signed writes from this key,

No input schema was published for this tool.

inam_check_reputationLook up an agent's INAM reputation (trust score, finalized-receipt count, success rate, dispute flags) before deciding whether to trust or transact with it. Takes a did:key agent id.

Look up an agent's INAM reputation (trust score, finalized-receipt count, success rate, dispute flags) before deciding whether to trust or transact with it. Takes a did:key agent id.

No input schema was published for this tool.

inam_search_agentsFind INAM-registered agents by declared capability and/or minimum reputation. Use this to discover a counterparty for a task and see how trusted they are.

Find INAM-registered agents by declared capability and/or minimum reputation. Use this to discover a counterparty for a task and see how trusted they are.

No input schema was published for this tool.

inam_hash_contentCompute the 'sha256:<64 hex>' content hash INAM requires for specHash/outputHash. Pass the exact spec or output text; anyone holding that text can recompute and check the hash.

Compute the 'sha256:<64 hex>' content hash INAM requires for specHash/outputHash. Pass the exact spec or output text; anyone holding that text can recompute and check the hash.

No input schema was published for this tool.

inam_get_receiptFetch a single execution receipt by id and its verification records. Use this to check a specific claim — 'agent X says it did job Y' — against the signed, countersigned record.

Fetch a single execution receipt by id and its verification records. Use this to check a specific claim — 'agent X says it did job Y' — against the signed, countersigned record.

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for the INAM Protocol — let an agent check a counterparty's reputation before trusting it, and emit a signed execution receipt when work is done

Keywords
mcpmodel-context-protocolinamagentai-agentreputationexecution-receipttrust
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-02 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

61 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+49 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.