cryptopunks-mcp-server

Instructions

Implementation Reference

• src/api.ts:175-188 (handler)

  The actual implementation of getAccount which calls the upstream API.

  export async function getAccount(
    address: string,
    options?: {
      owned?: boolean;
      salesLimit?: number;
      purchasesLimit?: number;
    },
  ) {
    const params: Record<string, string> = {};
    if (options?.owned) params.owned = "true";
    if (options?.salesLimit) params.salesLimit = String(options.salesLimit);
    if (options?.purchasesLimit) params.purchasesLimit = String(options.purchasesLimit);
    return get(DATA_BASE, `/api/account/${address}`, params);
  }

• src/tools.ts:159-170 (schema)

  The schema definition for get_account tool.

  get_account: {
    description:
      "Get comprehensive portfolio data for any Ethereum wallet or ENS name: owned punks, punks for sale, active bids placed and received, full buy/sell history, realized PnL, and total trading volume. This is the most information-dense endpoint in the API.",
    inputSchema: z.object({
      address: ethAddress,
      owned_only: z
        .boolean()
        .optional()
        .default(false)
        .describe("If true, return only owned punks and skip history"),
    }),
  },

• src/handlers.ts:339-343 (registration)

  The registration/handler switch case that maps the tool call to the api.getAccount function.

  case "get_account": {
    const result = await api.getAccount(args.address, {
      owned: args.owned_only ?? false,
    });
    return ok(result);