Voidly Atlas (hosted) MCP server
io.github.voidly-ai/atlasvoidly-aistreamable-httpv0.1.1Scanned
Hosted, no install: read-only censorship incident records, country index data and coverage.
4 tools: 4 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Voidly Atlas (hosted) MCP server can do
The Voidly Atlas (hosted) MCP server is published by the GitHub account voidly-ai. It has 4 tools. It can create or change data (4 tools: voidly_incident_stats, voidly_incident_detail, voidly_country_data and voidly_measurement_summary), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (voidly_incident_stats, voidly_incident_detail, voidly_country_data and 1 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 4Claude Code: ask
voidly_country_dataUse this for questions like 'is the internet censored in Iran' or 'is X blocked in Y' where Y is a country: returns Voidly's country-level censorship index entry for one two-letter…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this for questions like 'is the internet censored in Iran' or 'is X blocked in Y' where Y is a country: returns Voidly's country-level censorship index entry for one two-letter country code (status level, score, OONI anomaly rate and measurement count over the index's rolling window). It is a country-level signal, not a check of one website. This connector has no per-site test. A site with no measurement is unknown, not accessible. The score is the share of OONI measurements flagged anomalous over the index window, not a measure of how censored a country is. The response update time is not when the underlying measurements were observed.
Annotations the server declares
- title: Country data
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
voidly_incident_detailUse this when you have a published Voidly incident ID (for example IR-2026-0253, from a Voidly page, report or citation) and need that censorship or shutdown incident's details: co…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this when you have a published Voidly incident ID (for example IR-2026-0253, from a Voidly page, report or citation) and need that censorship or shutdown incident's details: country, title, status, incident dates, source labels and measurement count. It cannot search incidents by country or keyword. Source labels are attribution, not independent corroboration; check status and dates before calling an incident current.
Annotations the server declares
- title: Incident record
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
voidly_incident_statsUse this for questions about how many incident records Voidly holds, such as 'how many censorship incidents has Voidly logged' or the date range of the record.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this for questions about how many incident records Voidly holds, such as 'how many censorship incidents has Voidly logged' or the date range of the record. Returns all-country counts of incident records by severity, type and status, the citable_censorship count, and the earliest and latest incident dates. The total includes connectivity-disruption signals and suspected single-source rows, so it is not a count of confirmed censorship; use citable_censorship for that. It does not filter by country and has no per-site check. A count does not show that censorship is happening now.
Annotations the server declares
- title: Incident counts
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
voidly_measurement_summaryUse this for a global overview of Voidly's censorship measurement coverage: how many countries, networks and domains are measured, and the window dates of the confirmed-block layer…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use this for a global overview of Voidly's censorship measurement coverage: how many countries, networks and domains are measured, and the window dates of the confirmed-block layer. Country and domain pairs Voidly labels confirmed means blocking was seen on 3 or more networks in the layer window; treat them as leads to check, not verdicts, and check confirmed_block_layer.window_end. When the source marks that layer under review, its counts are withheld and review.verdict is unknown. Domains outside the measured set have no finding.
Annotations the server declares
- title: Measurement summary
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://atlas-mcp.voidly.ai/mcp: tools/list returned 4 tools to an anonymous client, including voidly_incident_stats (write), voidly_incident_detail (write), voidly_country_data (write), voidly_measurement_summary (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 0 to 4
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 0 -> 4.View diff
- Tools that change things, listed without credentials: 0 to 4
Tools4 changed.~4 changedView diff
- Changed:voidly_country_dataChanges thingsdescription
- Changed:voidly_incident_detailChanges thingsdescription
- Changed:voidly_incident_statsChanges thingsdescription
- Changed:voidly_measurement_summaryChanges thingsdescription
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http atlas https://atlas-mcp.voidly.ai/mcpclaude mcp add --transport http atlas https://atlas-mcp.voidly.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__atlas__voidly_incident_stats",
"mcp__atlas__voidly_incident_detail",
"mcp__atlas__voidly_country_data",
"mcp__atlas__voidly_measurement_summary"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as atlas. Review it before you use it.
Capability tags behind 4 rules
- mcp__atlas__voidly_incident_stats untrusted-input
- mcp__atlas__voidly_incident_detail untrusted-input
- mcp__atlas__voidly_country_data untrusted-input
- mcp__atlas__voidly_measurement_summary untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.voidly-ai/atlas/verify?hash=08a9738c150b61822a071ed46abdf56bb672a230d1e6c94f40675ac7c092a15c" | jq -e '.changed == false'Pinned hash 08a9738c150b, from Nov 8, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.voidly-ai/atlas/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.voidly-ai/atlas)Source: MCP Registry. Synced Oct 23, 2026, 20:17 UTC.
Voidly Atlas (hosted) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Voidly Atlas (hosted) MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Voidly Atlas (hosted) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Voidly Atlas (hosted) MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Voidly Atlas (hosted) MCP server have?
- 4 tools: 4 write. voidly_incident_stats, voidly_incident_detail, voidly_country_data and voidly_measurement_summary.
Does the Voidly Atlas (hosted) MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Voidly Atlas (hosted) MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Voidly Atlas (hosted) MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.