Skip to content
DroneLedger logo

DroneLedger MCP server

Which MCP servers are DroneLedger's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to DroneLedger

Whose server it is
  • Registry namecom.droneincidents/droneledgerverified in the MCP registry

The registry name sits under droneincidents.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools6
  • Server calls itselfdroneledger
  • Server version1.2.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 162 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 3 of 6 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer468 ms
  • Space in an agent's context≈ 671 tokensthe definitions of all its tools (6), which an agent carries on every turn
  • Tool definitionsA · 92 of 100
  • Typed results0 of 6 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 3 of 6

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers6 tools · read 2026-10-27
  • search_incidents

    Search published dossiers. Filters are combined. Returns short summaries with URL and citation.

  • get_incident

    Full dossier: evidence states with supporting sources, drone types as named by sources, timeline, editorial history and citation.

  • get_trends

    Dossiers per period (today, 7, 30, 90, 365 days) by incident date, with the previous period of the same length. Reflects archive coverage, not all incidents worldwide.

  • list_drone_types

    Catalogue of drone types with category, origin, operators and published unit-cost estimates (third-party figures with source, year and price basis).

  • get_drone_type

    Manufacturer, production, operators, unit-cost estimates with sources, characteristics.

  • get_methodology

    Evidence states, attribution rules, source families and how to cite.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "droneledger": {
      "type": "http",
      "url": "https://droneincidents.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http droneincidents https://droneincidents.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://droneincidents.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.