Provider REST API

8 actions

Connect Claude to Globalping

Run ping, traceroute, DNS, MTR and HTTP tests against any public host from probes around the world. Toolspoke puts 8 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: API token (optional)
Actions exposed: 8
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Globalping
Open the marketplace in your workspace, add Globalping to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Nothing to connect. Globalping needs no credential.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Globalping shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Globalping asks for

Globalping needs no credential. There is nothing to go and fetch: the settings below are optional, and they are configuration rather than secrets.

API tokenOptional: Optional. dash.globalping.io → Tokens → Generate new token. A token raises the hourly test allowance and lets tests past it spend your credits; without one, tests share the anonymous allowance.

What Claude can do in Globalping

8 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 3Reads
Writes: 5Writes
Destructive: 0Destructive

Reads

Fetches data and changes nothing.

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

Creates or updates something on the other side.

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.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 8 actions above are the whole of it. A call to any other name is refused before it reaches Globalping rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
Nothing here deletes: This connector writes to Globalping, but nothing in it deletes or permanently alters anything.
It reaches no further than your credential: Toolspoke holds no access to Globalping of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Globalping: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Globalping. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Globalping's own rate limits. A call that Globalping refuses comes back to the agent as a failed call.

Using Globalping with an agent

Written by whoever built this connector. Agents read the same text on demand through read_guide, so what is below is what they see.

Globalping

A measurement is asynchronous. Each run_* tool creates one and returns only its id and probesCount. Call get_measurement with that id until status is finished - usually a few seconds.

locations is a list of objects. The easiest form is [{"magic": "Germany"}]; magic matches a continent, country, city, ASN or network name. The structured fields (continent, country, city, asn, network, tags) and a per-location limit are also accepted. The top-level limit is how many probes run the test in total.

Targets must be public hostnames or IPs. Each probe counts as one test against the hourly allowance; get_limits shows what is left.

Before you connect it

What can Claude do in Globalping?

8 named actions: 3 that only read and 5 that write. They include run_ping, run_traceroute and run_dns. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Globalping connector need?

None at all. Globalping is reachable without one, so there is nothing of yours for Toolspoke to store. The connector does take api token as optional configuration.

Does the Globalping connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 8 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Globalping connector not do?

The 8 actions above are the whole of it. A call to any other name is refused before it reaches Globalping rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. This connector writes to Globalping, but nothing in it deletes or permanently alters anything. Toolspoke holds no access to Globalping of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Globalping. An agent has to ask. Toolspoke does not retry, queue or back off around Globalping's own rate limits. A call that Globalping refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Globalping's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Globalping?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More observability connectors

Browse all of them