Data Collection
eykon.ai
Queries geospatial intelligence datasets for vessel, aircraft, conflict, refinery, and mineral-deposit information.
ENDPOINT 1
https://eykon.ai/api/mcp
MCP server metadata
- Name
- eykon
- Version
- 1.0.0
PUBLIC CATALOGUE. This is every tool eYKON exposes, listed without a key so you can see what is here before subscribing. Calling one requires an API key from https://eykon.ai/settings and a paid plan; the tools available to a given key depend on its tier. query_calibration returns eYKON's own measured forecast skill, so an agent can check the track record before trusting any other answer.
Known tools 24
query_conflictsQuery armed-conflict events (GDELT-backed, with ACLED fallback when licensed) by region / date / event type / actor.
Inferred read-onlyquery_refineriesQuery oil refineries from OpenStreetMap (canonical refinery tags only — petroleum_refinery, oil_refinery, refinery).
Inferred read-onlyquery_minesQuery mineral deposits from the USGS Mineral Resources Data System (MRDS — public-domain US Government, ~304k records globally, archival snapshot frozen at 2011).
Inferred read-onlyquery_power_plantsQuery unit-level power plants from the Global Energy Monitor — Global Integrated Power Tracker (GIPT).
Inferred read-onlyquery_pipelinesQuery gas pipelines (GEM GGIT), oil/NGL pipelines (GEM GOIT), and LNG terminals (GEM GGIT) in one call.
Inferred read-onlyquery_portsQuery commercial seaports from the NGA World Port Index (~3,800 ports worldwide).
Inferred read-onlyquery_weatherQuery current weather conditions for a specific location (Open-Meteo).
Inferred read-onlyquery_thermal_anomaliesQuery NASA FIRMS satellite thermal anomalies (VIIRS 375m + MODIS 1km, near-real-time, ~3h latency).
Inferred read-onlyquery_nightlightsQuery NASA Black Marble night-lights (VIIRS VNP46A2, ~500 m): moonlight/atmosphere-corrected nighttime radiance sampled nightly at every FIRMS-watched facility, plus significance events judged against each facility's OWN clear-night baseline.
Inferred read-onlyquery_agent_reportsRetrieve recent intelligence reports generated by eYKON Sub-Agents.
Inferred read-onlyquery_convergencesRecent convergence_events (anomaly-of-anomalies) with synthesis and contributing anomaly IDs.
Inferred read-onlyquery_shadow_fleet_leadsRanked shadow-fleet vessel leads, scored from silence relative to the OWN observed reporting cadence of each vessel (14-day baseline), vanished-under-way, and flag-of-convenience.
Inferred read-onlyquery_dark_contact_eventsDark-contact EVENTS from the Shadow Fleet board — resolvable observations with a lifecycle, not a leads snapshot.
Inferred read-onlyquery_calibrationeYKON's own forecast record: Brier and log-loss per TRACK over a window.
Inferred read-onlyquery_precursor_matchesNearest precursor_library entries for the given theatre, by cosine similarity.
Inferred read-onlyrun_chokepoint_scenarioRun a chokepoint closure scenario (same model as the Chokepoint Simulator).
Inferred read-onlyquery_regime_shiftsActive regime shifts (30d-vs-60d test) with p-values and effect sizes.
Inferred read-onlyquery_entitiesSearch the entities registry (vessels, operators, owners, flags, ports, refineries, mines).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.eykon]
url = "https://eykon.ai/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"eykon": {
"type": "http",
"url": "https://eykon.ai/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: eykon
Remote MCP URL: https://eykon.ai/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"eykon": {
"url": "https://eykon.ai/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"eykon": {
"type": "http",
"url": "https://eykon.ai/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "eykon",
"transport": "streamable-http",
"url": "https://eykon.ai/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for eykon.ai was fetched 2026-09-12T09:07:35.150Z.
eykon.ai is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.