RIPE Atlas logo

RIPE Atlas

Run distributed RIPE Atlas measurements and inspect probes, results, measurement status, and credit usage through MCP.

Install RIPE Atlas

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ripe-atlas": {
      "command": "npx",
      "args": [
        "-y",
        "ripe-atlas-mcp-server"
      ],
      "env": {
        "RIPE_ATLAS_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Automated check passed— started and listed 13 tools correctly (5d ago).

Overview

RIPE Atlas MCP server connects AI assistants to the RIPE Atlas network measurement platform. It can create ping, traceroute, DNS, TLS, HTTP, and NTP measurements, then retrieve results and measurement details. Probe searches support filters such as country, ASN, prefix, status, and tags, while result queries can be narrowed by time or probe. Reach for it when you need Internet measurements from distributed vantage points through an MCP-compatible client.

Use cases

  • Run ping measurements from probes in selected countries
  • Compare DNS responses across distributed probes
  • Trace routes through a chosen ASN or geographic area
  • Check TLS certificates or HTTP responses from multiple locations
  • Inspect measurement results and RIPE Atlas credit usage

Key features

  • Creates six types of RIPE Atlas measurements
  • Selects probes by country, ASN, prefix, area, ID, or tags
  • Retrieves results with time and probe filters
  • Returns JSON or Markdown responses
  • Searches and inspects distributed probes
  • Reports credit balance and usage statistics

Tools13

What RIPE Atlas lets your agent do. Expand a tool for its parameters.

Verified live~7.3k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 46d

What it can do

From the 13 tools this server returned when we ran it; 13 declare their own safety hints.

Can delete or modify data · 1Handles credentials · 1Makes network requests · 13Read-only tools · 12
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age188 days
Maintainers1

Observed 2026-10-23 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · ripe-atlas-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5Stargazers on the source repository.
npm downloads163Package downloads in the last 30 days.
Last commit2mo agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed13Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How RIPE Atlas works

What RIPE Atlas MCP server does

The RIPE Atlas MCP server exposes the RIPE Atlas measurement platform as MCP tools for AI assistants. It supports six measurement types: ICMP ping, traceroute over ICMP, UDP, or TCP, DNS lookups with DNSSEC support, TLS/SSL certificate checks, HTTP requests using GET, HEAD, or POST, and NTP time queries.

The server also covers the measurement lifecycle. Agents can list measurements with filters, inspect a measurement by ID, retrieve results, and stop a running measurement. Separate probe tools search for probes and return details for a specific probe. Credit information is available through an account tool.

How it works

The RIPE Atlas MCP server sends measurement requests to RIPE Atlas, which runs them from distributed network probes. Measurement creation accepts a target hostname or IP address, IPv4 or IPv6 selection, and a probe count from 1 to 1000. Probe selection can be based on country, ASN, IP prefix, geographic area, explicit probe IDs, or included and excluded tags.

Measurements can run once or recur. Result retrieval supports time-range filters, probe filters, and a latest-only mode. Tool responses can use JSON for structured handling or Markdown for human-readable output. The underlying RIPE Atlas network consists of hardware and software probes hosted around the world.

Setup and configuration

Install the package with npx ripe-atlas-mcp-server, or install it globally with npm install -g ripe-atlas-mcp-server. The repository also documents a source build using npm install followed by npm run build.

Creating measurements requires a free RIPE Atlas account, an API key, and the key's “Create measurements” permission. Set that key in RIPE_ATLAS_API_KEY. Read-only actions, including listing measurements and searching probes, work without an API key.

The README provides stdio configurations for Claude Desktop, VS Code with GitHub Copilot, and Cursor. Each configuration starts the package with npx and passes the API key through the client's environment settings.

Tools and capabilities

The available tools are:

  • atlas_measure_ping, atlas_measure_traceroute, atlas_measure_dns, atlas_measure_tls, atlas_measure_http, and atlas_measure_ntp for creating measurements.
  • atlas_list_measurements, atlas_get_measurement, atlas_get_results, and atlas_stop_measurement for measurement management.
  • atlas_search_probes and atlas_get_probe for probe discovery and details.
  • atlas_get_credits for credit balance and usage statistics.

Use the RIPE Atlas MCP server for distributed reachability checks, route inspection, DNS comparison, certificate checks, HTTP testing, time queries, or locating probes by network and geography.

Limitations and notes

Creating measurements consumes RIPE Atlas account permissions and credits, so check credit usage before running larger or recurring jobs. The API key is not needed for the documented read-only operations, but it is needed to create measurements. Probe availability and returned results depend on the RIPE Atlas network and the filters supplied to each request.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about RIPE Atlas

RIPE Atlas is an MCP server that connects AI assistants to the RIPE Atlas network measurement platform. Its main tools create ping, traceroute, DNS, TLS, HTTP, and NTP measurements, retrieve results, search probes, manage measurements, and check account credits.

Install it by running `npx ripe-atlas-mcp-server`, or install the package globally with `npm install -g ripe-atlas-mcp-server`.

Yes, RIPE Atlas works with Cursor through its MCP configuration. Add a server entry that runs `npx -y ripe-atlas-mcp-server` and provide `RIPE_ATLAS_API_KEY` in the configuration environment when creating measurements.

You need an API key to create measurements, but not for documented read-only operations. Create a RIPE Atlas account, generate a key with “Create measurements” permission, and set it as `RIPE_ATLAS_API_KEY`.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewRIPE Atlas AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ripe-atlas?style=directory)](https://allmcps.com/mcp/ripe-atlas)
HTML Embed
<a href="https://allmcps.com/mcp/ripe-atlas"><img src="https://allmcps.com/api/badge/ripe-atlas?style=directory" alt="RIPE Atlas on AllMCPs" /></a>