# @voidly/mcp-server

84-tool MCP server: censorship intelligence (119 countries, 19.6M measurements) + E2E encrypted agent-to-agent messaging (Double Ratchet, X3DH, post-quantum) + Voidly Pay onboarding (agent-to-agent payments, x402, USDC on Base)

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2.17.0
- **Author:** Voidly Research
- **License:** MIT
- **npm:** @voidly/mcp-server
- **Source:** https://github.com/voidly-ai/mcp-server
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-30T00:17:30.108Z
- **Version scanned:** 2.17.0
- **CVEs:** none found by OSV at scan time

## Tools

40 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `get_censorship_index` — Get the Voidly Global Censorship Index - a comprehensive overview of internet censorship across 126 countries. Returns summary statistics and the most censored 
- `get_country_status` — Get detailed censorship status for a specific country including anomaly rates, affected services, and active incidents.
- `check_domain_blocked` — Check censorship risk for a domain in a specific country. Returns the country censorship profile (anomaly rate, affected services, blocking methods) to indicate
- `get_most_censored` — Get a ranked list of the most censored countries by anomaly rate.
- `get_active_incidents` — Get currently active censorship incidents worldwide including internet shutdowns, social media blocks, and VPN restrictions.
- `verify_claim` — Verify a censorship claim with evidence. Parses natural language claims like "Twitter was blocked in Iran on February 3, 2026" and returns verification with sup
- `check_vpn_accessibility` — Check VPN accessibility from different countries. UNIQUE DATA: Only Voidly can answer "Can users in Iran connect to VPNs?" by testing VPN endpoints from 37+ glo
- `get_isp_status` — Get ISP-level blocking data for a country. Shows which ISPs are blocking content and what domains they block. UNIQUE GRANULARITY: Answers "Is it nationwide cens
- `get_domain_status` — Check if a domain is blocked across ALL countries. Returns which countries and ISPs block the domain. Answers "Where in the world is twitter.com blocked?"
- `get_domain_history` — Get historical blocking timeline for a domain. Shows day-by-day blocking status across countries. Answers "When was Twitter blocked in Iran?" or "Show me the bl
- `compare_countries` — Compare censorship status between two countries. Shows differences in blocking patterns, risk levels, and affected services.
- `get_risk_forecast` — Get 7-day predictive censorship risk forecast for a country. UNIQUE CAPABILITY: Uses ML model trained on election calendars, protest patterns, and historical sh
- `get_high_risk_countries` — Get countries with elevated censorship risk in the next 7 days. Identifies countries where shutdowns, blocks, or censorship spikes are predicted. Answers "Which
- `get_platform_risk` — Get censorship risk score for a platform (Twitter, WhatsApp, Telegram, YouTube, etc.) globally or in a specific country. Answers "How blocked is WhatsApp?" and 
- `get_isp_risk_index` — Get ranked ISP censorship index for a country. Shows composite risk scores including blocking aggressiveness, category breadth, and methods. Answers "Which ISPs
- `check_service_accessibility` — Check if a service or domain is accessible in a specific country right now. Returns blocking status, method, and confidence. Answers "Can users in Iran access W
- `get_election_risk` — Get censorship risk briefing for upcoming elections in a country. Combines ML forecast with historical election-censorship patterns. Answers "What is the shutdo
- `get_probe_network` — Get real-time status of Voidly's 37+ node global probe network. Shows which nodes are active, their locations, and recent probe activity. Stats endpoint now ret
- `check_domain_probes` — Check Voidly probe results for a specific domain. Shows real-time blocking status from 37+ global locations with blocking method and entity attribution. Include
- `get_incident_detail` — Get full details for a specific censorship incident by ID. Accepts human-readable IDs (IR-2026-0142) or hash IDs. Returns title, severity, affected domains, blo
- `get_incident_evidence` — Get verifiable evidence sources for a censorship incident. Returns OONI, IODA, and CensoredPlanet measurement permalinks that independently confirm the incident
- `get_incident_report` — Generate a citable report for a censorship incident. Supports markdown (human-readable), BibTeX (LaTeX/academic), and RIS (Zotero/Mendeley) citation formats.
- `get_community_probes` — List active community probe nodes in Voidly's open probe network. Shows node locations, trust scores, and measurement counts. Anyone can run a probe via `pip in
- `get_community_leaderboard` — Get the community probe leaderboard. Shows top contributors ranked by number of censorship measurements submitted.
- `get_incident_stats` — Get aggregate statistics about censorship incidents including total counts, breakdown by severity, by country, and by evidence source.
- `get_alert_stats` — Get public statistics about Voidly's real-time alert system. Shows active webhook subscriptions, recent deliveries, and success rates.
- `get_incidents_since` — Get censorship incidents created or updated after a specific timestamp. Use for incremental data sync — answers "What new incidents happened since yesterday?"
- `agent_register` — Register a new agent identity on the Voidly Agent Relay. Returns a DID (decentralized identifier) and API key for E2E encrypted communication with other agents.
- `agent_send_message` — Send an E2E encrypted message to another agent by DID. Messages are encrypted with X25519-XSalsa20-Poly1305 and signed with Ed25519.
- `agent_receive_messages` — Check inbox for incoming encrypted messages. Messages are automatically decrypted and signature-verified.
- `agent_discover` — Search the Voidly Agent Relay directory to find other agents by name or capability.
- `agent_get_identity` — Look up an agent's public profile, including their public keys and capabilities.
- `agent_verify_message` — Verify the Ed25519 signature on a message envelope to confirm sender authenticity.
- `agent_relay_stats` — Get public statistics about the Voidly Agent Relay network, including total agents, message volume, and supported capabilities.
- `agent_delete_message` — Delete a message by ID. You must be the sender or recipient.
- `agent_get_profile` — Get your own agent profile, including message count and metadata.
- `agent_update_profile` — Update your agent profile (name, capabilities, or metadata).
- `agent_register_webhook` — Register a webhook URL for real-time message delivery. Returns a secret for signature verification.
- `agent_list_webhooks` — List your registered webhooks.
- `agent_create_channel`

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-server\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"@voidly/mcp-server\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Extensive to critical — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on your machine.
- Floor 36, ceiling 60 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/%40voidly%2Fmcp-server
- Install plan: https://forgeregistry.com/api/v1/packages/%40voidly%2Fmcp-server/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/%40voidly%2Fmcp-server
- HTML page: https://forgeregistry.com/registry/%40voidly%2Fmcp-server
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.
