Skip to main content
Glama
hypeprinter007-stack

anchor-x402-mcp

by hypeprinter007-stack
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

screen_wallet

Check any EVM or Solana wallet against OFAC sanctions lists. Returns sanctions match, flagged programs (Tornado Cash, Lazarus Group), and risk verdict for AML pre-flight checks.

Instructions

Sanctions + AML screening for any EVM or Solana wallet address. Returns sanctions match (boolean), specific OFAC SDN programs flagged (Tornado Cash, Lazarus Group, Hydra Market, Garantex, Blender.io etc.), inferred chain, and a low/medium/high risk verdict. Use for AML pre-flight checks before any treasury transfer, KYC onboarding, vendor diligence, payroll wallet verification, marketplace counterparty checks. $0.001 USDC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletYesEVM 0x… address (40 hex) or Solana base58 pubkey.

Implementation Reference

  • index.js:221-225 (handler)
    The handler for screen_wallet builds a GET request to the API endpoint with the wallet address as a query parameter.
    case "screen_wallet":
  return {
    url: `${BASE_URL}/v1/screen?${new URLSearchParams({ wallet: args.wallet })}`,
    opts: { method: "GET" },
  };
  • index.js:91-103 (schema)
    Tool definition and input schema for screen_wallet: requires a 'wallet' string (EVM 0x… or Solana base58).
    name: "screen_wallet",
description:
  "Sanctions + AML screening for any EVM or Solana wallet address. Returns sanctions match (boolean), specific OFAC SDN programs flagged (Tornado Cash, Lazarus Group, Hydra Market, Garantex, Blender.io etc.), inferred chain, and a low/medium/high risk verdict. Use for AML pre-flight checks before any treasury transfer, KYC onboarding, vendor diligence, payroll wallet verification, marketplace counterparty checks. $0.001 USDC.",
inputSchema: {
  type: "object",
  properties: {
    wallet: {
      type: "string",
      description: "EVM 0x… address (40 hex) or Solana base58 pubkey.",
    },
  },
  required: ["wallet"],
},
  • index.js:202-204 (registration)
    screen_wallet is registered as part of the TOOLS array which is served via ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
  tools: TOOLS,
}));

Tool Definition Quality

A4.4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description carries full burden. Discloses return fields (sanctions match, OFAC programs, chain, risk verdict) and cost. No mention of rate limits or error handling, but key behaviors are covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four concise sentences, front-loaded with purpose. Every sentence adds value (purpose, inputs, outputs, use cases, cost). No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations or output schema, the description adequately explains inputs, outputs, use cases, and cost. Could elaborate on error cases or chain detection, but overall sufficient for a single-parameter tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter description. Description reinforces accepted address formats (EVM hex or Solana base58) and adds context about chain inference. Goes beyond schema by specifying output details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Sanctions + AML screening for any EVM or Solana wallet address', using specific verb (screening) and resource. Distinguishes from siblings like intel_wallet or decode_tx by focusing on sanctions compliance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly lists use cases: AML pre-flight checks, KYC onboarding, vendor diligence, etc. Does not mention when not to use or alternatives, but the guidance is clear and comprehensive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hypeprinter007-stack/anchor-x402-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server