Gemral Edge
Point-in-time U.S. public records: federal contracts, congressional and insider trades, lobbying.
What can you do with Gemral Edge?
get_company_exposureget_event_expected_impactget_contract_beneficiariesget_policy_affected_companiesget_signal_historical_outcomesscreen_convergenceexplain_scoreget_top_signals
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http gemral-edge 'https://mcp.gemral.com/mcp'
{
"mcpServers": {
"gemral-edge": {
"type": "http",
"url": "https://mcp.gemral.com/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
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 <key>. - 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 GEMRAL_EDGE_API_KEY=YOUR_GEMRAL_EDGE_KEY gemral-edge-mcp
Without GEMRAL_EDGE_API_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:
get_company_exposureget_event_expected_impactget_contract_beneficiariesget_policy_affected_companiesget_signal_historical_outcomesscreen_convergenceexplain_scoreget_top_signalsget_leaderboardget_track_recordget_forecastget_ticker_intelligenceget_actor_profileget_crypto_funding_extremesget_onchain_whale_flowsaudit_cluster_insider_buyingget_committee_conflict_mapscan_crypto_patternsget_physical_footprintsearch_management_promisesget_open_promisesget_overdue_promisesget_management_credibilitycompare_management_teamsget_claim_historyverify_claimget_language_driftget_guidance_accuracysearch_accountability_peopleget_upcoming_catalystsget_breakout_watchget_precursor_signalsget_event_impact_previewget_policy_intelligence_feedget_beneficiary_tickersget_event_countdownverify_event_status
Documentation
- Data due-diligence questionnaire (methods, coverage, known limits): https://www.gemral.com/edge-ddq.md
- API quickstart: https://www.gemral.com/edge-api-quickstart.md
- Data license: https://www.gemral.com/edge-api-license.md
Fields derived from map data and satellite imagery carry these attributions: "© OpenStreetMap contributors" and "Contains modified Copernicus Sentinel data 2023-2026".
Output is informational and is not investment advice.
License
The files in this repository (README and metadata) are MIT licensed. Data returned by the server is covered by the Gemral Edge data license linked above.
Frequently asked questions
What is Gemral Edge?
Point-in-time U.S. public records: federal contracts, congressional and insider trades, lobbying.
How do I install Gemral Edge?
It runs as a remote server. In Claude Code: claude mcp add --transport http gemral-edge 'https://mcp.gemral.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Gemral Edge need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Gemral Edge open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Gemral Edge?
It is published by gemral-edge. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.