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

REMOTE · API.INAMPROTOCOL.ORG · 2 COMPONENTS

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

−1 this week 81 Trust /100

Last scanned (21 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1261 tokens (~210/item across 6 items; 6 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 6 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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 171 → 210 ▼ functional
  • 17 Nov 26 0
    • Tool “inam_verify_receipt” rewrote its description, which is the text the model reads security
    • Tool “inam_check” rewrote its description, which is the text the model reads security
    • Tool “inam_check_reputation” rewrote its description, which is the text the model reads security
    • Tool “inam_get_receipt” rewrote its description, which is the text the model reads security
    • Tool “inam_hash_content” rewrote its description, which is the text the model reads security
    • Tool “inam_search_agents” rewrote its description, which is the text the model reads security
    • Schema quality: 140 → 171 ▼ functional
    • Server version: 0.6.0 → 0.6.1 functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • Tool “inam_check_reputation” changed its title: Check agent reputation cosmetic
    • Tool “inam_verify_receipt” changed its title: Verify receipt cosmetic
    • Tool “inam_get_receipt” changed its title: Get receipt cosmetic
    • Tool “inam_search_agents” changed its title: Search agents cosmetic
    • Tool “inam_hash_content” changed its title: Hash content cosmetic
    • Tool “inam_check” changed its title: Pre-payment check cosmetic
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 26 Oct 26 +1

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

  • 24 Oct 26 +1

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

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 · Probed https://api.inamprotocol.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=inamprotocol.org CN=WE1,O=Google Trust Services,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 56d86e43b7e028c80e0ad92890cd45b2
SANs: inamprotocol.org, api.inamprotocol.org, *.api.inamprotocol.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.inamprotocol.org. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
inamprotocol.org. DS published 2371 13 Verified
api.inamprotocol.org. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.inamprotocol.org/mcp Verified 200
http (plaintext) http://api.inamprotocol.org/mcp Inconclusive 406
MCP tools · 6 exposed · ~1,029 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.

Install

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

io.github.inamprotocol/inam-mcp is a hosted endpoint at https://api.inamprotocol.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.inamprotocol.org

# add to Claude Code
claude mcp add --transport http inamprotocol-inam-mcp 'https://api.inamprotocol.org/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 hosted endpoint (https://api.inamprotocol.org/mcp).

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

io.github.inamprotocol/inam-mcp scores 81 out of 100 on VerifyMCP. 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 6 tools: inam_check_reputation, inam_search_agents, inam_hash_content, inam_get_receipt, inam_verify_receipt, inam_check. Their descriptions and schemas cost roughly 1,029 tokens of context every time the server is loaded.

Does the io.github.inamprotocol/inam-mcp server require authentication?

No. We connected to io.github.inamprotocol/inam-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the io.github.inamprotocol/inam-mcp server?

VerifyMCP ran 12 checks on io.github.inamprotocol/inam-mcp, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.inamprotocol/inam-mcp: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.