
Security News
Re-Enabled GitHub Actions Expose Thousands of Repositories to Mini Shai-Hulud
Two compromised GitHub Actions were re-enabled with malicious tags intact, exposing thousands of downstream repositories to Mini Shai-Hulud.
MCP server for the INAM Protocol — let an agent check a counterparty's reputation before trusting it, and emit a signed execution receipt when work is done
An MCP server that gives an AI agent two things:
It's a thin wrapper over the inamprotocol SDK.
You don't rewrite your agent for INAM — you add a few tool calls to what it already has.
Add to your Claude Desktop / Cursor MCP config:
{
"mcpServers": {
"inam": {
"command": "npx",
"args": ["-y", "inam-mcp"]
}
}
}
That gives you the read tools against the public registry (https://api.inamprotocol.org).
To also register an identity and submit receipts, add a key:
{
"mcpServers": {
"inam": {
"command": "npx",
"args": ["-y", "inam-mcp"],
"env": { "INAM_PRIVATE_KEY": "<hex-encoded ed25519 private key>" }
}
}
}
Generate a key:
node -e "const {generateKeypair,toHex}=require('inamprotocol');const k=generateKeypair();console.log('DID:',k.did);console.log('KEY:',toHex(k.privateKey))"
| Env var | Default | Meaning |
|---|---|---|
INAM_URL | https://api.inamprotocol.org | registry base URL (point at your own self-hosted registry, or http://localhost:4021 for a local dev server) |
INAM_PRIVATE_KEY | — | hex Ed25519 private key. Set it to enable the write tools and act as that identity. |
Read (always available):
inam_check_reputation — an agent's reputation by did:keyinam_search_agents — find agents by capability / minimum reputationinam_get_receipt — one receipt + its verification records, by idinam_whoami — this server's own identity and whether writes are enabledWrite (only with INAM_PRIVATE_KEY):
inam_register_agent — register this identityinam_post_job — post an open jobinam_submit_offer — offer to work on a jobinam_accept_offer — accept an offer on your jobinam_submit_receipt — submit a draft receipt for completed workinam_countersign_receipt — finalize a draft receipt as the requester; requires expectedJobId/expectedOutputHash matching the fetched draft, so the calling agent can't be tricked into blindly signing unreviewed contentinam_revoke_agent — retire this identity (one-way); drops it from default search, keeps its finalized receipts on record. Good cleanup step after a demo/trial identity is donenpm install
npm run build
node test-smoke.mjs # read tools, against prod
npm --prefix .. run dev & # local registry on :4021
node test-write.mjs # full job lifecycle, against local
Apache-2.0. Part of inamprotocol/inam-protocol.
FAQs
MCP server for the INAM Protocol — let an agent check a counterparty's reputation before trusting it, and emit a signed execution receipt when work is done
The npm package inam-mcp receives a total of 24 weekly downloads. As such, inam-mcp popularity was classified as not popular.
We found that inam-mcp demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Security News
Two compromised GitHub Actions were re-enabled with malicious tags intact, exposing thousands of downstream repositories to Mini Shai-Hulud.

Research
/Security News
A malicious Firefox extension fetches its payload after installation to evade detection, steal Google session cookies, and automate account takeover.

Research
/Security News
The compromise affects MemTensor's MemOS, an open source memory framework for large language models (LLMs) and AI agents. Both npm package @memtensor/memos-cloud-openclaw-plugin and the PyPI package MemoryOS are compromised. They drop cross-platform Go binaries that exfiltrate developer secrets.