Databases
dprk-reports.org
An MCP server for querying the DPRK Reports database, enabling entity search, detailed entity lookups, relationship discovery, path finding, and database statistics.
ENDPOINT 1
https://dprk-reports.org/mcp
MCP server metadata
- Name
- dprk-reports
- Version
- 1.0.0
Known tools 5
search_entitiesSearch the DPRK Reports database for persons, companies, organizations, vessels, and events.
Inferred read-onlyget_entityGet full details of a specific entity by its ID, including all properties and sanctions status.
Inferred read-onlyfind_pathFind the shortest connection path between two entities in the DPRK Reports network.
Inferred read-onlyget_statsGet high-level statistics about the DPRK Reports database: total entities, edges, sanctioned entities, and breakdown by entity type.
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.dprk-reports]
url = "https://dprk-reports.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dprk-reports": {
"type": "http",
"url": "https://dprk-reports.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dprk-reports
Remote MCP URL: https://dprk-reports.org/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": {
"dprk-reports": {
"url": "https://dprk-reports.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dprk-reports": {
"type": "http",
"url": "https://dprk-reports.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dprk-reports",
"transport": "streamable-http",
"url": "https://dprk-reports.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.