Connect Globalping to Claude Code
Run ping, traceroute, DNS, MTR and HTTP tests against any public host from probes around the world. Add Toolspoke to Claude Code once and it can use 8 Globalping actions. Your Globalping credential stays in Toolspoke, and you choose which actions Claude Code may call.
Set it up in Claude Code
Three steps, the first one once for every toolkit you will ever add.
Add Toolspoke to Claude Code
Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcpThe sign-in opens in your browser, and Toolspoke asks you to approve it.
Install Globalping and connect it
Add Globalping to a project in your Toolspoke workspace.
Globalping needs no credential. There is nothing to go and fetch: the settings below are optional, and they are configuration rather than secrets.
Choose what Claude Code may do
All 8 actions start on. Switch off any of the 5 actions that change something in Globalping, and Claude Code gets a refusal if it tries.
What you can ask Claude Code for
A few of the Globalping actions that only read, so they are safe to try first.
- Read a measurement's status and per-probe results by id
- Show the hourly test allowance left for this token (or this server's IP without one) and the remaining credits
What Claude Code can do in Globalping
3 actions read and 5 write.
Reads
Get measurement
Read a measurement's status and per-probe results by id. Call again until status is finished. Reading does not use the test allowance.
List probes
List every probe online now with its continent, country, city, ASN, network and tags, the values a locations filter matches. The list is long; prefer magic locations unless you need exact values.
Get limits
Show the hourly test allowance left for this token (or this server's IP without one) and the remaining credits. Free, and it fails on a bad token, so it is what an install tests itself with.
Writes
Run ping
Ping a host from probes worldwide to measure latency and packet loss. Returns a measurement id; read the result with get_measurement. Uses one test from the hourly allowance per probe, and credits once that is spent.
Run traceroute
Trace the network path to a host from probes worldwide. Returns a measurement id; read the result with get_measurement.
Run dns
Resolve a name from probes worldwide, to check propagation or compare answers between regions. Returns a measurement id; read the result with get_measurement.
Run mtr
Run MTR (traceroute plus per-hop loss and latency) to a host from probes worldwide. Returns a measurement id; read the result with get_measurement.
Run http
Send an HTTP HEAD, GET or OPTIONS request to a host from probes worldwide, with timings and TLS details. Returns a measurement id; read the result with get_measurement.
Globalping in Claude Code: questions
Does Claude Code see my Globalping credential?
No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.
Can I stop Claude Code from changing things in Globalping?
Yes. Each of the 8 actions can be switched off for a project. Turn off the 5 that change something and Claude Code can only read.
Will 8 actions crowd Claude Code's context?
No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Globalping action it needs when it needs it. Adding more toolkits does not add more tools to its list.
Can I add it once for every project?
Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.
What does it cost?
Tool calls are free on every plan, and a Globalping call does not run in a sandbox, so it bills nothing.
Globalping in your other apps
Try Globalping in Claude Code
Free to start, and tool calls cost nothing on any plan.