# CloudPing MCP server

> Lets an AI client run ping, traceroute, DNS and HTTP probes from distributed global agents and stream the results as JSON.

- Repository: https://github.com/internetworklab/cloudping
- Page: https://hostedmcp.org/servers/internetworklab/cloudping
- Transport: —
- Stars: 24
- License: MIT

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `DN42_ASN` | no | no |  |
| `DN42_ISP` | no | no |  |
| `EXACT_LOCATION_LAT_LON` | no | no |  |
| `JWT_TOKEN` | no | no |  |
| `NODE_NAME` | no | no |  |
| `SUBNET_OVERRIDE` | no | no |  |

## FAQ

### What probes can CloudPing run?

It supports ping, traceroute (UDP or ICMP), TCP ping, DNS probes, HTTP probes across HTTP/1.1, HTTP/2 and HTTP/3, and BGP route lookup via MRT data.

### How does the CloudPing MCP server authenticate clients?

The MCP server uses StreamableHTTP with JWT authentication.

### What format do CloudPing API responses use?

Responses are streamed as newline-delimited JSON lines using a line feed delimiter.

### Can I use an already deployed CloudPing instance instead of building it?

Yes, a public instance is available at ping2.sh, and a DN42 instance at ping.dn42. Nothing needs to be built or installed.

### Does CloudPing support BGP route lookups?

Yes, it offers BGP Route Lookup via MRT data, queryable by origin ASN, neighbor ASN, AS path segments and IP/CIDR prefix.
