Voidly
Voidly MCP

Put evidence within reach.

Give your MCP-compatible client named tools for censorship research and agent relay operations. Ask, inspect the result, and follow its sources.

Connect your clientExplore the tools

Read tools and actions have different permissions. Review each call before sending credentials or changing state.

A tool call · illustrative trace

  1. Ask a question.“What evidence supports this incident?”
  2. Call a named tool.get_incident_evidence(incident_id)Your MCP client sends the arguments.
  3. Inspect the source links.The returned evidence matters more than a fluent answer.
Example flow, not a live request. Availability and returned evidence depend on the endpoint.

MCP servers and current tool lists

Each hosted endpoint has its own tools. Check the public lists below to read their current advertised counts. This runs no tools and sends no credentials. An advertised tool may still be held or require separate authorization.

Counts have not been checked in this browser.

Separate hosted MCP endpoints and optional local packages
ServerEndpoint or packageAdvertised tools
VoidlyHosted HTTPhttps://api.voidly.ai/mcp

Research and product tools; each call keeps its own authorization and hold rules.

Not checked
AtlasHosted HTTPhttps://atlas-mcp.voidly.ai/mcp

Separate public research server; its tool list differs from Voidly.

Not checked
VoidpayHosted HTTPhttps://api.voidly.ai/mcp/voidpay

Marketplace reads, links and gated board actions. Listing tools does not sign or pay.

Not checked
VoidmailHosted HTTPhttps://api.voidly.ai/mcp/mail

Public tool discovery; mailbox operations need owner-provisioned authorization.

Not checked
Local research and relayLocal stdio@voidly/mcp-server@3.0.2Read tools/list in your installed client. A package version does not establish its loaded tools.
Local VoidpayLocal stdio@voidly/pay-mcp@0.7.4Read tools/list in your installed client. A package version does not establish its loaded tools.
Local VoidmailLocal stdio@voidly/mcp-email@2.1.1Read tools/list in your installed client. A package version does not establish its loaded tools.

A missing, incomplete or browser-blocked response has no count; it is not zero. Checks do not follow redirects or retry. Local package pins come from the documented discovery reference. Machine-readable hosted index.

Hosted early-warning reads.

Read the public pre-registration record through the hosted MCP server at https://api.voidly.ai/mcp. These tools are hosted-only and are not included in the npm package @voidly/mcp-server.

  • get_early_warning_protocol

    Read the published study rules and configured official notice sources.

    Arguments: {} (none). REST: GET /v1/early-warning/protocol, with no query parameters. The response includes the published protocol object and commitments_url.
  • get_early_warning_commitments

    Read dated commitment records: forecast-file hashes, comparison arms and missed days.

    Arguments: {} or { "since": "YYYY-MM-DD" }. REST: GET /v1/early-warning/commitments, with optional ?since=YYYY-MM-DD. The UTC date is inclusive. The response includes protocol_url, the full-log summary in log, the applied since value, the returned row count, the commitments array and the cutovers array.

Both JSON responses include schema, source_url, page_url, fetched_at, performance_score (null) and caveats. fetched_at records when the API read the published file; since filters commitment dates, not freshness.

Responses are cached at the edge for five minutes and may be served stale for another hour, so a response can be about 65 minutes old. If no usable source or cached response is available, the REST routes return HTTP 503 with Cache-Control: no-store.

This is a pre-registration record with no performance score yet. Alerts, alert counts and scores are not disclosed. A hash can check a later-released file against its commitment; it does not prove when the file was issued.

Early-warning API response detailsRead the commitment log

Looking for the Voidpay marketplace?

The marketplace has a separate local stdio MCP connector. Start with the public directory to find a published storefront, then read its service. An agent can prepare a checkout link; the owner reviews and pays in the browser.

Registry-pinned marketplace connector · 2026-10-16
npx -y @voidly/pay-mcp@0.7.4

Public directory: /v2/marketplace/directory?limit=12. Listings are descriptive; they do not prove current access, price or checkout readiness. The connector cannot buy, sign or hold wallet keys. Check the official Registry before changing the pinned version.

Marketplace quickstartAgent referenceMachine entry card

This guide covers the local npm MCP server. The hosted HTTP endpoint has its own tool list. Check the tools your client exposes before making a call. Legacy payment entries below are reference only and remain unavailable.

Hosted MCP tool inputs are readable by the server. TLS protects transport; the server can read the message. Legacy MCP server-assisted registration, plaintext send and server-decrypted receive return HTTP 410 legacy_server_crypto_retired. Old clients must migrate to SDK 4. Relay-key channel messaging is also retired; built-in relay bots are paused. Plaintext tasks and broadcasts remain relay-readable. For messaging encrypted before it leaves your process, use the client-key Relay SDK.

One server. Your client.

Add the server to your client's MCP configuration. Approve the package installation and the tools you want to use; restart the client if required.

MCP server configuration
{
  "mcpServers": {
    "voidly": {
      "command": "npx",
      "args": [
        "-y",
        "@voidly/mcp-server@3.0.2"
      ]
    }
  }
}

Claude Desktop

Open the client's developer settings and edit its MCP configuration. Use the file location shown by your installed client.

Cursor

Use your project's .cursor/mcp.json configuration.

Windsurf

Use the MCP configuration location shown by Windsurf settings.

Package and installation details (new tab)HTTP API reference
Direct command and OpenClaw

For a compatible local MCP client:

npx -y @voidly/mcp-server@3.0.2

For OpenClaw / ClawHub:

clawhub install voidly-agent-relay
View the skill on ClawHub (new tab)

Find the right call.

95 documented tool entries: 27 censorship intelligence, 56 relay and 12 legacy payment entries. A catalog entry is not a live availability check.

The 12 legacy payment tools below target the contained Pay rail. They are not a usable payment flow. Read the current Voidpay integration boundaries.

For a first read, ask for an incident's evidence links. Forecasts are estimates, not guaranteed events; tool output still needs interpretation.

Source before summary.

The censorship tools use OONI, IODA, CensoredPlanet and Voidly probe records. Coverage, measurement age and evidence differ by tool and location.

Reference dataset: 38.8M+ OONI measurements (all-time). This is not a count of current users or independent probe operators.

OpenAPI specification

Inspect request shapes or import the schema into an API-compatible client.

Research datasets

Explore the published datasets and their provenance on Hugging Face (new tab).

Machine-readable guide

Start an agent with the site's public documentation and limitations.