Categories › AI & Agents › Multi-agent, orchestration & workflows
Check packages, MCP servers and x402 endpoints before agents install, connect or pay. Signed.
Remote server: your requests and data go to alalanet.com. Claude Code: claude mcp add --transport http alalanet-check-before-your-agent-install https://alalanet.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
check_repo_config — Before opening or trusting a GitHub repository someone sent you (a take-home task, a code review, a demo, a fork): its agent configuration ccheck_service — Call before the first payment to an x402 endpoint, before connecting to an MCP server, and whenever a call to it fails. Give url (any https find_service — Use when you need a paid API or MCP server for a task, or a working alternative after a call failed. Pass query in plain words (e.g. weatherinstall_check — Checks something before it is installed, typically when a README, a document or another agent suggests installing it: an npm or PyPI packagepayment_status — Tells whether an x402 payment settled, for use after a timeout, a 5xx or any unclear answer to a paid request and before a new payment is sipreflight_payment — Decision for one x402 payment, made right before it is signed. Pass the endpoint url and the 402 it returned (PAYMENT-REQUIRED header value report_purchase — After you paid an x402 endpoint on Base or Solana (network eip155:8453, base, solana or solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp): report theverify_tools — 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 toNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.