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 client Explore the tools

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

A tool call · illustrative trace

Ask a question.“What evidence supports this incident?”
Call a named tool.get_incident_evidence(incident_id)Your MCP client sends the arguments.
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.

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.

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"
      ]
    }
  }
}

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 @voidly/mcp-server

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. Server-side messaging tools do not have the same privacy boundary as the client-side Relay SDK.

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.