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 · 2 COMPONENTS

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

+2 this week 92 Trust /100

Last scanned (15 hours ago)

Scores higher than 92% of npm servers

Category Security

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 Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, reached via inamprotocol > zod. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to inamprotocol/inam-protocol). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1077 tokens (~153/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, reached via inamprotocol > zod. A fixed version is available. security
    • Schema quality: 123 → 153 ▼ functional
    • Package version: 0.6.0 → 0.6.1 functional
  • 9 Nov 26 +5
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −4
    • Provenance: pass → unverified ▼ security
    • Security disclosure: unverified → pass ▲ functional
  • 7 Nov 26 −1
    • Stability: 0.97 → pass security
    • Security disclosure: pass → unverified ▼ functional
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 21 Nov 2026 · Analysed npm/inam-mcp@0.6.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo inamprotocol/inam-protocol
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/inamprotocol/inam-protocol/.github/workflows/publish-npm-mcp.yml@refs/heads/main
Rekor log index 3951352996
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:a0cfe27d95188c5caa12933149c625c60fd4db8a5018a4742473229eff69a82e2ff658bbb8bba62074ae0259f0e06cea5dfba1ca9c5cb15680b8e9fbd

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 100 packages
Packages resolved 100
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,077 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 ~258

Use before paying an x402 endpoint, a paid MCP tool, a wallet or an agent: checks an x402 endpoint URL, an EVM wallet or a did:key 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. A URL that does not answer with an x402 payment request gets verdict fail ('Not an x402 paywall'): there is nothing to pay there in this format, which says nothing about whether the site is safe. 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).

NameTypeReqDescription
methodstring–HTTP method for a URL target; default GET, use POST for endpoints that only answer POST
targetstringyesx402 endpoint http(s) URL, 0x EVM wallet address, or did:key:z...

No output schema declared.

No examples provided.

inam_check_reputation ~200

Use before hiring, delegating to or paying an AI agent whose did:key id you have: looks up its INAM reputation. An id the registry does not know means no record, not a bad agent. 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:<id> and unanchored_counterparty_volume.

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

No output schema declared.

No examples provided.

inam_get_receipt ~109

Use to read what a receipt says (who did what for whom, when, with what outcome): fetches a single execution receipt by id together with its verification records. To test whether the receipt holds up, use inam_verify_receipt. 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.

NameTypeReqDescription
receiptIdstringyessha256:... receipt id

No output schema declared.

No examples provided.

inam_hash_content ~92

Use to fingerprint a text, or to compare a spec or output you hold with the hash in a receipt: 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.

NameTypeReqDescription
contentstringyesthe exact spec or output text to hash

No output schema declared.

No examples provided.

inam_search_agents ~113

Use to find an AI agent for a task: searches INAM-registered agents by declared capability and/or minimum trust score. Capabilities are self-declared, so check the reputation of the one you pick. Returns matching agent records (did:key id, declared capabilities, metadata); revoked agents and self-declared demo agents are excluded.

NameTypeReqDescription
capabilitystring–e.g. 'translation.tr-en', 'code-review'
minReputationnumber–minimum trust score; agents below it are excluded

No output schema declared.

No examples provided.

inam_verify_receipt ~257

Use when someone presents a receipt id as proof that an agent did a job: runs the registry's integrity checks on that 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.

NameTypeReqDescription
outputstring–exact output text; checked against the receipt's result.outputHash
receiptIdstringyessha256:... receipt id
specstring–exact task spec text; checked against the receipt's task.specHash

No output schema declared.

No examples provided.

inam_whoami ~48

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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
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 92 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 7 tools: inam_check_reputation, inam_search_agents, inam_hash_content, inam_get_receipt, inam_verify_receipt, and 2 more. Their descriptions and schemas cost roughly 1,077 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 21 November 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.

What did VerifyMCP test on the io.github.inamprotocol/inam-mcp server?

VerifyMCP ran 16 checks on io.github.inamprotocol/inam-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.