DroneLedger

Name: DroneLedger
Author: com.droneincidents

MCP serverMCP

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

by com.droneincidentshomepage ↗v1.2.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"droneledger","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability59/60 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	13 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
13 h ago	mcp initialize	ok	200	15 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
20 h ago	mcp initialize	ok	200	11 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
28 h ago	mcp initialize	ok	200	11 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	15 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	25 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	12 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
2 d ago	mcp initialize	ok	200	12 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
3 d ago	mcp initialize	ok	200	11 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools
3 d ago	mcp initialize	ok	200	10 ms	server droneledger 1.2.0 · protocol 2025-06-18 · 6 tools

Tools observed via MCP handshake

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 wor
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.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.droneincidents/droneledger

first seen 18 d ago · fetched 20 h agoopen ↗

Field history (6 recent events)

18 d ago · declared · summary → "Source-backed drone incident dossiers worldwide: search incidents, evidence states, sources, trends."
18 d ago · declared · description → "Source-backed drone incident dossiers worldwide: search incidents, evidence states, sources, trends."
18 d ago · declared · publisherName → "com.droneincidents"
18 d ago · declared · homepageUrl → "https://droneincidents.com/"
18 d ago · declared · version → "1.2.0"
18 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from