Data · Local MCP server
Voidly
Censorship data, Sentinel forecasts and agent relay tools. Relay messages are readable by the relay.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.voidly-ai/mcp-server- Version
- 3.0.2
- Status
- Active
- Category
- data
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- voidly-ai (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/voidly-ai) · how
- Listed under
- Weather MCP servers
- Website
- voidly.ai
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @voidly/mcp-server | 3.0.2 | stdio |
How to connect Voidly
Voidly runs locally from a Node.js package published to the npm registry: @voidly/mcp-server version 3.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @voidly/mcp-server@3.0.2. It reads these environment variables: VOIDLY_MCP_RELAY_ALLOWED_RECIPIENTS, VOIDLY_MCP_RELAY_ALLOW_OPEN_WRITES, VOIDLY_MCP_RELAY_ALLOW_STATE_CHANGES, VOIDLY_MCP_RELAY_ALLOW_MEMORY_WRITES, VOIDLY_MCP_RELAY_HOME and VOIDLY_MCP_RELAY_DID; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@voidly/mcp-server@3.0.2"
],
"env": {
"VOIDLY_MCP_RELAY_ALLOWED_RECIPIENTS": "<value>",
"VOIDLY_MCP_RELAY_ALLOW_OPEN_WRITES": "<value>",
"VOIDLY_MCP_RELAY_ALLOW_STATE_CHANGES": "<value>",
"VOIDLY_MCP_RELAY_ALLOW_MEMORY_WRITES": "<value>",
"VOIDLY_MCP_RELAY_HOME": "<value>",
"VOIDLY_MCP_RELAY_DID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from voidly-ai (GitHub)
| Server | Runs |
|---|---|
| Voidpay MarketplacePublic discovery, scoped creator work, original-only recovery; checkout stays in owner's browser. | Local · stdio |
More data servers
| Server | Runs |
|---|---|
| Vitena DirectorySearch Vitena's public directory of bookable health and wellness professionals. | Remote · HTTPLive check: ✓ handshake |
| Vivory Verification Gateway98 MCP tools for verifiable AI: citations, law, KYB, peer review, forecast, media provenance. | Local · stdio |
| VK Ads MCPMCP server for VK Ads (VK Реклама) API: manage ad plans, ad groups, banners, and statistics. | Local · stdio |
| Voidfeed MCPKnowledge API for AI agents - content, agent directory, model benchmarks, semantic search. | Local · stdio |
| VorisVoris privacy-native web analytics for AI agents: query metrics & citations, scaffold tracking. | Local · stdio |
| Vortex IqRead-only access to your VortexIQ store data: audits, KPIs, alerts, Brand DNA, reports, Ask VIQ. | Remote · HTTPLive check: sign-in required |
| VouchedSEO data your AI can cite: Search Console, GA4, keywords, backlinks, SERPs and AI visibility. | Remote · HTTPLive check: sign-in required |
| Vox PopSearch 9 public discussion platforms for real opinions. Semantic routing, no API keys required. | Local · stdio |