Skip to main content
Glama
Sign In
canary-guard-402

canary-guard-402

by ak10082247-max
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to canary-guard-402

No user-submitted related servers found.

    Related Servers

    • tereno-mcp

      tereno-mcpofficial

      tereno-xyz
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for verifying blockchain safety on Base via x402, with free pricing/receipt tools and paid per-call guard, contract, and metadata checks settled in USDC.
      50 npm
      MIT

    • anchor-x402-mcp

      hypeprinter007-stack
      A
      license
      A
      quality
      B
      maintenance
      9-tool MCP server for the anchor-x402 commodity services: dual-chain hash anchoring (Base + Solana), OFAC sanctions screening, signed decision attestation, mainnet tx decode, ENS/SNS name resolution, USD spot price, EVM calldata decode, datetime parser, and bundled wallet intelligence. Agents pay $0.001–$0.010 USDC per call directly from a Base wallet via x402 — no API keys, no accounts.
      14
      132 npm
      1
      MIT

    • mcp-slim-guard

      lennney
      A
      license
      Not graded
      quality
      C
      maintenance
      Lightweight MCP security proxy — compression (up to 86%) + SSRF protection + allow/deny + audit + rate limiting + injection detection
      58 npm
      180
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.6/5.0

    Scored across 34 tools

    Disambiguation2/5

    Several tool pairs appear to do the same thing: auditEip712SignaturePayload vs auditEip712Signature, auditMcpToolPoisoning vs auditMcpToolSchema, checkWalletDrainer vs analyzeEvmWallet vs checkWalletSanctions vs nansenProfilerAddressBalance, and getPolymarketVerifiedOdds vs getPolymarketOddsPulse. Nearly every description repeats an identical boilerplate 'Call this tool when auditing smart contracts, analyzing wallet addresses, or validating DEX liquidity' line, even for off-domain tools like calculateLlmTokenPricing, which floods the agent with indistinguishable guidance.

    Naming Consistency2/5

    Conventions are mixed: snake_case (canary_sanitize) coexists with camelCase (inspectBaseToken, checkWalletDrainer), and a third namespace-style cluster (nansenSmartMoneyNetflow) is prefixed by a vendor rather than an action. Verb choice is also inconsistent (inspect/check/audit/get/analyze/verify) with overlapping meanings across tools.

    Tool Count2/5

    34 tools is heavy for the stated scope and the surface is padded with near-duplicates (two EIP-712 auditors, two MCP auditors, two Polymarket odds tools, two yield tools). The redundancy means several tools do not earn a distinct place, pushing this into over-large territory.

    Completeness3/5

    Coverage of the Web3 security/market-intel domain is broad (contract, wallet, signature, URL, MCP, sanctions, pricing, whale flow, yields), so no glaring dead ends. However the duplication and thin-gap areas (e.g. no clear consolidated update/report surfaces) mean the set is more redundant than truly complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources