RIPE Atlas — Claude Code MCP server: what it does, how to install
RIPE Atlas runs ping, traceroute, DNS, and HTTP checks across thousands of global probes directly through an MCP-connected assistant.
MIT ★ 5 updated 2026-08-01
claude mcp add ripe-atlas -e RIPE_ATLAS_API_KEY=<RIPE_ATLAS_API_KEY> -- npx -y ripe-atlas-mcp-serverWhat RIPE Atlas does
This server connects AI coding assistants to the RIPE Atlas hardware and software probe network. It equips agents with dedicated tools to execute six network diagnostics: ICMP ping (atlas_measure_ping), traceroute with ICMP, UDP, or TCP targets (atlas_measure_traceroute), DNSSEC-aware DNS resolution, TLS certificate verification, HTTP requests, and NTP synchronization checks. Measurement outputs return in either Markdown or structured JSON.
Probe selection is fully configurable. You can define target address families (IPv4 or IPv6), probe sample counts between 1 and 1000, or filter by ISO country codes, autonomous system numbers (ASN), IP prefixes, and geographic zones. Built-in discovery tools like atlas_search_probes explore active vantage points, while atlas_get_credits tracks remaining measurement credits on your account.
Read-only lookups work anonymously, but triggering any live measurement fails without setting RIPE_ATLAS_API_KEY with creation rights.
What it helps with
- verify routing paths with multi-protocol traceroute from selected ASNs
- check global DNS record propagation across distributed vantage points
- inspect remote TLS certificates and HTTP responses from specific countries
- locate active measurement probes by prefix, ASN, or geographic region
Example prompts for the agent
- Ping 1.1.1.1 from 10 probes worldwide
- Run an ICMP traceroute to 8.8.8.8 using 5 probes located in Germany
- Look up AAAA records for example.com from 50 global probes
How to install RIPE Atlas
Platform CLI
claude mcp add ripe-atlas -e RIPE_ATLAS_API_KEY=<RIPE_ATLAS_API_KEY> -- npx -y ripe-atlas-mcp-serverReplace <…> with your own values
Platform CLI
codex mcp add ripe-atlas --env RIPE_ATLAS_API_KEY=<RIPE_ATLAS_API_KEY> -- npx -y ripe-atlas-mcp-serverReplace <…> with your own values
Config file
{
"mcpServers": {
"ripe-atlas": {
"command": "npx",
"args": [
"-y",
"ripe-atlas-mcp-server"
],
"env": {
"RIPE_ATLAS_API_KEY": "<RIPE_ATLAS_API_KEY>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"ripe-atlas": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ripe-atlas-mcp-server"
],
"env": {
"RIPE_ATLAS_API_KEY": "<RIPE_ATLAS_API_KEY>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e RIPE_ATLAS_API_KEY=<RIPE_ATLAS_API_KEY> ripe-atlas npx -y ripe-atlas-mcp-serverReplace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about RIPE Atlas
How to install RIPE Atlas in Claude Code?
Run claude mcp add ripe-atlas -e RIPE_ATLAS_API_KEY=<RIPE_ATLAS_API_KEY> -- npx -y ripe-atlas-mcp-server. Ensure Node.js and npx are installed on your machine.
What does the RIPE Atlas MCP server do?
It exposes RIPE Atlas diagnostics to MCP clients, letting assistants run network measurements like ping, traceroute, and DNS queries. Results arrive from real hardware and software probes across the globe.
Do I need an API key to use this server?
Searching probes and reading previous measurement records work without authentication. Running new tests requires a valid RIPE_ATLAS_API_KEY with measurement creation permissions and sufficient credits.