Gemral Edge
Point-in-time U.S. public records: federal contracts, congressional and insider trades, lobbying.
Que pouvez-vous faire avec Gemral Edge ?
get_company_exposureget_event_expected_impactget_contract_beneficiariesget_policy_affected_companiesget_signal_historical_outcomesscreen_convergenceexplain_scoreget_top_signals
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
claude mcp add --transport http gemral-edge 'https://mcp.gemral.com/mcp'
{
"mcpServers": {
"gemral-edge": {
"type": "http",
"url": "https://mcp.gemral.com/mcp"
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent 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.
Questions fréquentes
Qu'est-ce que Gemral Edge ?
Point-in-time U.S. public records: federal contracts, congressional and insider trades, lobbying.
Comment installer Gemral Edge ?
Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http gemral-edge 'https://mcp.gemral.com/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Gemral Edge ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
Gemral Edge est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient Gemral Edge ?
Il est publié par gemral-edge. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.