Docs/Sources/Uptime Ping Grounding Data

Uptime Ping Grounding Data

Ping a URL to check if it's up

OperationalCredits 2 per callp50 233msNetworking

Overview

Send a POST request with a hostname or public IP address and the desired ping count. The service contacts the target in real time to evaluate reachability and completed round trips. Paid plans can configure custom millisecond timeouts and receive numeric IP resolution, packet loss percentages, and detailed latency metrics.

Live Test Uptime Ping Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as UptimePingGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "UptimePingGroundingData",
  "arguments": {
    "host": "google.com"
  }
}

You do not name the tool yourself; the model picks it. Asking about google.com in the terms this source covers is enough for it to reach for UptimePingGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
hostRequiredstringThe host name or public IP that you want to ping
timeoutOptionalPremiumintegerThe timeout for the ping request in milliseconds
default 1500 · range 100–3000
roundTripsOptionalintegerHow many pings to send before averaging the round-trip time
default 1 · range 1–5

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "host": "google.com",
    "numericHost": "2607:f8b0:4001:c6e::8a",
    "alive": true,
    "roundTrips": 3,
    "packetLoss": 0,
    "minMS": 0.652,
    "avgMS": 0.6846666666666666,
    "maxMS": 0.712,
    "stdDev": 0.02478350706058811,
    "times": [
      0.712,
      0.652,
      0.69
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
hoststringgoogle.comThe hostname or IP address that was pinged
numericHostPremiumstring2607:f8b0:4001:c6e::8aThe numeric IP address of the host that was pinged
alivebooleantrueWhether the host is reachable and responding to ping requests
roundTripsnumber3Number of successful ping round trips completed
packetLossPremiumnumber0Percentage of packets lost during the ping operation
minMSPremiumnumber0.652Minimum round trip time in milliseconds
avgMSPremiumnumber0.6846666666666666Average round trip time in milliseconds
maxMSPremiumnumber0.712Maximum round trip time in milliseconds
stdDevPremiumnumber0.02478350706058811Standard deviation of round trip times
timesPremiumarray[0.712,0.652,0.69]Array of individual round trip times in milliseconds

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at alive: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This source is not part of VerveContext. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Server Reachability Checks
DevOps engineers trigger ping checks during deployments to confirm that newly provisioned web servers respond before routing production traffic to them.
Network Latency Monitoring
When network engineers detect sluggish connections, they inspect round-trip responses across public IP endpoints to diagnose potential packet drop issues.
Domain Availability Verification
To catch outages fast, internal status dashboards poll critical external third-party hostnames and display immediate alive indicators to support staff.
Automated Incident Triage
Alerting systems ping reported remote servers to verify reachability before paging on-call staff for an offline alert.

Other ways to use Uptime Ping Grounding Data

Set up Uptime Ping Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Networking:

Was this page helpful?