The dashboard’s data, for your agents

The Data MCP exposes the dashboard’s data to an agent: district profiles and monthly series, country league tables and overviews, recent alerts and anomaly episodes, listed companies’ footprints and exposure, and what the measurement covers. Each tool returns rows with the data vintage, the source files and the plan gates applied.

Access is by key. Keys are issued by hand during the beta and carry a plan, Free, Pro or Enterprise, with the same gates as the dashboard: district-level detail and exports on Pro, full history, episode detail and company compare on Enterprise. A Free key sees what a Free account sees, including the worked examples in full.

The server is in beta. Tool names, fields and limits may change; every result names its vintage, and the measurement behind it is the dashboard’s committed snapshot, not live monitoring.

claude mcp add --transport http kaspr-data https://mcp.kasprdata.com/data/mcp --header "Authorization: Bearer kmcp_…"

{
  "mcpServers": {
    "kaspr-data": {
      "url": "https://mcp.kasprdata.com/data/mcp",
      "headers": { "Authorization": "Bearer kmcp_…" }
    }
  }
}

{
  "mcpServers": {
    "kaspr-data": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.kasprdata.com/data/mcp", "--header", "Authorization: Bearer kmcp_…"]
    }
  }
}

A 401 means the key is missing or revoked; a 403 names the plan the tool needs; a result always carries meta.data_vintage.

By continuing, you agree to our Terms & Conditions and Privacy Policy.

Every call carries Authorization: Bearer <key>. The server checks the key, reads its plan, and forwards the question to the dashboard with that plan; the dashboard applies the same gates it applies to a signed-in account.

Rows are capped per plan: 50 on Free, 500 on Pro, 5,000 on Enterprise. A capped result says so in meta.truncated with the total available.

One entry per tool, in the server’s order. Parameters are read from the server’s own schemas; unknown parameters are refused with invalid_request. What the measurement covers (regions and districts per country) is a resource, kaspr-data://coverage, not a tool. A gate fires only under the condition named; outside it the tool answers on every plan.

Keys are rate-limited per minute and per day, and a key that touches many distinct places in an hour is slowed; the server tells you which limit you hit.

Rows per result are capped by plan (above). Results are a snapshot of the dashboard’s committed data at the vintage each result names; the Enterprise weekly drop refreshes it.

• invalid_request — A parameter is missing, of the wrong type, or unknown.
• unauthorized — No key, or a revoked one.
• plan_required — The tool or the detail asked for needs a higher plan; the message names it.
• not_found — The place, episode or company id does not exist.
• data_unavailable — The dataset behind the tool is not on the server right now.
• rate_limited — Too many calls in a minute or a day for the key, or too many distinct places in an hour; the message says which, and when to try again.
• area_limit_reached — The key has touched its daily allowance of distinct places.
• licence_suspended — The key is suspended; write to info@kasprdata.com.
• backend_unavailable — The server could not reach the dashboard; try again shortly.

Every call is recorded with the key id, the tool, its parameters, the row count, the status and a request id, and kept for thirteen months, so usage can be metered, a leaked extract traced to its key, and abuse investigated. Results carry a licence line; see the terms.

The strict rules, in brief. The binding text is on the terms page, which installing or calling the server accepts.

• — Internal use only: no redistribution of the data or results, no resale, no publication of row-level results.
• — No storage beyond 30 days, and no use of the data to train models.
• — No reliance for decisions that could harm people or property; the measurement is a snapshot, not monitoring.
• — No warranty of accuracy, availability or fitness; liability is limited as the terms set out.
• — Keys are personal to the licensee and may be suspended for breach.

Read the terms

The timing and scheduling servers, which plan calls and posts on KASPR’s typical week, are documented on KASPR Schedule’s site.

Timing and scheduling MCP docs ↗

2026-10-06 — switched on at mcp.kasprdata.com/data/mcp; 13 tools (regional core, alerts and anomaly episodes, company footprint) and two resources (coverage, terms), plan-gated as on pulse.kasprdata.com. Disaster-event tools withheld pending licence review.