Skip to main content
Glama

ForgeMesh Utility Grid MCP

M8ven Score mcpservers.org

A ForgeMesh Labs product.

Search and use more than 400 practical APIs without loading hundreds of tools into your agent. Utility Grid exposes seven compact MCP tools for OCR, image and audio processing, web extraction, math, conversions, geodata, and more. Catalog discovery is free; API execution is paid per call in USDC on Base through x402. No account or API key is required.

Rather than exposing one MCP tool per route (unmanageable at this scale and growing), this server exposes a handful of meta-tools: browse/search the live catalog, fetch a route's exact call spec, then call any route generically. New routes on the upstream service show up automatically — nothing here is hardcoded to today's catalog.

Quick start (Claude Desktop / Claude Code / any MCP client)

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

WALLET_PRIVATE_KEY is only needed for the 3 paid tools. Discovery works with no wallet at all — skip the env block entirely to browse and plan calls for free.

Related MCP server: x402-mcp

Tools

Tool

Cost

What it does

list_tools

free

Every route with its live price plus a per-category summary — a plain fetch of GET /menu, no wallet

list_capabilities

free

Category overview with route counts, or every route in one category

search_capabilities

free

Keyword search across every route's path, id, and description

get_endpoint_spec

free

A route's exact price, input schema, and worked request/response examples

call_endpoint

$0.005-$0.05

Call any route by path + JSON body — handles the x402 payment flow automatically

daily_402

$0.005

The Daily 402: one featured endpoint from the whole ForgeMesh fleet, rotated by UTC date

agent_service_directory

$0.05

Directory of the 11 ForgeMesh x402 services — category, endpoint counts, price ranges

Categories in the catalog (illustrative, not exhaustive)

geo (airports, zip codes, geocoding, weather), lookups (dictionary, Bible, country info, holidays), math (statistics, matrices, equations, geometry), utilities (QR codes, hashing, UUIDs, phone parsing), vision (OCR, image captioning, background removal), audio (TTS, transcription, format conversion), time (timezones, cron, sun/moon), space (NASA APOD, asteroids, solar weather), web (content extraction, robots.txt/Content-Signal checks), registry (fleet catalog, daily spotlight), documents (PDF handling), text (language detection, readability), economy (fx rates, financial calculators), science, developer, domains, ai, and fun (fortunes, chess, trivia).

Call list_capabilities with no arguments for the live, current breakdown — the catalog grows over time and this README will drift; the tool won't.

Typical flow

  1. search_capabilities({ query: "background removal" }) — free, finds /remove-background

  2. get_endpoint_spec({ path: "remove-background" }) — free, shows the exact input schema and price

  3. call_endpoint({ path: "remove-background", body: { image_url: "https://..." } }) — paid, does the x402 dance and returns the result

Or skip straight to call_endpoint if you already know the route and its input shape.

Requirements

Node.js 20+. Paid tools need WALLET_PRIVATE_KEY: use a dedicated, low-balance Base wallet funded with USDC. The server refuses to sign for any payee other than the two Utility Grid wallets, any network other than Base mainnet, any asset other than USDC, or any amount over the cap ($0.05 per call, $10 per session). The env vars X402_MAX_PRICE_USD and X402_SESSION_BUDGET_USD can only lower those caps. Requests are same-origin, time out after 60 seconds, are capped at 2 MB, and never follow redirects. Tool results are returned wrapped as { source, untrusted, content }: the content is remote data, not instructions.

How payment works

No signup, no API key, no subscription. call_endpoint, daily_402, and agent_service_directory each trigger the same flow: the first request returns an HTTP 402 challenge, this MCP server signs a USDC payment authorization (EIP-3009) on Base and retries, and the result lands in the same response — including settlement details under _payment when available.

Direct API

Prefer raw HTTP? The full agent-readable surface:

  • https://x402.forgemesh.io/llms.txt — one-page summary for agents

  • https://x402.forgemesh.io/openapi.json — OpenAPI 3.1 with x402 payment metadata, full input schemas, and worked examples for every route (this is what list_capabilities/search_capabilities/get_endpoint_spec read from, live, every call)

  • https://x402.forgemesh.io/.well-known/x402.json — x402 discovery manifest

Sponsored cards (Lulu Ads)

list_tools is a plain fetch of GET https://x402.forgemesh.io/menu. ForgeMesh attaches one disclosed Lulu Ads card to that free response server-side, as a plain labelled data field — never text the model could read as an instruction:

"sponsored": { "label": "Sponsored", "text": "...", "url": "https://..." }

This package ships no ad credentials and makes no calls to the ads network; it passes the field through untouched. Paid tools never carry a card. Strip it with delete result.sponsored.

