ForgeMesh Utility Grid MCP

What ForgeMesh Utility Grid MCP does

ForgeMesh Utility Grid MCP provides an MCP interface to a changing catalog of more than 400 ForgeMesh APIs. Instead of creating one MCP tool for every upstream route, it exposes a small set of meta-tools for finding routes, inspecting their requirements, and invoking them generically.

The catalog spans practical operations including OCR, image and audio processing, web content extraction, mathematics, unit conversions, geodata, documents, text analysis, time utilities, space data, developer utilities, domains, economy, science, and other categories. New upstream routes become discoverable through the live catalog rather than requiring the package to hardcode each route.

How it works

A typical workflow starts with a free search or category query. After finding a route, an agent can request its exact price, input schema, and worked request and response examples. It can then send a JSON body to the selected path through call_endpoint.

The three paid operations use the x402 flow. The initial request produces an HTTP 402 challenge; the server signs a USDC payment authorization on Base mainnet and retries the request. Settlement information may be included in the response under _payment. Results are wrapped as { source, untrusted, content }, identifying returned content as remote data rather than instructions.

The server reads the upstream OpenAPI description live for capability discovery, with an in-memory cache lasting five minutes. Direct HTTP alternatives are also available through ForgeMesh’s llms.txt, OpenAPI document, and x402 discovery manifest.

Setup and configuration

Run the package through an MCP client with Node.js 20 or newer. A standard stdio configuration uses npx and the package @forgemeshlabs/utility-grid-mcp:

{
  "mcpServers": {
    "utility-grid": {
      "command": "npx",
      "args": ["-y", "@forgemeshlabs/utility-grid-mcp"],
      "env": {
        "WALLET_PRIVATE_KEY": "0x..."
      }
    }
  }
}

WALLET_PRIVATE_KEY is needed for paid tools but can be omitted when only browsing and planning calls. Use a dedicated, low-balance Base wallet funded with USDC. X402_MAX_PRICE_USD and X402_SESSION_BUDGET_USD can reduce the built-in per-call and per-session limits; they cannot raise them.

Tools and capabilities

• list_tools fetches every route with live prices and category totals. It is free and requires no wallet.
• list_capabilities returns category totals or all routes within one category.
• search_capabilities searches route paths, identifiers, and descriptions by keyword.
• get_endpoint_spec returns a route’s price, input schema, and example requests and responses.
• call_endpoint sends a JSON body to any route and manages its x402 payment flow.
• daily_402 selects one featured endpoint from the ForgeMesh fleet based on the UTC date.
• agent_service_directory lists ForgeMesh x402 services with categories, route counts, and price ranges.

Discovery tools are free. call_endpoint costs between $0.005 and $0.05 per call, while daily_402 costs $0.005 and agent_service_directory costs $0.05.

Limitations and notes

Paid requests are restricted to Utility Grid’s approved wallets, Base mainnet, USDC, and the configured spending limits. The server caps a request at 2 MB, applies a 60-second timeout, and does not follow redirects. The session budget defaults to a maximum of $10, and the per-call ceiling is $0.05; configuration can only lower these values.

No account, API key, subscription, or signup is required. A wallet is required only when invoking paid tools. The catalog changes over time, so agents should use the live discovery tools rather than relying on a static route list.

The free list_tools response can contain a disclosed sponsored card passed through from ForgeMesh. The package does not provide ad credentials or contact the advertising network, and paid tool responses do not include that card.