Skip to main content
Glama

insumer_setup

Generate a free API key for on-chain attestation across 31 EVM chains and Solana. Provides 10 verification credits and 100 daily calls. No credit card required.

Instructions

Generate a free InsumerAPI key instantly. No credit card required. Returns an API key (insr_live_...) with 10 verification credits and 100 calls/day. The user should add the key to their MCP config as INSUMER_API_KEY and restart. One free key per email, 3 per IP per day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailYesEmail address for the API key
appNameNoName of your app or project (default: 'MCP Agent')

Implementation Reference

  • The handler function for the insumer_setup tool. It makes a POST request to KEYGEN_URL with the user's email and appName (defaulting to 'MCP Agent'), requesting a free tier API key. Returns the generated key (insr_live_...) with instructions to add it to MCP config as INSUMER_API_KEY.
    server.tool(
      "insumer_setup",
      "Generate a free InsumerAPI key instantly. No credit card required. Returns an API key (insr_live_...) with 10 verification credits and 100 calls/day. The user should add the key to their MCP config as INSUMER_API_KEY and restart. One free key per email, 3 per IP per day.",
      {
        email: z.string().email().describe("Email address for the API key"),
        appName: z.string().max(100).optional().describe("Name of your app or project (default: 'MCP Agent')"),
      },
      async (args) => {
        const res = await fetch(KEYGEN_URL, {
          method: "POST",
          headers: { "Content-Type": "application/json" },
          body: JSON.stringify({
            email: args.email,
            appName: args.appName || "MCP Agent",
            tier: "free",
          }),
        });
        const result = await res.json() as Record<string, unknown>;
        if (result.success && result.key) {
          return {
            content: [{
              type: "text" as const,
              text: [
                `API key generated successfully!`,
                ``,
                `Key: ${result.key}`,
                `Tier: free`,
                `Credits: 10`,
                `Daily limit: 100 calls`,
                ``,
                `To activate, add this to your MCP config:`,
                ``,
                `  "env": { "INSUMER_API_KEY": "${result.key}" }`,
                ``,
                `Then restart your MCP client.`,
              ].join("\n"),
            }],
          };
        }
        return {
          content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
          isError: true,
        };
      }
    );
  • src/index.ts:176-220 (registration)
    Registration of the 'insumer_setup' tool via server.tool(...). The tool is defined with description, Zod schema for input (email required, appName optional), and the async handler function. Also references insumer_setup in console.error messages on lines 12 and 23.
    server.tool(
      "insumer_setup",
      "Generate a free InsumerAPI key instantly. No credit card required. Returns an API key (insr_live_...) with 10 verification credits and 100 calls/day. The user should add the key to their MCP config as INSUMER_API_KEY and restart. One free key per email, 3 per IP per day.",
      {
        email: z.string().email().describe("Email address for the API key"),
        appName: z.string().max(100).optional().describe("Name of your app or project (default: 'MCP Agent')"),
      },
      async (args) => {
        const res = await fetch(KEYGEN_URL, {
          method: "POST",
          headers: { "Content-Type": "application/json" },
          body: JSON.stringify({
            email: args.email,
            appName: args.appName || "MCP Agent",
            tier: "free",
          }),
        });
        const result = await res.json() as Record<string, unknown>;
        if (result.success && result.key) {
          return {
            content: [{
              type: "text" as const,
              text: [
                `API key generated successfully!`,
                ``,
                `Key: ${result.key}`,
                `Tier: free`,
                `Credits: 10`,
                `Daily limit: 100 calls`,
                ``,
                `To activate, add this to your MCP config:`,
                ``,
                `  "env": { "INSUMER_API_KEY": "${result.key}" }`,
                ``,
                `Then restart your MCP client.`,
              ].join("\n"),
            }],
          };
        }
        return {
          content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],
          isError: true,
        };
      }
    );
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the key format (insr_live_...), included credits (10 verification, 100 calls/day), and usage limits. No contradictions with annotations.

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 sentences, each with a distinct purpose: generation, no credit card, what to do with the key, and limits. No redundant or wasted words.

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

Completeness5/5

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

Given the tool's simplicity, the description covers all needed information: what it does, input parameters, output format, post-usage instructions, and rate limits. No output schema, but return value is adequately described.

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% with basic descriptions. The overall description adds context about default appName ('MCP Agent') and confirms email is required, but does not add significant new meaning beyond schema.

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 'Generate a free InsumerAPI key instantly', identifying the specific resource (API key) and action (generate). This sets it apart from sibling tools that deal with discounts, attestation, buying credits, etc.

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?

It provides explicit context: no credit card required, one free key per email, 3 per IP per day, and instructions to add the key to MCP config and restart. It doesn't explicitly state when not to use it, but the purpose is clear enough to distinguish from 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/douglasborthwick-crypto/mcp-server-insumer'

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