Disposable Phone Check Skill

What this skill does

Let your agent flag burner numbers. Call it as an MCP tool to check whether a phone is a known disposable or temporary number. 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 Disposable Phone Check Skill — exactly what your agent gets back when it makes the call.

vervekit · disposablephonetool call

{
  "phone": "+12085813945"
}

result

phone: +12085813945
isDisposable: true
firstSeen: 2024-01-30

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

Sign in to try

Ways to use it

Validate at the edge of your app

Enable Disposable Phone Check so your app can add disposable phone check to your app before it stores or acts on input — one skill, no separate validation service to run.

A guardrail tool for agents

Over MCP, your model can call disposablephone to check an input is real and safe before it takes an action, closing off a common failure mode.

One request from any stack

Call Disposable Phone Check over REST from any backend to add disposable phone check to your app inline in your pipeline, using the same key as every other skill.

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.

disposablephone

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/disposablephone

Ask your agent

“Enable Disposable Phone Check and ask your agent to add disposable phone check to your app.”
“Is this input real and safe to use?”

Disposable Phone Check Skill, answered

How to connect it over MCP or REST.

How do I add Disposable Phone Check to my app or agent?

Enable the Disposable Phone Check Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the disposablephone 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 disposable phone check 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 Disposable Phone Check appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Disposable Phone Check 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 Disposable Phone Check is available immediately.

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

VerveKit runs on APIVerve, our production data engine; Disposable Phone Check is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

More Data Validation skills

Browse all skills

Validate at the edge of your app

A guardrail tool for agents

One request from any stack

Disposable Phone Check Skill, answered

Give your software a way to act on the world.

Scaling in production?