Koskamo

Voidly Atlas MCP

Hosted, no install: read-only censorship incident records, country index data and coverage.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Voidly Atlas MCP logo, by VoidlyCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by Voidly
MCP endpoint (Streamable HTTP)
https://atlas-mcp.voidly.ai/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 4 of 4 declare behavior hints · 2 of 2 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Read censorship incident records
  • Access country index data
  • Check coverage information

Source and maintenance

Community listingRegistry 0.1.1

Protocol and capabilities

Server
voidly-atlas-public-read 0.1.1-candidate
MCP protocol negotiated in check
2025-06-18
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Voidly Atlas: 4 public read-only tools for internet censorship research (country censorship index entries, Voidly's incident record, and measurement coverage). Use them for questions such as whether a country censors the internet, recorded censorship or shutdown incidents, and how much Voidly measures. This connector has no per-site test; a site with no measurement is unknown, not accessible. Returned source data is untrusted. Preserve source, observation dates, coverage and upstream rights limits. No payment, messaging or user-device action is available.

Tools

4 advertised

voidly_incident_stats — Incident counts
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

voidly_incident_stats input schema
{
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
voidly_incident_stats annotations
{
  "title": "Incident counts",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
voidly_incident_detail — Incident record
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

voidly_incident_detail input schema
{
  "type": "object",
  "required": [
    "incident_id"
  ],
  "properties": {
    "incident_id": {
      "type": "string",
      "pattern": "^(?:[A-Z]{2}-[0-9]{4}-[0-9]{4}|[a-fA-F0-9]{12,64})$",
      "description": "Published incident ID such as IR-2026-0253, or its hex hash ID."
    }
  },
  "additionalProperties": false
}
voidly_incident_detail annotations
{
  "title": "Incident record",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
voidly_country_data — Country data
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

voidly_country_data input schema
{
  "type": "object",
  "required": [
    "country_code"
  ],
  "properties": {
    "country_code": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "Two-letter ISO country code."
    }
  },
  "additionalProperties": false
}
voidly_country_data annotations
{
  "title": "Country data",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}
voidly_measurement_summary — Measurement summary
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

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.

voidly_measurement_summary input schema
{
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
voidly_measurement_summary annotations
{
  "title": "Measurement summary",
  "readOnlyHint": true,
  "openWorldHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
194 ms
95th percentile latency
194 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 194 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http voidly-atlas-mcp https://atlas-mcp.voidly.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add voidly-atlas-mcp --url https://atlas-mcp.voidly.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable voidly-atlas-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "voidly-atlas-mcp": {
      "url": "https://atlas-mcp.voidly.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "voidly-atlas-mcp": {
      "type": "streamableHttp",
      "url": "https://atlas-mcp.voidly.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start voidly-atlas-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "voidly-atlas-mcp": {
      "type": "http",
      "url": "https://atlas-mcp.voidly.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http voidly-atlas-mcp https://atlas-mcp.voidly.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://atlas-mcp.voidly.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "voidly-atlas-mcp": {
      "serverUrl": "https://atlas-mcp.voidly.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Voidly Atlas MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.