Gemral Edge MCP server

Gemral Edge MCP server

Remote MCP server for Gemral Edge: point-in-time U.S. public-record data (federal contracts, congressional and insider trades, lobbying, regulatory publications) and AI-infrastructure physical data, for AI assistants.

The server is hosted. This repository holds its public metadata (server.json for the official MCP Registry), connection instructions, and a small zero-dependency stdio proxy (proxy.mjs) for clients that only run local servers. The proxy forwards every request to the hosted server; it contains no data and no server code.

• Every record is tied to the company and ticker that were valid on the day it became public.
• Publication lags are applied, so the data can be joined without look-ahead.
• Each record type ships only after a sampled accuracy check against the original public documents (95% minimum).
• Delisted and acquired companies stay in the history under the ticker they had at the time.
• Data comes only from public sources and contains no material non-public information.
• Delivered as Parquet files, a REST API and an MCP server for AI assistants.
• For AI-infrastructure companies we also track data-center sites, air permits, permitted backup-generator MW, substations, grid demand, equipment imports, capex and satellite measurements.

Known limits worth reading before you rely on the data:

• Roughly half of events on delisted tickers have historical prices; results on delisted names can be biased upward by survivorship.
• Permitted backup-generator MW is an upper bound on on-site backup capacity, not IT load; we do not convert it.
• Imports are industry context by product code and origin country, not company-level shipments.

Connect

• Server URL (streamable HTTP): https://mcp.gemral.com/mcp
• Auth: OAuth (clients that support MCP authorization discover it automatically) or an API key sent as Authorization: Bearer .
• Keys and plans: https://www.gemral.com/edge/pricing · questions: support@gemral.com

Claude (custom connector) or ChatGPT (connector): add the server URL above and sign in when prompted.

Cursor, Windsurf and other clients that take a JSON config:

{
  "mcpServers": {
    "gemral-edge": {
      "url": "https://mcp.gemral.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_GEMRAL_EDGE_KEY" }
    }
  }
}

Local stdio proxy (npx or Docker)

For clients that only launch local commands. Requires Node 18+.

{
  "mcpServers": {
    "gemral-edge": {
      "command": "npx",
      "args": ["-y", "github:gemral-edge/gemral-edge-mcp"],
      "env": { "GEMRAL_EDGE_API_KEY": "YOUR_GEMRAL_EDGE_KEY" }
    }
  }
}

Docker: docker build -t gemral-edge-mcp . && docker run -i --rm -e GEMRALEDGEAPIKEY=YOURGEMRALEDGEKEY gemral-edge-mcp

Without GEMRALEDGEAPI_KEY the proxy still answers tools/list from the bundled tools.json (generated from the hosted server's tools/list), and tool calls return a message explaining how to get access. No key? Connect your client to the server URL above instead and sign in with OAuth (free tier).

Tools

37 tools, as returned by the server's tools/list:

Shortened. The full README is on GitHub.