Skip to main content
Glama

hyperd.wallet.risk

Assess wallet risk by combining Chainalysis sanctions screening with GoPlus heuristics. Returns a sanctioned flag and a 0-100 heuristic score for phishing, mixers, and scams.

Instructions

Check a wallet's risk profile. Combines Chainalysis Sanctions Oracle (OFAC SDN authoritative) with GoPlus address heuristics (mixers, phishing, scams). Returns sanctioned flag + 0-100 heuristic score. Costs $0.10 in USDC.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes0x EVM wallet address
chainNoChain. Default 'base'.
deepNoCross-check across multiple chains. Default false.

Implementation Reference

  • src/server.ts:258-267 (registration)
    Registration of the 'hyperd.wallet.risk' tool via server.tool() with the MCP McpServer instance. Defines tool name, description, input schema (address, chain, deep), and handler.
    server.tool(
      "hyperd.wallet.risk",
      "Check a wallet's risk profile. Combines Chainalysis Sanctions Oracle (OFAC SDN authoritative) with GoPlus address heuristics (mixers, phishing, scams). Returns sanctioned flag + 0-100 heuristic score. Costs $0.10 in USDC.",
      {
        address: z.string().describe("0x EVM wallet address"),
        chain: z.string().optional().describe("Chain. Default 'base'."),
        deep: z.boolean().optional().describe("Cross-check across multiple chains. Default false."),
      },
      async (args) => asText(await paidGet("/api/risk/wallet", args)),
    );
  • Handler function for the tool. Calls paidGet('/api/risk/wallet', args) which executes the x402 paid HTTP request, then formats the JSON response as text via asText().
      async (args) => asText(await paidGet("/api/risk/wallet", args)),
    );
  • Input schema for the tool defined with zod: address (required string), chain (optional string, default 'base'), deep (optional boolean, default false).
    {
      address: z.string().describe("0x EVM wallet address"),
      chain: z.string().optional().describe("Chain. Default 'base'."),
      deep: z.boolean().optional().describe("Cross-check across multiple chains. Default false."),
    },
  • The paidGet() helper function that performs the x402 payment flow: builds the URL with query params, executes paidRequest() which handles the 402 Payment Required dance with x402/EIP-3009.
    async function paidGet(
      path: string,
      query: Record<string, string | number | boolean | undefined>,
    ): Promise<unknown> {
      if (!httpClient) {
        throw new Error(WALLET_NOT_CONFIGURED_MSG);
      }
    
      const url = new URL(`${API_BASE}${path}`);
      for (const [k, v] of Object.entries(query)) {
        if (v !== undefined && v !== "" && v !== null) url.searchParams.set(k, String(v));
      }
      return paidRequest("GET", url, undefined);
    }
  • The asText() helper that wraps the API response JSON into the MCP text content format.
    function asText(data: unknown) {
      return { content: [{ type: "text" as const, text: JSON.stringify(data, null, 2) }] };
    }
Behavior4/5

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

With no annotations, the description discloses data sources, expected outputs (sanctioned flag, 0-100 score), and cost ($0.10). It does not mention idempotency, side effects, or latency, but the core behavioral traits are clear.

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?

The description is a concise three sentences, front-loaded with the main purpose. Every sentence adds value: purpose, data sources/outputs, cost. No wasted words.

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?

Without an output schema, the description adequately explains return values (sanctioned flag + score). It also mentions cost. However, it could cover error conditions or response format in more detail.

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

Parameters3/5

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

Schema coverage is 100%, so parameters are already described. The description adds no additional meaning beyond what is in the schema (e.g., no elaboration on 'deep' cross-check). Baseline of 3 is appropriate.

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?

The description clearly states 'Check a wallet's risk profile' with specific verb and resource. It distinguishes from siblings by detailing data sources (Chainalysis, GoPlus) and outputs (sanctioned flag + heuristic score), making it clear what this tool does uniquely.

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

Usage Guidelines3/5

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

The description implies use when checking risk, but provides no explicit guidance on when to use this tool versus siblings like hyperd.wallet.anomaly or hyperd.wallet.persona. It does not state exclusions or alternatives.

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/hyperd-ai/hyperd-mcp'

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