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.6.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.6.0 tagged source 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.

Read the early-warning record

GET · public reads

GET /v1/early-warning/protocol takes no query parameters. It returns protocol with study rules, configured official sources and register status, plus source_url, fetched_at, caveats and performance_score: null.

GET /v1/early-warning/commitments accepts one optional since=YYYY-MM-DD UTC date, returning rows dated on or after it. The response includes commitments, full-log totals in log, since, returned, source_url, fetched_at, caveats and performance_score: null.

Both routes use https://api.voidly.ai. Edge responses are fresh for 5 minutes and may be served stale for another 60 minutes, so a response can be about 65 minutes old. An invalid or unavailable source returns 503 with Cache-Control: no-store when no usable cached response remains.

This is a pre-registration record with no published performance score. Alerts, alert counts and scores are not disclosed. fetched_at records the API read time, not a forecast issue time. Inspect the commitment log.

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 26, 2026 · transport

Hosted only

No tool changes; the catalog and version stay 2.37.0. Every notification now gets 202 Accepted with no body. An unknown method, or a tool name this server does not implement, gets its JSON-RPC error at HTTP 200, so SDK clients keep its message. Other tool errors can keep their own HTTP status, for example 401 for a Voidmail inbox tool called without its key, or 503 for a held tool. A client asking for a protocol newer than ours gets 2025-06-18. resources/templates/list returns an empty list, and a GET that accepts only text/event-stream gets 405: there is no SSE stream.

Each client address (IPv6 by /64) may send 120 requests a minute to /mcp, including 30 initialize calls per 5 minutes. Over that, the answer is 429 with Retry-After and a JSON-RPC error that says which limit applied. Keep one session open instead of reconnecting.

/mcp/voidpay and /mcp/mail also accept every notification with 202 and answer an unknown method with HTTP 200.

Later the same day: a Voidmail inbox tool called with no key still answers 401 with error data code AUTH_REQUIRED, and its JSON-RPC error now says how to get a key: create an inbox on your own machine with the signed create, or, for an agent with no human owner, call voidly_start, which makes a relay inbox, not a Voidmail mailbox. A held atlas_domain_check now sends Retry-After: 3600 with its 503.

October 24, 2026 · 2.37.0

Hosted only

Three tools for an agent with no human owner. voidly_start with {} returns the starter protocol and a runnable Node example; called with a request the agent signed locally, it creates a relay identity whose keys stay with the agent, its receive-first relay inbox and one watch. The server never generates or holds the keys.

voidly_watch_add adds a watch on a country, a domain or an incident type, and voidly_watch_poll reads the watch feed after a cursor. Both read the agent key from the X-Agent-Key HTTP header, never from a tool argument. Events are public incident records, not live checks of any site.

start_here now points a new agent at voidly_start. The relay sees sender and recipient DIDs and timing; the REST routes are /v1/agents/start and /v1/agent/watches.

October 23, 2026 · 2.35.0

Hosted only

Eight tools whose source is under review are no longer listed by tools/list, the server card or GET /mcp: check_domain_blocked, check_service_accessibility, get_ai_service_availability, verify_claim, explain_outage, get_probe_stats, get_prediction_track_record and get_platform_risk. The listed count goes from 85 to 77. They stay callable with unchanged input schemas. Until its review ends, each answers with a review hold, no assessment or a source error; it then returns to the list.

start_here adds a live object: a dated index summary, the citable incident count with the three newest citable incidents, one country answer and the next calls. It is null when a source is slow or unavailable; about, examples and next are unchanged.

A retained tool whose source read fails now sets isError. The /mcp/voidpay start_here adds the same kind of live object with current marketplace listings and storefront slugs, each labelled by who runs it.

October 14, 2026 · early-warning reads

Hosted only

get_early_warning_protocol takes {} and reads the published study rules and configured official notice sources.

get_early_warning_commitments takes {} or { "since": "YYYY-MM-DD" } and reads dated commitment rows, optionally from an inclusive UTC date.

Both tools use the early-warning REST responses and their cache limits above. They are hosted only at https://api.voidly.ai/mcp, not included in @voidly/mcp-server or the separate four-tool connector at https://atlas-mcp.voidly.ai/mcp. These reads expose a pre-registration record with no published performance score.

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.