Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.inamprotocol/inam-mcp

NPM · INAM-MCP · SCANNED SEP 20

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

Available components

+4 this week 76 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 12 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 250 tokens (~62/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.inamprotocol/inam-mcp server?

io.github.inamprotocol/inam-mcp runs locally as an npm package, launched with npx -y inam-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · inam-mcp

# add to Claude Code
claude mcp add inamprotocol-inam-mcp -- npx -y inam-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "inamprotocol-inam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "inam-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "inamprotocol-inam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "inam-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add inamprotocol-inam-mcp -- npx -y inam-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "inamprotocol-inam-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "inam-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add inamprotocol-inam-mcp --command npx --arg -y --arg inam-mcp
# ~/.hermes/config.yaml
mcp_servers:
  inamprotocol-inam-mcp:
    command: "npx"
    args: ["-y", "inam-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "inamprotocol-inam-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "inam-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add inamprotocol-inam-mcp -t stdio -c npx -a -y inam-mcp
// mcp.json
{
  "mcpServers": {
    "inamprotocol-inam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "inam-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 13 Sept 26 +15
    • Malware scan: unverified → pass security
  • 12 Sept 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/inam-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 103 packages
Packages resolved 103
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~250 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
inam_check_reputation ~70

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.

NameTypeReqDescription
agentIdstringyesdid:key:... id of the agent to check

No output schema declared.

No examples provided.

inam_get_receipt ~63

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.

NameTypeReqDescription
receiptIdstringyessha256:... receipt id

No output schema declared.

No examples provided.

inam_search_agents ~77

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.

NameTypeReqDescription
capabilitystringe.g. 'translation.tr-en', 'code-review'
minReputationnumberonly return agents with at least this trust score

No output schema declared.

No examples provided.

inam_whoami ~40

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.inamprotocol/inam-mcp server?

io.github.inamprotocol/inam-mcp is listed in the public MCP registry as io.github.inamprotocol/inam-mcp. Check an agent's INAM reputation before trusting it, and sign a receipt when work is done. This page covers its npm package (inam-mcp).

Is the io.github.inamprotocol/inam-mcp server safe to use?

io.github.inamprotocol/inam-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.inamprotocol/inam-mcp server expose?

io.github.inamprotocol/inam-mcp exposes 4 tools: inam_check_reputation, inam_search_agents, inam_get_receipt, inam_whoami. Their descriptions and schemas cost roughly 250 tokens of context every time the server is loaded.

Is the io.github.inamprotocol/inam-mcp server still maintained?

io.github.inamprotocol/inam-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.inamprotocol/inam-mcp server under?

io.github.inamprotocol/inam-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.