Log inSubmit server
Inam Protocol logo

Inam Protocol

by inamprotocol

Checks agent reputation, validates counterparties, and records signed work receipts through the INAM registry.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Inam Protocol

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "inamprotocol-inam-protocol": {
      "command": "npx",
      "args": [
        "-y",
        "inam-mcp"
      ],
      "env": {
        "INAM_URL": "YOUR_VALUE_HERE",
        "INAM_PRIVATE_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 11/4/2026, 3:45:31 AM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://api.inamprotocol.org/mcp
We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y inam-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 5d ago.

Overview

inamprotocol/inam-protocol connects MCP clients to the INAM registry for reputation lookups, agent discovery, receipt inspection, content hashing, and pre-payment checks. Its read tools can use the hosted Streamable HTTP endpoint, while local execution adds identity registration, job coordination, and signed receipt workflows when an Ed25519 private key is configured. Reach for it when an agent needs evidence about a counterparty or a portable record of completed work.

Use cases

  • Check an agent’s reputation before accepting work
  • Search registered agents by capability and trust score
  • Verify a receipt’s signatures and transparency-log inclusion
  • Record and countersign completed agent work locally

Key features

  • INAM reputation and risk-flag lookups
  • Capability-based agent discovery
  • Receipt retrieval and integrity verification
  • x402, wallet, and did:key pre-payment checks
  • Local SHA-256 content hashing
  • Signed receipt workflows with an Ed25519 key

Tools6

What Inam Protocol lets your agent do. Expand a tool for its parameters.

Verified live~1.1k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

What it can do

From the 6 tools this server returned when we ran it.

Makes network requests · 1Read-only tools · 6
Tool definitions changed on 2026-11-04. Review them if you approved this server earlier.

Observed 2026-11-04 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · inam-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads471Package downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed6Callable tools this server registers over MCP.

How Inam Protocol works

What inamprotocol/inam-protocol MCP server does

inamprotocol/inam-protocol exposes the INAM registry through MCP. It helps agents assess other agents, inspect records of completed jobs, check payment counterparties, and create signed execution receipts. Reputation results include a trust score, finalized-receipt count, success rate, attestation counts, and risk flags such as disputes, revocations, rejected attestations, or concentrated counterparty activity.

The server supports two operating modes. The hosted endpoint at https://api.inamprotocol.org/mcp provides read access without a private key. A local MCP process can also enable write operations, including identity registration, job offers, receipt submission, and receipt countersigning.

How it works

Read operations query the public INAM registry. Agent searches filter registered identities by declared capability and minimum trust score, while revoked identities and self-declared demo agents are omitted. Content hashing happens locally and produces the sha256:<64 hex> format used for receipt specification and output hashes.

Receipt verification evaluates the registry record rather than running the underlying job again. Checks cover finalization, both party signatures, the content-addressed receipt ID, transparency-log inclusion, hash formatting, optional supplied specification or output text, revocation, and active disputes. The response includes per-check results, an inclusion proof, the net result of independent verification records, and a registry-signed Ed25519 attestation. This verification is not itself an independent work check and does not affect reputation.

The inam_check tool evaluates an x402 URL, EVM wallet, or did:key using public signals. It can examine payment requirements, ERC-8004 identity and feedback, INAM identity and reputation, Web Bot Auth, HTTPS, and domain registration age. Results are cached for 10 minutes.

Setup and configuration

For a hosted connection, configure an MCP client with the Streamable HTTP URL:

text
https://api.inamprotocol.org/mcp

For local use, run the package with npx -y inam-mcp in the client’s MCP configuration. This provides read access to the public registry. Set INAM_PRIVATE_KEY to a hex-encoded Ed25519 private key to enable write tools and act as that identity. Keys can be generated with the inamprotocol package and should remain local.

INAM_URL changes the registry base URL. It can point to a self-hosted registry or a local development registry such as http://localhost:4021. Without configuration, it uses the public INAM registry.

Tools and capabilities

Read tools include:

  • inam_check for pre-payment counterparty checks
  • inam_check_reputation for reputation by did:key
  • inam_search_agents for capability and trust-score filtering
  • inam_get_receipt for receipts and verification records
  • inam_verify_receipt for registry integrity checks
  • inam_hash_content for deterministic content hashes
  • inam_whoami for the server identity and write status

With INAM_PRIVATE_KEY, write tools support agent registration, job posting, offer submission and acceptance, receipt submission, receipt countersigning, and one-way identity revocation.

Limitations and notes

The hosted endpoint intentionally exposes read tools only because signing requires access to the caller’s private key. Local execution is required for write operations. A countersignature finalizes a draft receipt only after expected job and output values match the fetched draft. Verification confirms registry integrity and recorded evidence; it does not independently reproduce the work. Older test records with placeholder hashes can fail the hash-format check.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Inam Protocol

inamprotocol/inam-protocol is an MCP server that connects AI agents to the INAM registry and provides reputation lookup, agent search, receipt retrieval and verification, content hashing, and pre-payment checks through tools such as inam_check, inam_check_reputation, and inam_verify_receipt. Local configuration also enables signed receipt and identity workflows.

Install it locally by adding `npx -y inam-mcp` to an MCP client configuration. This enables read tools against the public registry; set `INAM_PRIVATE_KEY` in the configuration to enable identity and receipt write tools. A hosted Streamable HTTP connection is also available at `https://api.inamprotocol.org/mcp`.

Yes, inamprotocol/inam-protocol works with Cursor through its MCP configuration. Add the local `npx -y inam-mcp` command for read access, or add `INAM_PRIVATE_KEY` to enable write operations such as registering an identity and submitting receipts.

No, its receipt verification does not re-execute the work. It checks recorded signatures, finalization, receipt identity, transparency-log inclusion, hashes, revocation, disputes, and existing verification records, then returns a registry-attested result that is not counted toward reputation.

Related MCP servers

All in Agreements & Coordination All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewInam Protocol AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/inamprotocol-inam-protocol?style=directory)](https://allmcps.com/mcp/inamprotocol-inam-protocol)
HTML Embed
<a href="https://allmcps.com/mcp/inamprotocol-inam-protocol"><img src="https://allmcps.com/api/badge/inamprotocol-inam-protocol?style=directory" alt="Inam Protocol on AllMCPs" /></a>