pingLABSCO SUMMARY
Answers the question you actually have: is it slow from there, or from everywhere.
The network is the product - measurements come from real probes in the places you name, so 'is this reachable from China' stops being guesswork. Signing in raises your rate limits, and the quota tool tells you where you stand rather than leaving you to find out by being cut off.
What it is
jsDelivr's own server over the Globalping network. It is a remote endpoint - nothing to install - and it turns natural-language descriptions of locations into real measurements from real probes.
What you get
- The five measurement types: ping, traceroute, DNS resolution against a chosen resolver, MTR, and HTTP requests
- Locations named the way people talk about them - continents, country codes, cities, networks and ASNs, cloud regions, or combinations of these
- The list of available probe regions and filters, so you can see what you can select from
- Your current quota and usage, and retrieval of a past measurement by its ID
- A comparison helper for reading multi-region performance side by side, and a built-in tool reference
Requirements
No install: connect to the streamable HTTP endpoint at https://mcp.globalping.dev/mcp. Interactive clients authenticate over OAuth when they connect. Headless use passes a Globalping API token as a bearer header instead; tokens are generated at dash.globalping.io. Clients that can only do SSE over a local process can bridge with mcp-remote.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Checking whether a site is slow only for some users
Ping and fetch it from several continents in one question and compare the response times side by side.
02
Working out where a route goes wrong
Trace to the target from two regions and read where the paths diverge, then run MTR for packet loss along the way.
03
Confirming a DNS change has propagated
Resolve the name against specific resolvers from different countries and see which are still returning the old record.
04
Choosing where to test from
List the available probe regions and filters first, then name the ones that match the users you care about.
10 tools
Listed in project docs. Your client may show a different list.
traceroutednsmtrhttplocationslimitsgetMeasurementcompareLocationshelpBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.globalping.dev/mcpRequirements
- A Globalping account authorized over OAuth 2.0 in interactive clients, or a Globalping API token from dash.globalping.io sent as Authorization: Bearer
MCP Clients
Cursor, Any MCP client
JSON
{
"mcpServers": {
"globalping": {
"url": "https://mcp.globalping.dev/mcp"
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"globalping": {
"url": "https://mcp.globalping.dev/mcp"
}
}
}Codex
CODEX · TERMINAL
codex mcp add globalping --url https://mcp.globalping.dev/mcpClaude Code
CLAUDE CODE · TERMINAL
claude mcp add --transport http globalping https://mcp.globalping.dev/mcpGemini CLI
GEMINI CLI · TERMINAL
gemini extensions install https://github.com/jsdelivr/globalping-mcp-serverAny MCP client — legacy SSE
ANY MCP CLIENT — LEGACY SSE · TERMINAL
npx mcp-remote https://mcp.globalping.dev/sse
