Skip to content
GridRouterhome

Search

Search providers, capabilities and pages

An MCP server that gives agents every GTM data tool

Point a compatible MCP client at one URL and your agent can search the catalog, get a quote and call any capability, inside the budget you set.

See it working

Agent calls in the call logSimulationOpen in the demo

Real catalog providers. Calls, results, costs and performance are simulated. No provider is contacted.

Calls over time282 calls, 90-minute buckets
  • Hit208
  • Miss68
  • Failed6
Calls per bucket by outcome
Bucket (UTC)HitMissFailed
Sep 27, 15:56 UTC521
Sep 27, 17:26 UTC1230
Sep 27, 18:56 UTC510
Sep 27, 20:26 UTC420
Sep 27, 21:56 UTC440
Sep 27, 23:26 UTC210
Sep 28, 00:56 UTC100
Sep 28, 02:26 UTC500
Sep 28, 03:56 UTC400
Sep 28, 05:26 UTC200
Sep 28, 06:56 UTC401
Sep 28, 08:26 UTC400
Sep 28, 09:56 UTC400
Sep 28, 11:26 UTC410
Sep 28, 12:56 UTC510
Sep 28, 14:26 UTC1130
Sep 28, 15:56 UTC660
Sep 28, 17:26 UTC520
Sep 28, 18:56 UTC310
Sep 28, 20:26 UTC600
Sep 28, 21:56 UTC810
Sep 28, 23:26 UTC010
Sep 29, 00:56 UTC110
Sep 29, 02:26 UTC100
Sep 29, 03:56 UTC010
Sep 29, 05:26 UTC120
Sep 29, 06:56 UTC220
Sep 29, 08:26 UTC021
Sep 29, 09:56 UTC400
Sep 29, 11:26 UTC600
Sep 29, 12:56 UTC910
Sep 29, 14:26 UTC620
Sep 29, 15:56 UTC920
Sep 29, 17:26 UTC721
Sep 29, 18:56 UTC820
Sep 29, 20:26 UTC421
Sep 29, 21:56 UTC830
Sep 29, 23:26 UTC210
Sep 30, 00:56 UTC510
Sep 30, 02:26 UTC210
Sep 30, 03:56 UTC010
Sep 30, 05:26 UTC110
Sep 30, 06:56 UTC500
Sep 30, 08:26 UTC400
Sep 30, 09:56 UTC300
Sep 30, 11:26 UTC530
Sep 30, 12:56 UTC541
Sep 30, 14:26 UTC650
ProviderCallsError ratep95Spend
LeadMagic1581.3%2.7 s$0.424
Hunter771.3%1.7 s$0.277
Prospeo417.3%1.8 s$0.024
DetectZeStack60.0%3.2 s$0
MCP tool calls show up in the same log, charts and spend as API calls.

What you get

  • One server URL

    https://mcp.gridrouter.io/mcp over MCP 2026-07-28 stateless Streamable HTTP, with OAuth or an API key.

  • Tools for the whole loop

    Search the catalog, quote a call, run a capability or a waterfall, and read a run's result.

  • Scoped keys and spend caps for agents

    Give each agent its own key with only the scopes it needs and a daily, weekly or monthly limit.

  • The same pipeline as the API

    MCP calls route, fall back, hit the private cache and land in the call log like any other call.

  • Your waterfalls become tools

    A published waterfall shows up as its own MCP tool, versioned like the endpoint.

How it works

  1. Create an API key for the agent with the call and catalog:read scopes and a spend limit.

  2. Add the GridRouter server to your MCP client's config.

  3. Ask for data in plain language; the agent picks the tool, and every call is logged.

mcp.json
{
  "mcpServers": {
    "gridrouter": {
      "url": "https://mcp.gridrouter.io/mcp",
      "headers": { "Authorization": "Bearer ${GRID_API_KEY}" }
    }
  }
}

Questions

Which MCP clients work?

Clients that implement MCP 2026-07-28 stateless Streamable HTTP. Older clients that require the initialize handshake cannot connect. OAuth is available in clients that support MCP authorization.

How do I stop an agent from overspending?

Give it its own API key with a spend limit that resets daily, weekly or monthly. Calls past the limit are refused before any provider is called.

Are MCP calls billed differently?

No. They're the same calls as the API, with the same prices, cache and logs.

Try it on your own data

Free while we launch. Bring your vendor keys; no card needed.