Developer · Local MCP server
RIPE Atlas
RIPE Atlas network measurements - ping, traceroute, DNS, TLS, HTTP, NTP, and probes.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.jrelph/ripe-atlas- Version
- 1.0.2
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-07-07
- Updated
- 2026-07-07
- Publisher
- jrelph (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/jrelph) · how
- Website
- atlas.ripe.net
- Repository
- github.com/jrelph/ripe-atlas-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | ripe-atlas-mcp-server | 1.0.2 | stdio |
How to connect RIPE Atlas
RIPE Atlas runs locally from a Node.js package published to the npm registry: ripe-atlas-mcp-server version 1.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y ripe-atlas-mcp-server@1.0.2. It reads the environment variable RIPE_ATLAS_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"ripe-atlas": {
"command": "npx",
"args": [
"-y",
"ripe-atlas-mcp-server@1.0.2"
],
"env": {
"RIPE_ATLAS_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| RheaRhea MCP - expert-curated database of biochemical reactions. | Remote · HTTPLive check: ✓ handshake |
| RideDesk Developer DocsDeveloper docs for building on RideDesk: booking API, widgets, per-account booking MCP. No auth. | Remote · HTTPLive check: ✓ handshake |
| Rigor MCPVerified statistical inference for AI agents: hypothesis tests, sequential testing, power. | Local · stdio |
| RigourQuality gates for AI agents. Lint, test, build checks with memory persistence. | Local · stdio |
| RiskRover MCPDraft risk-based test plans and assess automated test coverage against product risks with RiskRover. | Local · stdio |
| RivetManage Rivet Cloud namespaces and actors, run Code Mode, and open the Rivet Actor Inspector. | Remote & Local · HTTP, stdioLive check: sign-in required |
| rlayShared channels where agents from different vendors collaborate over a relayed message log. | Remote · HTTPLive check: sign-in required |
| Rlg MCPMCP server exposing rlg log streams to LLM agents via JSON-RPC 2.0 over stdio. | Local · stdio |