Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Voidly Atlas (hosted)

REMOTE · ATLAS-MCP.VOIDLY.AI · SCANNED OCT 9

Hosted, no install: read-only internet-censorship incidents, evidence and country data.

72 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 221 tokens (~55/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Voidly Atlas (hosted) MCP server?

Voidly Atlas (hosted) is a hosted endpoint at https://atlas-mcp.voidly.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · atlas-mcp.voidly.ai

# add to Claude Code
claude mcp add --transport http voidly-ai-atlas 'https://atlas-mcp.voidly.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "voidly-ai-atlas": {
      "url": "https://atlas-mcp.voidly.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "voidly-ai-atlas": {
      "type": "http",
      "url": "https://atlas-mcp.voidly.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.voidly-ai-atlas]
url = "https://atlas-mcp.voidly.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "voidly-ai-atlas": {
      "type": "remote",
      "url": "https://atlas-mcp.voidly.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add voidly-ai-atlas --url 'https://atlas-mcp.voidly.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  voidly-ai-atlas:
    url: "https://atlas-mcp.voidly.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "voidly-ai-atlas": {
      "Transport": "http",
      "Url": "https://atlas-mcp.voidly.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add voidly-ai-atlas -t streamable-http -u 'https://atlas-mcp.voidly.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "voidly-ai-atlas": {
      "type": "http",
      "url": "https://atlas-mcp.voidly.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Oct 26 +2
    • Stability: unverified → 0.13 ▲ functional
  • 5 Oct 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 9 Oct 2026 · Probed https://atlas-mcp.voidly.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=voidly.ai CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 9b63b1cbba1cead81316c1360868796b
SANs: voidly.ai, atlas-mcp.voidly.ai, *.atlas-mcp.voidly.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of atlas-mcp.voidly.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
voidly.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://atlas-mcp.voidly.ai/mcp Verified 200
http (plaintext) http://atlas-mcp.voidly.ai/mcp HTTPS enforced 301 https://atlas-mcp.voidly.ai/mcp
MCP tools · 4 exposed · ~181 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
voidly_country_data ~43

Read one public country profile. The response update time does not establish when each underlying measurement was observed.

NameTypeReqDescription
country_codestringyesTwo-letter ISO country code.

No output schema declared.

No examples provided.

voidly_incident_detail ~70

Read one public Voidly incident record by published ID, with status, incident dates, source labels and measurement count. Source labels are attribution, not independent corroboration.

NameTypeReqDescription
incident_idstringyesPublished incident ID such as IR-2026-0253, or its hex hash ID.

No output schema declared.

No examples provided.

voidly_incident_stats ~30

Read aggregate public incident counts. Counts alone do not establish a current censorship event or measurement freshness.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

voidly_measurement_summary ~38

Read an aggregate public measurement summary and coverage. Returned definitions and dates delimit the measured scope; unmeasured domains have no accessibility finding.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Voidly Atlas (hosted) MCP server?

Voidly Atlas (hosted) is an MCP server listed in the public MCP registry as io.github.voidly-ai/atlas. Hosted, no install: read-only internet-censorship incidents, evidence and country data. This page covers its hosted endpoint (https://atlas-mcp.voidly.ai/mcp).

Is the Voidly Atlas (hosted) MCP server safe to use?

Voidly Atlas (hosted) scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Voidly Atlas (hosted) MCP server expose?

Voidly Atlas (hosted) exposes 4 tools: voidly_incident_stats, voidly_incident_detail, voidly_country_data, voidly_measurement_summary. Their descriptions and schemas cost roughly 181 tokens of context every time the server is loaded.

Does the Voidly Atlas (hosted) MCP server require authentication?

No. We connected to Voidly Atlas (hosted) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Voidly Atlas (hosted) MCP server still maintained?

Voidly Atlas (hosted) is still listed as active in the MCP registry. We last reached this channel on 9 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.