Website Contacts Scraper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrape_contacts_from_websiteA | Scrape emails, phone numbers, and social profile links from a website root domain. Supports batching of up to 20 domains in a single request. Note that by default, the emals returned by the endpoint are not restricted to match the website domain (after the \ |
| get_website_by_keywordC | Get company website URL by keyword / company name. Up to 20 keywords are supported in a single query. This endpoint can be used in case you only have a company name and need to get the website domain before scraping emails and contacts from it. |
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 2 tools
The two tools have clearly distinct purposes: one retrieves a website URL from a keyword, the other scrapes contacts from a given domain. No overlap or ambiguity.
Both tools follow a consistent verb_noun pattern using snake_case: get_website_by_keyword and scrape_contacts_from_website. Perfectly predictable.
With only two tools, the server is minimal but focused. For a website contacts scraper, this covers the core workflow. A few more tools (e.g., email verification) could enhance completeness, but the count is reasonable.
The tools cover the essential lifecycle: finding a website from a company name and then scraping contacts from it. There are no obvious gaps for the stated purpose of scraping emails, phones, and social profiles from root domains.