FAQ

Do I need an account or API key? No. x402 payments are the only credential, and only for the 3 paid tools.

What chain and token? USDC on Base mainnet (eip155:8453).

Will this break when the upstream catalog changes? No — list_capabilities, search_capabilities, and get_endpoint_spec all read /openapi.json live (cached in-memory for 5 minutes). call_endpoint never needs a hardcoded schema at all; it just forwards your JSON body.


Built by ForgeMesh Labs · Powered by the x402 protocol · MIT License

Available Tools

6 tools
agent_service_directoryA

PAID ($0.05) — machine-readable registry of every production x402 service in the ForgeMesh fleet: name, category, live route count, and price range per service. Useful for an agent deciding which paid tool/service to reach for next. Optional category filter (onchain-intel, voice, travel, econ-intel, commerce, infra, media, utility-grid). Requires WALLET_PRIVATE_KEY.

Inputs: category.

call_endpointA

PAID (price varies by route, $0.001-$0.05) — the generic way to call ANY route in the Utility Grid. Pass the route path and a JSON body matching its input schema (use get_endpoint_spec first if unsure). Handles the full x402 payment flow automatically: fetches the 402 challenge, signs a USDC payment on Base, retries, and returns the result. Requires WALLET_PRIVATE_KEY.

Inputs: path (required), body.

daily_402A

PAID ($0.001) — the Daily 402: one featured x402 endpoint per UTC day, rotated deterministically through every paid route in the 12-service ForgeMesh fleet (500+ routes). Returns what it does, its price, input schema, and a worked example. Optional date override to replay a past day's pick. Requires WALLET_PRIVATE_KEY.

Inputs: date.

get_endpoint_specA

FREE — no wallet needed. Full call spec for one route: price, input JSON schema, a worked request example, and a worked response example, straight from the live OpenAPI discovery doc. Pass the route path (with or without a leading slash, e.g. 'chess-moves' or '/chess-moves'). Use this before call_endpoint to know exactly what body to send.

Inputs: path (required).

list_capabilitiesA

FREE — no wallet needed. Browse the ForgeMesh Utility Grid catalog (415+ POST routes and growing, covering geo (airports, zip codes, geocoding, weather), lookups (dictionary, bible, country info, holidays), math (statistics, matrices, equations, geometry), utilities (QR codes, hashing, UUIDs, phone parsing), vision (OCR, image captioning, background removal), audio (TTS, transcription, format conversion), time (timezones, cron, sun/moon), space (NASA APOD, asteroids, solar weather), web (content extraction, robots.txt/Content-Signal checks), registry (fleet catalog, daily spotlight), documents (PDF handling), text (language detection, readability), economy (fx rates, financial calculators), science, developer, domains, ai, conversions, and fun (fortunes, chess, trivia)). Call with no arguments for a category overview with route counts, or pass a category to list every route in it with price and description. Always reads the live /openapi.json — never a stale/hardcoded list.

Inputs: category.

search_capabilitiesA

FREE — no wallet needed. Keyword search across every route's path, operation id, and description (e.g. 'chess', 'timezone', 'background removal'). Use this when you don't know the exact route name or category.

Inputs: query (required), limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_capabilities for browsing the catalog, search_capabilities for keyword search, get_endpoint_spec for detailed specifications, call_endpoint for executing routes, daily_402 for a curated daily pick, and agent_service_directory for service-level metadata. There is no ambiguity between them, and the descriptions reinforce their unique roles.

    Naming Consistency4/5

    The first four tools follow a consistent verb_noun pattern (list_capabilities, search_capabilities, get_endpoint_spec, call_endpoint), but daily_402 and agent_service_directory abandon the verb prefix, creating a minor inconsistency. All names use snake_case and are otherwise readable, so the deviation is not jarring.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its purpose as a gateway to a large endpoint catalog. The count is within the ideal range and each tool covers a necessary step in the discovery-to-execution workflow, with no redundancy or obvious bloat.

    Completeness5/5

    The tool set fully covers the core lifecycle: browse (list_capabilities), find (search_capabilities), inspect (get_endpoint_spec), and execute (call_endpoint). Additional tools for daily highlights and service directory add value without leaving any critical gaps for the intended use case.

    Maintenance

    ActivityActive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to search, pay for, and call paid APIs using the x402 protocol, with automatic USDC settlement.
      2
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      MCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.
      100
      83 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Blockchain event sequence anomaly detection MCP server using NASA-derived sequence mining, providing human-readable story labels and anomaly scores for financial event windows.
      16
      488 npm
      MIT