Domain & IP Pinger Skill

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 Domain & IP Pinger Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as DomainIPPingerSkill. 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.

{
  "name": "DomainIPPingerSkill",
  "arguments": {
    "host": "google.com"
  }
}

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

Connecting

One server URL covers every skill 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": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

https://api.vervekit.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.

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

{
  "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.

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.

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 Domain & IP Pinger Skill

Set up Domain & IP Pinger Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Related

More in Networking: