Domain & IP Pinger Skill

What this skill does

Let your agent check if a host is up. Call it as an MCP tool to ping any domain or IP and get a live up/down result. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the Domain & IP Pinger Skill — exactly what your agent gets back when it makes the call.

vervekit · pingertool call

{
  "host": "google.com",
  "retries": 1
}

result

host: google.com
numericHost: 2607:f8b0:4001:c6e::8a
alive: true
roundTrips: 3
packetLoss: 0
minMS: 0.652
avgMS: 0.6846666666666666
maxMS: 0.712

+2 more fields

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

Host & IP lookups, no plumbing

Enable Domain & IP Pinger and your app can add domain & ip pinger to your app without standing up your own resolver or stitching together network APIs.

A tool agents call to check hosts

Over MCP, pinger is the tool your model reaches for to verify connectivity facts instead of assuming them.

One request, any language

Call Domain & IP Pinger over REST from any backend to add domain & ip pinger to your app inline, using the key you already have.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

pinger

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/pinger

Ask your agent

“Enable Domain & IP Pinger and ask your agent to add domain & ip pinger to your app.”
“Look up everything you can about this host.”

Domain & IP Pinger Skill, answered

How to connect it over MCP or REST.

How do I add Domain & IP Pinger to my app or agent?

Enable the Domain & IP Pinger Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the pinger tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to add domain & ip pinger to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Domain & IP Pinger appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Domain & IP Pinger call cost?

Each call costs 1 credit. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Domain & IP Pinger is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; Domain & IP Pinger is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Host & IP lookups, no plumbing

A tool agents call to check hosts

One request, any language

Domain & IP Pinger Skill, answered

Give your software a way to act on the world.

Scaling in production?