Voidly

Voidly developers

Start with the exact connection.

Four practical entry points. Copy a starting command, then read the boundary before you build on it.

MCP · research

Atlas MCP

Ask for published incidents, country profiles, and measurement coverage. Keep the source and observation window with any answer.

Read the hosted connector guide

Run locally

Node 18+

Add this stdio server to your MCP client. The npm package has a broader catalog than the hosted four-tool connector.

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

Pin: @voidly/mcp-server@3.0.2. Review its tool list in your client before granting access.

Connect to the hosted read service

Public · no login

Paste this in Claude Code. Its four read-only tools cover incident statistics, one incident, one country, and measurement summary.

Claude Code terminal
claude mcp add --transport http voidly-atlas https://atlas-mcp.voidly.ai/mcp

Remote MCP URL: https://atlas-mcp.voidly.ai/mcp. The separate https://api.voidly.ai/mcp service has a different, broader catalog. A fresh response can still describe older observations. See hosted MCP changes.

MCP · marketplace

Voidpay MCP

Discover public services first. Creator actions need an owner-approved grant. A checkout link hands review to the owner's browser; the connector does not sign or pay.

Read the public package source

Run locally

Node 20+

Add the 12-tool stdio package. Public discovery needs no credential; creator operations require the documented private setup and scoped owner consent.

Voidpay local MCP configuration
{
  "mcpServers": {
    "voidpay": {
      "command": "npx",
      "args": [
        "-y",
        "@voidly/pay-mcp@0.7.4"
      ]
    }
  }
}

Pin: @voidly/pay-mcp@0.7.4. Never put a wallet key in MCP configuration.

Hosted connector

No install

Point an MCP client that supports Streamable HTTP at the hosted endpoint. Public reads need no key or install. Checkout-link preparation hands approval to the owner's browser; this connector has no wallet or payment action.

Streamable HTTP endpoint
https://api.voidly.ai/mcp/voidpay

Read the hosted connector guide. A listing is not a promise of availability or delivery.

Pay with a local agent wallet

x402 · separate from MCP

For a supported Base resource, inspect its current HTTP 402 amount, token and recipient before a configured wallet signs. @voidly/agent-wallet@0.2.0 keeps per-call and daily limits in its local ledger; those limits do not govern every transaction from the address. The CLI selects its fixed gateway from required --network; MCP Base mainnet also requires an explicit allowed-origin list.

Review wallet 0.2.0 release and inspect the public x402 catalog (JSON). The separate /v1/directory integration API is release-gated and is not a connection URL here. See the agent start path.

SDK · agent work

Sessions SDK

Check the installed package offline before connecting an approved service. The self-test checks a bundled signed provider fixture and tampering cases; it does not verify package provenance, test a live provider, or make a payment.

Read the application requirements

Install and self-test

Node 20.3+ for CLI
Sessions terminal
npm install --ignore-scripts --save-exact @voidly/session@1.4.3
node node_modules/@voidly/session/dist/proofsCli.mjs self-test

Pin: @voidly/session@1.4.3. An ok: true result is an offline check only. Paid jobs require an admitted app, owner-approved scope, a customer-controlled signer, persistent private storage, and separate settlement and delivery evidence.

HTTP · public read

REST API

Start with one public Atlas endpoint. The count summarizes published incident records; it does not measure your own network.

Browse the API reference

Request incident statistics

GET · no key for this read
REST terminal
curl --fail --silent --show-error   'https://api.voidly.ai/data/incidents/stats'

Check dates and coverage before citing the result. Other API routes can have different access rules and limits.

MCP · changelog

Hosted MCP changes

Check the served catalog before using a new tool. The server card and tools/list describe what the hosted endpoint currently offers.

Inspect the hosted server card

October 5, 2026 · proposed 2.11.0

Source proposal

The proposed release keeps the 54 existing tools and their input schemas callable at https://api.voidly.ai/mcp. It adds four Voidpay reads and four Voidmail tools, with mailbox reads requiring the agent bearer. This entry does not establish deployment or served availability.

Planned 2.12.0 · Atlas reads

Approval gated

Eight Atlas read aliases are proposed for the same endpoint. They appear only after separate owner approval and a served catalog check.

Version and deprecation policy

Hosted /mcp

The MCP protocol version, hosted server release version, and tool catalog are separate. Additive tools use a minor server release and are dated here when served. Breaking tool renames, removals, or input-schema changes use a major release after at least 90 days of notice and migration notes here. A renamed tool keeps its old alias callable throughout that notice.