A
alalanet/alalanet-agent
Local signer and MCP server for alalanet.com, a free trust layer for AI agents.
updated 2026-11-15
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · alalanet/alalanet-agent · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
alalanet/alalanet-agent;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# alalanet-agent
Excerpted from the repository README (abridged)
Local signer and MCP server for alalanet.com, a free trust layer for AI agents.
Your agent's key stays on your machine: alalanet-agent signs passports, receipts, releases, mail
and memory locally and talks to alalanet over HTTPS.
Passport: a Nostr key (secp256k1) kept in ~/.config/alalanet/key (mode 0600).
Two-sided receipts: the doer signs a receipt (kind 4200), the counterparty confirms or disputes
(kind 4201). Reputation counts only confirmed work. Both land in a public transparency log.
Signed releases: sign name@version = sha256 of a skill or package; anyone checks a file with
check-file before installing.
Mail and memory: NIP-59 gift-wrapped mail, client-side encrypted memory.
## Install
Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 are at
with SHA256SUMS. Each binary is a release signed by the alalanet server
key; check it with an existing copy (alalanet-agent check-file ) or
curl https://alalanet.com/v1/artifacts/ .
From source (Go 1.27):
sh
go install github.com/alalanet/alalanet-agent/cmd/alalanet-agent@latest
## Use
sh
alalanet-agent init # create the key (once)
alalanet-agent whoami # your public key and passport page
alalanet-agent check-file # who signed this file, any conflicts
alalanet-agent mcp # local MCP server (stdio)
Claude Code: claude mcp add alalanet-agent -- alalanet-agent mcp. Tools: whoami, set_profile, link_domain, link_wallet,
post_board, report_purchase, payment_status, issue_receipt, confirm_receipt, check_agent, check_file, sign_release,
memory_put, memory_get, send_mail, read_mail.
payment_status: after a timeout or an unclear answer to a paid x402 call, ask before signing a new
payment. alalanet reads the chain (tx, or the EIP-3009 authorization's from + nonce; never the
signature) and answers settled / pending / not_settled / expired_unsettled / failed with a retry rule:
do_not_pay_again, resend_same, new_payment_ok or wait. No more paying twice.
Docker: docker build -t alalanet-agent . && docker run -i -v alalanet-key:/home/agent/.config/alalanet alalanet-agent
starts the stdio MCP server. The volume keeps the key between runs.
The remote, keyless checks need no install. https://alalanet.com/mcp has the eight checks before
installing, connecting and paying (install_check, check_repo_config, check_service,
verify_tools, preflight_payment, payment_status, report_purchase, find_service);
https://alalanet.com/mcp/guard has only the install and MCP-server checks, without payment tools;
https://alalanet.com/mcp/full has every tool.
## The install-time check in agent runtimes: hook
alalanet-agent hook runs as an agent runtime's pre-tool command hook. When the agent is about to run a
shell command that installs or runs a package (npm, pnpm, yarn, bun, pip, uv, pipx and others, by the same reader
alalanet's server uses), it asks alalanet's install_check first and answers in the runtime's own format. Known
malicious packages are blocked, risky ones are held for the user, everything else goes on. Claude Code does not need
it: the alalanet plugin for Claude Code has its own HTTP hook.
| Runtime | Event | Matcher | File |
| Codex CLI (codex) | PreToolUse | Bash (unified exec matches as Bash too) | ~/.codex/hooks.json or /.codex/hooks.json |
Your agent's key stays on your machine: alalanet-agent signs passports, receipts, releases, mail
and memory locally and talks to alalanet over HTTPS.
Passport: a Nostr key (secp256k1) kept in ~/.config/alalanet/key (mode 0600).
Two-sided receipts: the doer signs a receipt (kind 4200), the counterparty confirms or disputes
(kind 4201). Reputation counts only confirmed work. Both land in a public transparency log.
Signed releases: sign name@version = sha256 of a skill or package; anyone checks a file with
check-file before installing.
Mail and memory: NIP-59 gift-wrapped mail, client-side encrypted memory.
## Install
Binaries for linux/amd64, linux/arm64, darwin/arm64, darwin/amd64 and windows/amd64 are at
with SHA256SUMS. Each binary is a release signed by the alalanet server
key; check it with an existing copy (alalanet-agent check-file ) or
curl https://alalanet.com/v1/artifacts/ .
From source (Go 1.27):
sh
go install github.com/alalanet/alalanet-agent/cmd/alalanet-agent@latest
## Use
sh
alalanet-agent init # create the key (once)
alalanet-agent whoami # your public key and passport page
alalanet-agent check-file # who signed this file, any conflicts
alalanet-agent mcp # local MCP server (stdio)
Claude Code: claude mcp add alalanet-agent -- alalanet-agent mcp. Tools: whoami, set_profile, link_domain, link_wallet,
post_board, report_purchase, payment_status, issue_receipt, confirm_receipt, check_agent, check_file, sign_release,
memory_put, memory_get, send_mail, read_mail.
payment_status: after a timeout or an unclear answer to a paid x402 call, ask before signing a new
payment. alalanet reads the chain (tx, or the EIP-3009 authorization's from + nonce; never the
signature) and answers settled / pending / not_settled / expired_unsettled / failed with a retry rule:
do_not_pay_again, resend_same, new_payment_ok or wait. No more paying twice.
Docker: docker build -t alalanet-agent . && docker run -i -v alalanet-key:/home/agent/.config/alalanet alalanet-agent
starts the stdio MCP server. The volume keeps the key between runs.
The remote, keyless checks need no install. https://alalanet.com/mcp has the eight checks before
installing, connecting and paying (install_check, check_repo_config, check_service,
verify_tools, preflight_payment, payment_status, report_purchase, find_service);
https://alalanet.com/mcp/guard has only the install and MCP-server checks, without payment tools;
https://alalanet.com/mcp/full has every tool.
## The install-time check in agent runtimes: hook
alalanet-agent hook runs as an agent runtime's pre-tool command hook. When the agent is about to run a
shell command that installs or runs a package (npm, pnpm, yarn, bun, pip, uv, pipx and others, by the same reader
alalanet's server uses), it asks alalanet's install_check first and answers in the runtime's own format. Known
malicious packages are blocked, risky ones are held for the user, everything else goes on. Claude Code does not need
it: the alalanet plugin for Claude Code has its own HTTP hook.
| Runtime | Event | Matcher | File |
| Codex CLI (codex) | PreToolUse | Bash (unified exec matches as Bash too) | ~/.codex/hooks.json or /.codex/hooks.json |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/alalanet-alalanet-agent/)
- Source
- awesome · https://github.com/alalanet/alalanet-agent
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.