Home / MCP registry index / io.github.beepboop2025/narcoscope
NarcoScope — illicit-economy evidence atlas
io.github.beepboop2025/narcoscope in the official MCP registry.
Endpoint https://www.narcoscope.com/mcp. Source: github.com/beepboop2025/narcoscope.
The registry describes it as: Read bounded illicit-economy evidence with provenance, privacy, availability, and federation intact.
We read its 14 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
research_network list_capabilities get_overview get_atlas get_entities get_federation get_newsroom get_story get_palimpsest_bridge get_palimpsest_corridors get_palimpsest_bri_context get_connected_research get_market_catalog query_market_observations
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-beepboop2025-narcoscope)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.