# DroneLedger (remote · droneincidents.com)

Source-backed drone incident dossiers worldwide: search incidents, evidence states, sources, trends.

- Trust score: 82/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `droneincidents.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-droneincidents-droneledger/droneincidents.md), [page](https://verifymcp.io/servers/com-droneincidents-droneledger/droneincidents)

## Channel facts

- Endpoint: `https://droneincidents.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 452 tokens (~75/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the DroneLedger MCP server?

DroneLedger is a hosted endpoint at https://droneincidents.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-droneincidents-droneledger 'https://droneincidents.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-droneincidents-droneledger": {
      "url": "https://droneincidents.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-droneincidents-droneledger": {
      "type": "http",
      "url": "https://droneincidents.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-droneincidents-droneledger]
url = "https://droneincidents.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-droneincidents-droneledger": {
      "type": "remote",
      "url": "https://droneincidents.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-droneincidents-droneledger --url 'https://droneincidents.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-droneincidents-droneledger:
    url: "https://droneincidents.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-droneincidents-droneledger": {
      "Transport": "http",
      "Url": "https://droneincidents.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-droneincidents-droneledger -t streamable-http -u 'https://droneincidents.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-12 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-11-10 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 79, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `search_incidents` (~160 tokens)

Search drone incident dossiers

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

Input parameters:

- `category` (string)
- `corroboration` (string): Evidence tier: single = one source, unverified; multiple = two or more publishers; curated = checked by an editor.
- `country` (string): ISO 3166-1 alpha-2 code, e.g. UA, SA, RU.
- `drone_status` (string)
- `impact_status` (string)
- `limit` (integer)
- `query` (string): Free text, matched against title, place, country and summary.
- `since` (string): Incident date from (YYYY-MM-DD).
- `until` (string): Incident date until (YYYY-MM-DD).

### `get_incident` (~39 tokens)

Get one dossier

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

Input parameters:

- `id` (string, required)

### `get_trends` (~52 tokens)

Counts per period

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` (~37 tokens)

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` (~31 tokens)

Get one drone type

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

Input parameters:

- `id` (string, required)

### `get_methodology` (~22 tokens)

How DroneLedger assesses evidence

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-droneincidents-droneledger/droneincidents#diagnostics

## Score history

- 2026-11-21: 82
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 82
- 2026-11-15: 82
- 2026-11-14: 82
- 2026-11-13: 82
- 2026-11-12: 82
- 2026-11-11: 81
- 2026-11-10: 81
- 2026-11-09: 80
- 2026-11-08: 80
- 2026-11-07: 79
- 2026-11-06: 79
- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72

## Common questions

### What is the DroneLedger MCP server?

DroneLedger is an MCP server listed in the public MCP registry as com.droneincidents/droneledger. Source-backed drone incident dossiers worldwide: search incidents, evidence states, sources, trends. This page covers its hosted endpoint (https://droneincidents.com/mcp).

### Is the DroneLedger MCP server safe to use?

DroneLedger scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the DroneLedger MCP server expose?

DroneLedger exposes 6 tools: search_incidents, get_incident, get_trends, list_drone_types, get_drone_type, get_methodology. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.

### Does the DroneLedger MCP server require authentication?

No. We connected to DroneLedger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the DroneLedger MCP server still maintained?

DroneLedger is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the DroneLedger MCP server?

VerifyMCP ran 13 checks on DroneLedger, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://droneincidents.com/mcp
- Website: https://droneincidents.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-droneincidents-droneledger/droneincidents.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-droneincidents-droneledger/droneincidents/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-droneincidents-droneledger/droneincidents.json
- HTML version of this page: https://verifymcp.io/servers/com-droneincidents-droneledger/droneincidents
