Prospector MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROSPECTOR_TIER | No | Your Prospector tier (free, pro, or business). Defaults to free if not set. |
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 |
|---|---|
| verify_emailA | Verify if an email address is valid and deliverable. Performs DNS MX lookup, SMTP handshake verification (without sending email), catch-all detection, and disposable domain detection. Returns a confidence score (0-100). |
| verify_emails_batchA | Verify multiple email addresses in a single batch (max 25). Returns verification status and confidence score for each email. Efficient for cleaning outreach lists. |
| find_emailsA | Find email addresses for a business. Scrapes their website for contact info, generates pattern-based candidates from a contact name, and verifies all discovered emails via SMTP. Returns verified emails sorted by confidence score. This is your Hunter.io replacement — no API key needed. |
| check_domainA | Quick check if a domain can receive email. Verifies DNS MX records exist and returns mail server details. Use this to filter out dead domains before running find_emails. Does not count against your verification quota. |
| usage_statsA | Check your current usage quota. Shows how many verifications you've used today, your remaining quota, and your tier. |
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 5 tools
Each tool targets a distinct step in the email verification/prospecting workflow: single verification, batch verification, business discovery, domain pre-check, and usage stats. Even though verify_email and verify_emails_batch are similar, they serve different scale needs and are clearly separated.
Most tools follow a verb_noun pattern (verify_email, find_emails, check_domain), but usage_stats breaks the pattern as a noun phrase, and verify_emails_batch awkwardly appends the modifier. Despite minor deviations, names remain readable and predictable.
With 5 tools, the server is well-scoped for email verification and discovery. Each tool earns its place, covering individual, batch, discovery, domain pre-check, and quota monitoring without unnecessary bloat.
The tool surface covers the full lead generation cycle: domain pre-check, single/batch verification, email discovery, and quota tracking. No obvious dead ends or missing core operations for the stated purpose.