# io.github.inamprotocol/inam-mcp (remote · api.inamprotocol.org)

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

- Trust score: 81/100 (high trust)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.inamprotocol.org`: 81/100 (this document), [markdown](https://verifymcp.io/servers/inamprotocol-inam-mcp/api.md), [page](https://verifymcp.io/servers/inamprotocol-inam-mcp/api)
- npm · `inam-mcp`: 92/100, [markdown](https://verifymcp.io/servers/inamprotocol-inam-mcp/inam-mcp.md), [page](https://verifymcp.io/servers/inamprotocol-inam-mcp/inam-mcp)

## Channel facts

- Endpoint: `https://api.inamprotocol.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.6.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http inamprotocol-inam-mcp 'https://api.inamprotocol.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "inamprotocol-inam-mcp": {
      "url": "https://api.inamprotocol.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "inamprotocol-inam-mcp": {
      "type": "http",
      "url": "https://api.inamprotocol.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.inamprotocol-inam-mcp]
url = "https://api.inamprotocol.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "inamprotocol-inam-mcp": {
      "type": "remote",
      "url": "https://api.inamprotocol.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add inamprotocol-inam-mcp --url 'https://api.inamprotocol.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  inamprotocol-inam-mcp:
    url: "https://api.inamprotocol.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "inamprotocol-inam-mcp": {
      "Transport": "http",
      "Url": "https://api.inamprotocol.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add inamprotocol-inam-mcp -t streamable-http -u 'https://api.inamprotocol.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "inamprotocol-inam-mcp": {
      "type": "http",
      "url": "https://api.inamprotocol.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 81, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 171 → 210

### 2026-11-17 (score 82, 0)

- [security] 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
- [functional regression] Schema quality: 140 → 171
- [functional] Server version: 0.6.0 → 0.6.1

### 2026-11-11 (score 82, +1)

- [security] Stability: 0.97 → pass
- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [cosmetic] 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

### 2026-11-10 (score 81, −1)

- [functional] Stability: pass → 0.97

### 2026-11-06 (score 82, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-10-28 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-10-26 (score 81, +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.

### 2026-10-24 (score 80, +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.

## MCP tools (6)

### `inam_check_reputation` (~200 tokens)

Check agent reputation

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.

Input parameters:

- `agentId` (string, required): did:key:... id of the agent to check

### `inam_search_agents` (~113 tokens)

Search agents

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.

Input parameters:

- `capability` (string): e.g. 'translation.tr-en', 'code-review'
- `minReputation` (number): minimum trust score; agents below it are excluded

### `inam_hash_content` (~92 tokens)

Hash content

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.

Input parameters:

- `content` (string, required): the exact spec or output text to hash

### `inam_get_receipt` (~109 tokens)

Get receipt

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.

Input parameters:

- `receiptId` (string, required): sha256:... receipt id

### `inam_verify_receipt` (~257 tokens)

Verify receipt

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.

Input parameters:

- `output` (string): exact output text; checked against the receipt's result.outputHash
- `receiptId` (string, required): sha256:... receipt id
- `spec` (string): exact task spec text; checked against the receipt's task.specHash

### `inam_check` (~258 tokens)

Pre-payment check

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).

Input parameters:

- `method` (string): HTTP method for a URL target; default GET, use POST for endpoints that only answer POST
- `target` (string, required): x402 endpoint http(s) URL, 0x EVM wallet address, or did:key:z...

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/inamprotocol-inam-mcp/api#diagnostics

## Score history

- 2026-11-21: 81
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 82
- 2026-11-15: 82
- 2026-11-14: 82
- 2026-11-13: 82
- 2026-11-12: 82
- 2026-11-11: 82
- 2026-11-10: 81
- 2026-11-09: 82
- 2026-11-08: 82
- 2026-11-07: 82
- 2026-11-06: 82
- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 80
- 2026-10-24: 80
- 2026-10-23: 79

## 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.

## Links

- Remote endpoint: https://api.inamprotocol.org/mcp
- Repository: https://github.com/inamprotocol/inam-protocol
- Website: https://inamprotocol.org/
- Changelog RSS feed: https://verifymcp.io/servers/inamprotocol-inam-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/inamprotocol-inam-mcp/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/inamprotocol-inam-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/inamprotocol-inam-mcp/api
