Home / MCP registry index / io.github.ak10082247-max/canaryguard-402

CanaryGuard 402

io.github.ak10082247-max/canaryguard-402 in the official MCP registry. Endpoint https://canaryguard-402.onrender.com/mcp. Source: github.com/ak10082247-max/canaryguard-402.

The registry describes it as: Deterministic prompt-injection detection & sanitization for AI agents via x402 on Base.

Tools it advertises

canary_sanitize inspectBaseToken checkWalletDrainer auditMcpToolPoisoning guardAgentMemory inspectPhishingUrl checkSmartContractHoneypot auditEip712SignaturePayload getSafeBaseTrending getPolymarketVerifiedOdds runFullEnterpriseRiskAudit verifyAgentAttestation getOndemandMarketSnapshot getTokenHistoryAndSpread getSafeYieldAllocation analyzeEvmWallet inspectContractInfo checkWalletSanctions inspectUniswapPoolState getCryptoPriceOnchain repairAndSanitizeJson auditUrlAgentReadiness decodeBaseTxStatus getPolymarketOddsPulse getSafeDefiYields calculateLlmTokenPricing auditEip712Signature auditMcpToolSchema

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ak10082247-max-canaryguard-402/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ak10082247-max-canaryguard-402)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers