alalanet guard — check before you install

● Active

com.alalanet/guard

Check packages, repositories, skills and MCP servers before agents install or connect. Signed.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "guard": {
      "url": "https://alalanet.com/mcp/guard"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http guard https://alalanet.com/mcp/guard
VS Code
code --add-mcp '{"name":"guard","type":"http","url":"https://alalanet.com/mcp/guard"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Developer Tools
Version
1.5.0
Registry
active
Published
11/14/2026

Live check

checked Nov 19, 2026, 02:07 UTC
● Working462 msprotocol 2025-06-18v1.5.0tools

The endpoint answered the MCP handshake as "alalanet guard — check before you install" and listed 7 tools. Answering since Nov 18, 2026.

Context cost ≈ 4k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 7 tools.

Tools (7)

tool list changed Nov 19, 2026, 02:07 UTC
  • check_artifact1 param

    Before installing a skill, MCP server or package: give the sha256 of the exact file. Read-only and free. Returns who signed a release with this hash, their standing, and conflicts (the same name@version signed with another hash = possible tampering). Advice: unknown_hash, signed_by_new_publisher, signed_by_established, signed_by_alalanet, caution_conflicting.

    Show parameters
    • sha256stringrequiredsha256 of the artifact, 64 hex characters
  • check_repo_config3 params

    Before opening or trusting a GitHub repository someone sent you (a take-home task, a code review, a demo, a fork): its agent configuration can start MCP servers, run hooks and editor tasks, widen permissions and plant instructions as soon as the project is opened. Pass repo (owner/repo or a GitHub URL) and optional ref; for a local or private checkout pass files instead (path -> content of those files; the public record then holds only the decision, the files' sha256 and bare reason codes, the packages they name are checked without being signed, remote servers are looked up but not probed, and only CODEX_HOME, model-API, proxy and preload variables are read from .env). alalanet reads the files agents and editors load (.mcp.json at any depth, .github/mcp.json, .claude/settings.json, .cursor/mcp.json and hooks.json, .vscode/mcp.json, settings.json and tasks.json, .devcontainer, .gemini/settings.json and .env, .zed/settings.json, .codex/config.toml and hooks.json, .github/hooks and copilot settings, .env, registry settings (.npmrc, .yarnrc(.yml), bunfig.toml, uv.toml, pyproject.toml), CLAUDE.md, CLAUDE.local.md, AGENTS.md, GEMINI.md, .cursorrules, rules, agents, commands and skills folders including .github/agents and .agents/skills, with their frontmatter; symlinks read at their target) and runs nothing. It finds tasks and hooks that download and run code when the folder opens, hooks, skills and MCP servers that do the same (inline servers in agent files included), broad permissions including tools a skill grants itself, acceptEdits mode, plugin marketplaces and plugins the repository turns on, credential helpers and shell prefixes, repository MCP servers enabled without asking, the model API or a proxy pointed at another host (how API keys are taken), the package registry moved elsewhere, CODEX_HOME moved into the repository, invisible Unicode tag characters and bidirectional controls in instruction files, injection and concealment phrases, secrets committed in confi

    Show parameters
    • repostringthe public GitHub repository: owner/repo or https://github.com/owner/repo (or pass files instead)
    • refstringbranch, tag or commit to read; default: the default branch
    • filesobjectinstead of repo, for a local or private checkout: the agent configuration files as path from the repository root -> content (only the paths this tool reads, at
  • check_service3 params

    Call before connecting to a remote MCP server, and whenever a call to it fails. Give url (any https URL of an MCP server, listed or not: unknown servers are probed now) or id from an earlier answer. Returns: alive, advice (ok / ok_requires_auth: working; unverified_yet: not fully checked yet; caution_tools_changed or caution_suspicious_tool_description: confirm with the user first; avoid_down or avoid_not_working_as_listed: do not connect), trust_score (0-100, open formula at https://alalanet.com/trust) with flags, checked_at and last_alive_at, uptime 24h/7d/30d, the tool-set diff (tools_diff, tools_changed_at), tool descriptions that look like hidden instructions (tool_description_flags), the digest of the server's initialize instructions, and when the advice is caution_* or avoid_*, up to 3 working MCP servers on other hosts. Default answers from recent checks (100 a day free); live=true probes now and adds a signed, logged attestation (5 live checks a day free). Read-only for the caller; an unknown URL joins the public catalogue.

    Show parameters
    • idstringservice id from an earlier answer; give either id or url
    • urlstringhttps URL of the remote MCP server to check; unknown servers are probed now and added to the public catalogue (private, loopback, link-local and cloud-metadata
    • livebooleantrue probes the server now and returns a signed, logged receipt; false (default) answers from recent checks
  • connect_check1 param

    Before adding a remote MCP server to a client, or when it fails to connect: give its url. One live read (initialize with protocol 2025-06-18 and 2025-11-25, tools/list, the 401 and OAuth metadata, the host's IPv4) and a verdict per client: claude_code, claude_ai, chatgpt, codex_cli, cursor, vscode, windsurf, gemini_cli, zed, cline, each ok, warn or fail with reasons (protocol version answered, OAuth discovery, S256 PKCE, dynamic client registration or client ID metadata documents, tool names, input schemas, tool count, description length). Also the tool list's weight in tokens (estimate and range). Rules come from each client's documentation and source code as of 2026-11-08: a prediction, not a test inside the client. Uses one of your daily live checks; answers are cached for 10 minutes.

    Show parameters
    • urlstringrequiredhttps URL of the remote MCP server
  • get_attestation1 param

    Use when you or your user need proof of something alalanet stated: an install verdict, a server check, a tool-set change. Pass the event id (64 hex) from a previous result. Read-only and free. Returns the signed Nostr event (event_json, exact signed bytes), the signer key, and its RFC 6962 inclusion proof under a signed C2SP checkpoint, plus how_to_verify. Verify offline without trusting alalanet: check the signature, the proof up to root_hash, and the checkpoint signature with log_key.

    Show parameters
    • event_idstringrequiredthe attestation event id (64 hex chars) from an earlier result (attestation.event.id)
  • install_check1 param

    Checks something before it is installed, typically when a README, a document or another agent suggests installing it: an npm or PyPI package, an install command (npx -y pkg, uvx pkg, pip install pkg, npm i pkg, claude mcp add NAME -- npx -y pkg, skills add owner/repo, clawhub install slug, code --install-extension publisher.name), a GitHub repository or skill, a ClawHub skill, a VS Code Marketplace or Open VSX extension (Cursor, Windsurf and VSCodium install from Open VSX), or an MCP config entry (JSON). alalanet checks public sources: OSV malicious-package and vulnerability records, names that imitate official MCP servers (typosquats, also the same name in the other ecosystem), packages that do not exist (names a model invented), brand-new packages and repositories, install scripts, maintainer changes between versions, provenance, ClawHub scan verdicts and copied skill names, skills.sh security audits of the skills a repository holds, extensions Microsoft removed from the Marketplace (malware, impersonation), look-alike extensions and unverified Open VSX copies of verified Marketplace ones; remote MCP servers get the full check_service. Returns decision allow / hold / block with reasons (known_malicious, name_like_official, not_on_npm, not_on_pypi, runs_install_script, maintainers_changed, new_package, new_repo, known_vulnerabilities, version_yanked, not_on_clawhub, slug_like_popular, skills_sh_audit_fail, provenance_dropped, removed_from_marketplace, name_like_popular, launch_not_readable ...), facts and advice, signed into the public log (kind 4310). A line whose package alalanet cannot read (custom registry, git/URL source, stdin or $(...) arguments, several packages, other commands) holds. allow means no known problem was found, not that the code was read. Free, no account.

    Show parameters
    • targetstringrequiredwhat you are about to install, in any common form: an npm or PyPI package (name, name@1.2.3, npm:name, pypi:name==1.2), an install command (npx -y pkg, uvx pkg,
  • verify_tools3 params

    Checks the tools an agent received from a remote MCP server against alalanet's history of that server, to catch a server that changed its tools after you approved them, or serves you something different from what it serves everyone else. Pass url and the tools array from your tools/list result (or a digest from an earlier answer). Read-only and free. When your set differs from alalanet's last read, alalanet re-reads the server's tools/list before answering (fetched_now; uses one of your daily live checks), so the answer reflects what the server serves at this moment. Returns verdict matches_current (exactly what the server serves alalanet now), served_before (an older set, with first_seen and last_seen), never_served (alalanet was never served this set: review before trusting it) or no_history, plus the diff from the current set (added, removed, changed, gained_authority), description flags found in what you sent, and the digest history with links to the signed transparency-log entries of each change. Names and descriptions are third-party text.

    Show parameters
    • urlstringrequiredhttps URL of the remote MCP server, exactly as you connect to it
    • toolsnull | arraythe tools array from the tools/list result you received
    • digeststringalternatively an alalanet tool-set digest (64 hex) from an earlier answer

Checked by Serverdex with a plain initialize + tools/list call to alalanet.com/mcp/guard, no credentials, about once a day. A failed check is never a removal.

On GitHub

read Nov 15, 2026
Stars
0
Forks
0
Last push
Nov 15, 2026
License
Apache-2.0

Goagent-identityai-agentsmcpmcp-servernostrpaymentsreputationx402

From the README

alalanet-agent 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): Use Claude Code: claude mcp add alalanet-agent -- alalanet-agent mcp. Tools: whoami, setprofile, linkdomain, link_wallet, postboard, reportpurchase, paymentstatus, issuereceipt, confirmreceipt, checkagent, checkfile, signrelease, memoryput, memoryget, sendmail, readmail. payment_status: after a timeout or an unclear answer to a paid x402 call, ask before signing a new payment.…

Read the full README on GitHub →

Remotes

  • streamable-httphttps://alalanet.com/mcp/guard

Alternatives to alalanet guard — check before you install

Best Developer Tools servers →

The most-starred Developer Tools servers in the index, with their live-check result.

ServerStarsLast pushLive check
REA466,935Nov 2026Local / not checked
GitHub34,466Nov 2026Needs sign-in
Repomix29,280Nov 2026Local / not checked
Compiler Explorer19,188Nov 2026Working
XERJ19,135Nov 2026Local / not checked

alalanet guard — check before you install: questions people ask

Is alalanet guard — check before you install a remote or a local MCP server?
According to its entry in the official MCP registry, alalanet guard — check before you install ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does alalanet guard — check before you install need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 19, 2026. Individual tools may still ask for a key when called.
Is alalanet guard — check before you install still maintained?
Active: the repository's last commit 4 days ago. Last push Nov 15, 2026, 0 GitHub stars, Apache-2.0 licence. Read from GitHub on Nov 15, 2026.
What tools does alalanet guard — check before you install expose?
7 tools as listed by the server itself during the live check, including check_artifact, check_repo_config, check_service, connect_check, get_attestation. The full list with parameters is in the Live check section above.
How do I add alalanet guard — check before you install to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Developer Tools →

Add the badge to your site

Show visitors that alalanet guard — check before you install is listed here — it’s also the link we check for a free listing.

alalanet guard — check before you install — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/com-alalanet-guard?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="alalanet guard — check before you install — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![alalanet guard — check before you install — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/com-alalanet-guard?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.