mcp-company-contact-details-extractor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_company_contact_detailsA | Find a company's contact page from its domain and extract classified ROLE email addresses (general, support, sales, privacy), a main phone number in E.164 where the country resolves, and a postal address. Returns one flat Clay ready row. Named individuals are NEVER returned: an address is kept only when its domain belongs to the company and its local part is in the role vocabulary, so a person's address is dropped by an allow list rather than by a name detector. The row reports how many addresses were found and how many were rejected and why, so a thin result is never mistaken for a site that publishes nothing. Read only; requires an APIFY_TOKEN and consumes Apify credits per call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
There is only one tool on this server, so an agent cannot confuse it with anything else. Its purpose—extracting company contact details from a domain—is explicit and unique.
The single tool name follows a clear verb_noun pattern with snake_case: extract_company_contact_details. There are no mixed conventions or inconsistent verbs to create doubt.
One tool is below the typical 3-15 range, but this is a deliberate narrow extractor and the tool fully earns its place. The count is slightly under a fuller toolkit yet appropriate for the server's stated purpose.
The tool covers the full extraction workflow: finding the contact page, classifying role emails, normalizing the phone number, returning a postal address, and reporting rejected addresses. Because it is explicitly read-only, no CRUD lifecycle operations are expected, and there are no obvious dead ends.