# RIPE Atlas [Health: Active]

**Category:** 📊 Monitoring  
**Repository:** https://github.com/jrelph/ripe-atlas-mcp  
**GitHub Stars:** 5  
**npm Downloads (last month):** 163  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ripe-atlas

## Description
RIPE Atlas network measurements — ping, traceroute, DNS, TLS, HTTP, NTP, and probes

## Tools
Capabilities this server exposes over MCP:

- **atlas_measure_ping** — Create a ping measurement on the RIPE Atlas network.

Sends ICMP echo requests from distributed probes worldwide to a target host.

Args:
  - target (string): Target hostname or IP address
  - af (4|6): Address family (default: 4)
  - packets (1-16): Number of packets (default: 3)
  - size (1-2048): Packet size in bytes (default: 48)
  - probe_count (1-1000): Number of probes (default: 5)
  - from_country/from_asn/from_prefix/from_area/from_probes: Probe selection
  - is_oneoff (bool): One-shot measurement (default: true)
  - response_format ('json'|'markdown'): Output format

Returns: Measurement ID(s) and link to results.

Requires: RIPE_ATLAS_API_KEY with 'create measurement' permission.
- **atlas_measure_traceroute** — Create a traceroute measurement on the RIPE Atlas network.

Traces the network path from distributed probes to a target, showing each hop.

Args:
  - target (string): Target hostname or IP
  - protocol ('ICMP'|'UDP'|'TCP'): Protocol (default: ICMP)
  - max_hops (1-255): Max TTL (default: 32)
  - paris (0-64): Paris traceroute mode (default: 16, 0=standard)
  - port (1-65535): Destination port (TCP only)
  - probe_count, from_country, etc.: Probe selection

Returns: Measurement ID(s).

Requires: RIPE_ATLAS_API_KEY with 'create measurement' permission.
- **atlas_measure_dns** — Create a DNS measurement on the RIPE Atlas network.

Performs DNS lookups from distributed probes. Can query specific DNS servers or use the probe's local resolver.

Args:
  - query_argument (string): DNS name to query (e.g. 'example.com')
  - query_type: Record type (A, AAAA, MX, NS, SOA, TXT, CNAME, DNSKEY, etc.)
  - target (string, optional): DNS server to query. Omit to use probe's resolver.
  - set_rd_bit: Recursion Desired (default: true)
  - set_do_bit: DNSSEC OK flag
  - set_cd_bit: DNSSEC Checking Disabled
  - set_nsid_bit: Request Name Server ID
  - protocol ('UDP'|'TCP'): Transport (default: UDP)
  - probe_count, from_country, etc.: Probe selection

Returns: Measurement ID(s).

Requires: RIPE_ATLAS_API_KEY with 'create measurement' permission.
- **atlas_measure_tls** — Create a TLS/SSL certificate check measurement on the RIPE Atlas network.

Connects to a target and retrieves its TLS certificate from distributed probes worldwide.

Args:
  - target (string): Target hostname or IP
  - port (1-65535): Port to connect to (default: 443)
  - probe_count, from_country, etc.: Probe selection

Returns: Measurement ID(s).

Requires: RIPE_ATLAS_API_KEY with 'create measurement' permission.
- **atlas_measure_http** — Create an HTTP measurement on the RIPE Atlas network.

Makes HTTP requests from distributed probes to a target web server.

Args:
  - target (string): Target hostname or IP
  - method ('GET'|'HEAD'|'POST'): HTTP method (default: GET)
  - path (string): URL path (default: '/')
  - port (1-65535): Port (default: 80)
  - version (string): HTTP version (default: '1.1')
  - header_bytes: Max header bytes to capture
  - body_bytes: Max body bytes to capture
  - timing_verbosity (0|1|2): Detail level
  - probe_count, from_country, etc.: Probe selection

Returns: Measurement ID(s).

Requires: RIPE_ATLAS_API_KEY with 'create measurement' permission.
- **atlas_measure_ntp** — Create an NTP measurement on the RIPE Atlas network.

Queries NTP time servers from distributed probes to measure clock offset and delay.

Args:
  - target (string): NTP server hostname or IP
  - packets (1-16): Number of packets (default: 3)
  - timeout: Timeout per packet in ms
  - probe_count, from_country, etc.: Probe selection

Returns: Measurement ID(s).

Requires: RIPE_ATLAS_API_KEY with 'create measurement' permission.
- **atlas_list_measurements** — Search and list RIPE Atlas measurements with comprehensive filters.

Args:
  - search: Free-text search on target/description
  - type: Filter by measurement type (ping, traceroute, dns, sslcert, http, ntp)
  - status: Filter by status (2=Ongoing, 4=Stopped, etc.)
  - af: Address family (4 or 6)
  - target/target_contains: Filter by target
  - mine: Show only your measurements (requires API key)
  - page/page_size: Pagination
  - sort: Sort order (e.g. '-id' for newest first)

Returns: Paginated list of measurements.
- **atlas_get_measurement** — Get detailed information about a specific RIPE Atlas measurement by ID.

Args:
  - measurement_id (number): The measurement ID
  - response_format ('json'|'markdown'): Output format

Returns: Full measurement metadata including type, target, status, probes, timestamps.
- **atlas_get_results** — Retrieve results from a RIPE Atlas measurement.

Can fetch all results, latest results only, or filter by time range and probe IDs.

Args:
  - measurement_id (number): The measurement ID
  - latest (bool): If true, get only latest results (default: false)
  - start (unix timestamp): Only results after this time
  - stop (unix timestamp): Only results before this time
  - probe_ids (string): Comma-separated probe IDs to filter
  - response_format ('json'|'markdown'): Output format

Returns: Measurement results with per-probe data (RTT, hops, DNS answers, etc.)
- **atlas_stop_measurement** — Stop a running RIPE Atlas measurement.

Args:
  - measurement_id (number): The measurement ID to stop

Returns: Confirmation of the stop request.

Requires: RIPE_ATLAS_API_KEY with appropriate permissions.
- **atlas_search_probes** — Search for RIPE Atlas probes worldwide with filters for location, network, and status.

Args:
  - country (string): Two-letter ISO country code (e.g. 'DE', 'US', 'AU')
  - asn (number): Filter by ASN (IPv4)
  - asn_v6 (number): Filter by ASN (IPv6)
  - prefix (string): Filter by IPv4 prefix (e.g. '193.0.0.0/21')
  - prefix_v6 (string): Filter by IPv6 prefix
  - status (1|2|3): 1=Connected, 2=Disconnected, 3=Abandoned
  - is_anchor (bool): Only anchor probes
  - tags (string): Comma-separated tag slugs
  - search (string): Free-text search
  - sort (string): Sort field (e.g. 'id', '-id')
  - page/page_size: Pagination

Returns: Paginated list of probes with ID, country, ASN, status, tags.
- **atlas_get_probe** — Get detailed information about a specific RIPE Atlas probe by ID.

Args:
  - probe_id (number): The probe ID to retrieve
  - response_format ('json'|'markdown'): Output format

Returns: Probe details including country, ASN, prefix, status, tags, coordinates.
- **atlas_get_credits** — Check your RIPE Atlas credit balance and usage statistics.

Args:
  - response_format ('json'|'markdown'): Output format

Returns: Current balance, daily income/expenditure, estimated runout.

Requires: RIPE_ATLAS_API_KEY environment variable.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "ripe-atlas": {
    "command": "npx",
    "args": ["-y","ripe-atlas-mcp-server"],
    "env": {
      "RIPE_ATLAS_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `RIPE_ATLAS_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/ripe-atlas/readme_