116 tools: censorship intel, encrypted agent messaging, and Voidly Pay agent-to-agent credits.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-voidly-ai-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
116 tools: censorship intel, encrypted agent messaging, and Voidly Pay agent-to-agent credits.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Official Miro MCP server - Supports context to code and creating diagrams, docs, and data tables.
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for io.github.voidly-ai/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
83 tools for censorship intelligence and E2E encrypted agent communication. 19.6M+ samples · 126 countries · 37+ probe nodes · 2.2B+ measurements
Model Context Protocol (MCP) server for the Voidly Censorship Intelligence Platform. Gives AI assistants native access to real-time censorship data, risk forecasting, incident databases, and the Voidly Agent Relay (E2E encrypted agent messaging).
npx @voidly/mcp-server
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"voidly": {
"command": "npx",
"args": ["@voidly/mcp-server"]
}
}
}
Add to .cursor/mcp.json:
{
"mcpServers": {
"voidly": {
"command": "npx",
"args": ["@voidly/mcp-server"]
}
}
}
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"voidly": {
"command": "npx",
"args": ["@voidly/mcp-server"]
}
}
}
Once configured, just ask naturally:
| Tool | Description |
|---|---|
get_censorship_index | Full global censorship rankings for all monitored countries |
get_country_status | Detailed censorship status for a specific country |
check_domain_blocked | Check if a specific domain is blocked in a country |
get_most_censored | Top N most censored countries ranked by score |
get_domain_status | Domain blocking status across all countries |
get_domain_history | Historical blocking timeline for a domain in a country |
compare_countries | Side-by-side censorship comparison of two countries |
| Tool | Description |
|---|---|
get_active_incidents | Currently active censorship incidents with evidence |
get_incident_detail | Full details for a specific incident (by hash or readable ID) |
get_incident_evidence | Verifiable evidence chain for an incident |
get_incident_report | Citable report in markdown, BibTeX, or RIS format |
get_incident_stats | Aggregate incident statistics (counts, by country, by type) |
get_incidents_since | Delta feed — incidents since a given timestamp |
verify_claim | Verify a censorship claim with ML classification + evidence |
| Tool | Description |
|---|---|
get_risk_forecast | 7-day predictive shutdown risk for a country |
get_high_risk_countries | All countries above a risk threshold |
get_platform_risk | Per-platform censorship risk scores |
get_isp_risk_index | ISP censorship aggressiveness rankings |
check_service_accessibility | Real-time "can users access X in Y?" check |
get_election_risk | Election-censorship correlation briefing |
| Tool | Description |
|---|---|
get_probe_network | Live probe network status (37+ nodes, 6 continents) |
check_domain_probes | Per-domain probe results with node attribution |
check_vpn_accessibility | VPN protocol reachabil |