SPF Validator Skill

What this skill does

Let your agent audit email SPF records. Call it as an MCP tool to validate a domain's SPF and test whether an IP is authorized to send. 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 SPF Validator Skill — exactly what your agent gets back when it makes the call.

vervekit · spfvalidatortool call

{
  "domain": "myspace.com",
  "ip": "192.0.2.1"
}

result

host: myspace.com
has_spf_record: true
dns_lookups_num: 9
spf_record: v=spf1 mx ip4:63.208.226.34 ip4:204.16.3…
spf_records_list: [ 9 items ]
domains_extracted: [ 9 items ]
authorized_ips: { … }
issues_found: [ 0 items ]

+8 more fields

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

Ways to use it

Domain intelligence in one skill

Enable SPF Validator so your app can validate spf — pull records, health, or ownership — without integrating a WHOIS/DNS provider per data type.

A tool for security & research agents

Over MCP, your model calls spfvalidator to ground a claim about a domain in real records before it reasons about risk.

Enrich from your backend

Call SPF Validator over REST to validate spf across a list of domains in a scheduled job, one key for all of it.

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.

spfvalidator

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

Ask your agent

“Enable SPF Validator and ask your agent to validate spf.”
“Pull the records and health for example.com.”

SPF Validator Skill, answered

How to connect it over MCP or REST.

How do I add SPF Validator to my app or agent?

Enable the SPF Validator Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the spfvalidator 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 validate spf — 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 SPF Validator appears as a standard tool with nothing skill-specific to integrate.

How many credits does a SPF Validator call cost?

Each call costs 5 credits. 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 SPF Validator is available immediately.

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

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

Domain intelligence in one skill

A tool for security & research agents

Enrich from your backend

SPF Validator Skill, answered

Give your software a way to act on the world.

Scaling in production?