Overview
Contact Extractor works by extracting contact data from a website URL using web scraping techniques. It returns the contact emails, phone numbers, and places found on the website.
Live Test Contact Extractor Skill Skill →
The tool
Once your client is connected to the VerveKit server, this appears in its tool list as ContactExtractorSkill. 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": "ContactExtractorSkill",
"arguments": {
"url": "https://en.wikipedia.org/wiki/Email_address"
}
}You do not name the tool yourself; the model picks it. Asking about https://en.wikipedia.org/wiki/Email_address in the terms this skill covers is enough for it to reach for ContactExtractorSkill 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/mcpPer-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.
| Argument | Type | Description |
|---|---|---|
urlRequired | string | The URL of the web page to extract contact data from url |
limitOptionalPremium | number | Limits the number of found contact details found on the page. Set -1 for unlimited default 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.
{
"status": "ok",
"error": null,
"data": {
"url": "https://en.wikipedia.org/wiki/Email_address",
"emails": [
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]",
"[email protected]"
],
"phones": [],
"places": [
"China",
"Japan",
"Russia",
"Rajasthan",
"India"
],
"emailCount": 27,
"phoneCount": 0,
"placeCount": 5,
"uniqueDomains": [
"example.com",
"example.org",
"s.example",
"EasierReading.org",
"pobox.com"
]
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
url | string | https://en.wikipedia.org/wiki/Email_address | The web page URL that was scraped, echoed back from the request |
emails | array | ["[email protected]","[email protected]","[email protected]"] | Unique email addresses found on the page, in order of appearance and capped at `limit` |
phones | array | [] | Unique phone numbers found on the page, in order of appearance and capped at `limit` |
places | array | ["China","Japan","Russia"] | Unique places or street addresses found on the page, in order of discovery and capped at `limit` |
emailCount | number | 27 | Number of email addresses included in the `emails` array |
phoneCount | number | 0 | Number of phone numbers included in the `phones` array |
placeCount | number | 5 | Number of places included in the `places` array |
uniqueDomainsPremium | array | ["example.com","example.org","s.example"] | Unique domains extracted from the returned `emails` (e.g., example.com, company.org) |
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.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This skill is not part of VerveKit. Check the catalog. |
429 | Out of credits, or a brief rate limit. The message tells them apart. |
A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.
Use cases
- Sales Prospecting Enrichment
- Sales reps scan company contact pages to extract direct support emails and phone numbers before launching targeted outbound calling campaigns.
- Local Directory Aggregation
- When curating regional merchant directories, indexing bots scrape storefront websites to verify physical street addresses and telephone lines.
- Vendor Onboarding Verification
- Before approving newly registered suppliers, procurement portals check listed corporate websites to confirm published business locations and operational telephone numbers.
- Talent Sourcing Workflows
- To build candidate pipelines, recruiting platforms scrape agency team pages to discover public email addresses for key department heads.
Other ways to use Contact Extractor Skill
Set up Contact Extractor 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 Data Scraping: