About Ooni
Ooni is an MCP server for examining internet censorship and website reachability using OONI measurements. Its tools cover country-level checks, daily trends, app blocking, and individual probe results for censorship research.
Key features
- 01Check website blocking by country
- 02Track daily censorship trends
- 03Check messaging and circumvention app access
- 04Inspect raw probe measurements
Use cases
- 01Assess whether a site is blocked in a country
- 02Track when website blocking changes
- 03Check access to Telegram or Tor
- 04Review individual measurements and networks
MCP support
Exposes OONI measurement and censorship-checking tools to MCP clients. It can run locally over stdio or through the Pipeworx gateway, which adds shared meta-tools.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/ooni/mcpclaude mcp add --transport http pipeworx-io-ooni https://gateway.pipeworx.io/ooni/mcp{"mcpServers":{"pipeworx-io-ooni":{"type":"http","url":"https://gateway.pipeworx.io/ooni/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-ooni":{"type":"http","url":"https://gateway.pipeworx.io/ooni/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-ooni":{"type":"http","url":"https://gateway.pipeworx.io/ooni/mcp"}}}{"mcpServers":{"pipeworx-io-ooni":{"serverUrl":"https://gateway.pipeworx.io/ooni/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEmcp-ooni
OONI MCP — internet censorship & website reachability measurements from the
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
ooni_site_reachability | Check whether a website is blocked or censored in a specific country, using OONI network measurements from volunteer probes. Returns counts of OK, anomalous, confirmed-blocked, and failed measurements over the window plus a blocking assessment — e.g. is bbc.com blocked in China, is twitter.com blocked in Iran. Great-Firewall / national-censorship / internet-freedom research. |
ooni_blocking_trend | Daily time series of OONI censorship measurements for a website in a country — shows when blocking started, stopped, or intensified (e.g. Twitter in Iran day by day). Returns per-day OK / anomaly / confirmed-blocked counts. |
ooni_app_blocking | Check whether a messaging or circumvention app is blocked in a country using OONI app-specific tests: WhatsApp, Telegram, Signal, Facebook Messenger, or Tor. Returns measurement counts and a blocking assessment, e.g. "is Telegram blocked in Iran", "is Tor reachable from Russia". |
ooni_measurements | List recent raw OONI measurements for a domain and/or country — individual probe results with timestamp, network (ASN), anomaly/confirmed flags, and a link to the full measurement on OONI Explorer. Use after ooni_site_reachability to inspect specific blocking evidence. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"ooni": {
"url": "https://gateway.pipeworx.io/ooni/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/ooni/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/ooni_site_reachability \
-H 'Content-Type: application/json' \
-d '{"domain":"twitter.com","country":"IR"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/ooni_site_reachability. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"ooni": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-ooni"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-ooni
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Ooni data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.