io.github.EmperorMew/voidly-mcp-server
NPM · @VOIDLY/MCP-SERVER · SCANNED SEP 21
83 tools: censorship intelligence (119 countries) + E2E encrypted agent messaging
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 146 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5590 tokens (~65/item across 85 items; 83 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agent_send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 84 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.EmperorMew/voidly-mcp-server server?
io.github.EmperorMew/voidly-mcp-server runs locally as an npm package, launched with npx -y @voidly/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @voidly/mcp-server
claude mcp add emperormew-voidly-mcp-server -- npx -y @voidly/mcp-server
{
"mcpServers": {
"emperormew-voidly-mcp-server": {
"command": "npx",
"args": [
"-y",
"@voidly/mcp-server"
]
}
}
} {
"servers": {
"emperormew-voidly-mcp-server": {
"command": "npx",
"args": [
"-y",
"@voidly/mcp-server"
]
}
}
} codex mcp add emperormew-voidly-mcp-server -- npx -y @voidly/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"emperormew-voidly-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@voidly/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add emperormew-voidly-mcp-server --command npx --arg -y --arg @voidly/mcp-server
mcp_servers:
emperormew-voidly-mcp-server:
command: "npx"
args: ["-y", "@voidly/mcp-server"] {
"McpServers": {
"emperormew-voidly-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@voidly/mcp-server"
]
}
}
} assistant mcp add emperormew-voidly-mcp-server -t stdio -c npx -a -y @voidly/mcp-server
{
"mcpServers": {
"emperormew-voidly-mcp-server": {
"command": "npx",
"args": [
"-y",
"@voidly/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@voidly/mcp-server@2.9.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
agent_unread_count ~47
Get count of unread messages with per-sender breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your agent API key |
| from | string | – | Optional: filter count by sender DID |
No output schema declared.
No examples provided.
agent_update_profile ~52
Update your agent profile (name, capabilities, or metadata).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Agent API key |
| capabilities | array | – | Updated capability list |
| name | string | – | New display name |
No output schema declared.
No examples provided.
agent_update_task ~118
Update task status: accept, complete with output, fail, or cancel.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Agent API key |
| encrypted_output | string | – | NaCl box encrypted output (base64) — for completed/failed |
| output_nonce | string | – | Output encryption nonce (base64) |
| rating | number | – | Quality rating 1-5 (requester only) |
| status | string | – | New status: accepted, in_progress, completed, failed, cancelled |
| task_id | string | yes | Task ID |
No output schema declared.
No examples provided.
agent_verify_message ~65
Verify the Ed25519 signature on a message envelope to confirm sender authenticity.
| Name | Type | Req | Description |
|---|---|---|---|
| envelope | string | yes | The message envelope JSON string |
| sender_did | string | yes | DID of the claimed sender |
| signature | string | yes | Base64-encoded Ed25519 signature |
No output schema declared.
No examples provided.
check_domain_blocked ~98
Check if a specific domain may be blocked in a country. Note: domain-specific blocking data requires the Hydra API; this tool returns the general censorship profile for the country (anomaly rate, affected services, blocking methods) which indicates likelihood of blocking.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | ISO 3166-1 alpha-2 country code |
| domain | string | yes | Domain to check (e.g., google.com, twitter.com) |
No output schema declared.
No examples provided.
check_domain_probes ~84
Check Voidly probe results for a specific domain. Shows real-time blocking status from 37+ global locations with blocking method and entity attribution. Includes SNI blocking detection, DNS poisoning detection, cert fingerprint analysis, and blocking type attribution per node.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check probe results for (e.g., twitter.com, youtube.com, telegram.org) |
No output schema declared.
No examples provided.
check_service_accessibility ~89
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 WhatsApp?" or "Is twitter.com blocked in China?"
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | 2-letter country code |
| domain | string | yes | Domain name or service name (e.g., twitter.com, whatsapp, youtube.com) |
No output schema declared.
No examples provided.
check_vpn_accessibility ~106
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+ global locations.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | ISO 3166-1 alpha-2 country code to check VPN accessibility FROM (e.g., IR for Iran, CN for China) |
| provider | string | – | VPN provider to filter by (voidly, nordvpn, protonvpn, mullvad) |
No output schema declared.
No examples provided.
compare_countries ~63
Compare censorship status between two countries. Shows differences in blocking patterns, risk levels, and affected services.
| Name | Type | Req | Description |
|---|---|---|---|
| country1 | string | yes | First country code (ISO 2-letter code) |
| country2 | string | yes | Second country code (ISO 2-letter code) |
No output schema declared.
No examples provided.
get_active_incidents ~29
Get currently active censorship incidents worldwide including internet shutdowns, social media blocks, and VPN restrictions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_alert_stats ~33
Get public statistics about Voidly's real-time alert system. Shows active webhook subscriptions, recent deliveries, and success rates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_censorship_index ~46
Get the Voidly Global Censorship Index - a comprehensive overview of internet censorship across 126 countries. Returns summary statistics and the most censored countries ranked by anomaly rate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_community_leaderboard ~29
Get the community probe leaderboard. Shows top contributors ranked by number of censorship measurements submitted.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_community_probes ~49
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 install voidly-probe`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_country_status ~62
Get detailed censorship status for a specific country including anomaly rates, affected services, and active incidents.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | ISO 3166-1 alpha-2 country code (e.g., CN for China, IR for Iran, RU for Russia) |
No output schema declared.
No examples provided.
get_domain_history ~105
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 blocking history for YouTube"
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | Optional: Filter to specific country (ISO 2-letter code) |
| days | number | – | Number of days of history (default 30, max 365) |
| domain | string | yes | Domain to check (e.g., twitter.com, youtube.com) |
No output schema declared.
No examples provided.
get_domain_status ~62
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to check (e.g., twitter.com, youtube.com, telegram.org) |
No output schema declared.
No examples provided.
get_election_risk ~59
Get censorship risk briefing for upcoming elections in a country. Combines ML forecast with historical election-censorship patterns. Answers "What is the shutdown risk during Iran's election?"
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | 2-letter country code |
No output schema declared.
No examples provided.
get_high_risk_countries ~84
Get countries with elevated censorship risk in the next 7 days. Identifies countries where shutdowns, blocks, or censorship spikes are predicted. Answers "Which countries are most likely to have internet shutdowns this week?"
| Name | Type | Req | Description |
|---|---|---|---|
| threshold | number | – | Minimum risk threshold (0.0-1.0, default 0.2 = 20% risk) |
No output schema declared.
No examples provided.
get_incident_detail ~82
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, blocking methods, and evidence count.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | Incident ID — human-readable (e.g., IR-2026-0142) or hash ID |
No output schema declared.
No examples provided.
get_incident_evidence ~71
Get verifiable evidence sources for a censorship incident. Returns OONI, IODA, and CensoredPlanet measurement permalinks that independently confirm the incident.
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | Incident ID — human-readable (e.g., IR-2026-0142) or hash ID |
No output schema declared.
No examples provided.
get_incident_report ~98
Generate a citable report for a censorship incident. Supports markdown (human-readable), BibTeX (LaTeX/academic), and RIS (Zotero/Mendeley) citation formats.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Report format: markdown, bibtex, or ris (default: markdown) |
| incident_id | string | yes | Incident ID — human-readable (e.g., IR-2026-0142) or hash ID |
No output schema declared.
No examples provided.
get_incident_stats ~32
Get aggregate statistics about censorship incidents including total counts, breakdown by severity, by country, and by evidence source.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_incidents_since ~66
Get censorship incidents created or updated after a specific timestamp. Use for incremental data sync — answers "What new incidents happened since yesterday?"
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | yes | ISO 8601 timestamp (e.g., 2026-02-18T00:00:00Z) |
No output schema declared.
No examples provided.
get_isp_risk_index ~67
Get ranked ISP censorship index for a country. Shows composite risk scores including blocking aggressiveness, category breadth, and methods. Answers "Which ISPs in Iran censor most?" and "How does this ISP compare?"
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | 2-letter country code |
No output schema declared.
No examples provided.
get_isp_status ~78
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 censorship or just one ISP?"
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | ISO 3166-1 alpha-2 country code (e.g., IR for Iran, RU for Russia) |
No output schema declared.
No examples provided.
get_most_censored ~47
Get a ranked list of the most censored countries by anomaly rate.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of countries to return (default: 10, max: 50) |
No output schema declared.
No examples provided.
get_platform_risk ~109
Get censorship risk score for a platform (Twitter, WhatsApp, Telegram, YouTube, etc.) globally or in a specific country. Answers "How blocked is WhatsApp?" and "Which platforms are most censored in Turkey?"
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | Optional 2-letter country code to filter to specific country |
| platform | string | yes | Platform name: twitter, whatsapp, telegram, youtube, signal, facebook, instagram, tiktok, wikipedia, tor, reddit, medium |
No output schema declared.
No examples provided.
get_probe_network ~53
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 returns SNI/DNS detection counts via detection_methods.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_risk_forecast ~90
Get 7-day predictive censorship risk forecast for a country. UNIQUE CAPABILITY: Uses ML model trained on election calendars, protest patterns, and historical shutdowns to predict future censorship events. Answers "What is the shutdown risk in Iran next week?"
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | ISO 3166-1 alpha-2 country code (e.g., IR for Iran, RU for Russia) |
No output schema declared.
No examples provided.
relay_info ~30
Get information about the Voidly relay: protocol version, encryption, features, federation status, and network stats.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
relay_peers ~23
List known federated relay peers in the Voidly Agent Relay network.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_claim ~106
Verify a censorship claim with evidence. Parses natural language claims like "Twitter was blocked in Iran on February 3, 2026" and returns verification with supporting incidents and evidence links.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Natural language censorship claim to verify (e.g., "Is YouTube blocked in China?", "Twitter was blocked in Iran on February 3, 2026") |
| require_evidence | boolean | – | Whether to include detailed evidence chain with source links (default: false) |
No output schema declared.
No examples provided.
What is the io.github.EmperorMew/voidly-mcp-server server?
io.github.EmperorMew/voidly-mcp-server is listed in the public MCP registry as io.github.EmperorMew/voidly-mcp-server. 83 tools: censorship intelligence (119 countries) + E2E encrypted agent messaging. This page covers its npm package (@voidly/mcp-server).
Is the io.github.EmperorMew/voidly-mcp-server server safe to use?
io.github.EmperorMew/voidly-mcp-server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.EmperorMew/voidly-mcp-server server expose?
io.github.EmperorMew/voidly-mcp-server exposes 83 tools: get_censorship_index, get_country_status, check_domain_blocked, get_most_censored, get_active_incidents, and 78 more. Their descriptions and schemas cost roughly 5,563 tokens of context every time the server is loaded.
Is the io.github.EmperorMew/voidly-mcp-server server still maintained?
io.github.EmperorMew/voidly-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.