Meerkats.ai MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEERKATS_API_KEY | Yes | Your Meerkats.ai API key | |
| SCRAPPER_API_URL | No | API URL for scraping (default: https://api.meerkats.ai) | https://api.meerkats.ai |
| SCRAPPER_CALLBACK_API_URL | No | Callback API URL (default: https://api.meerkats.ai/callback) | https://api.meerkats.ai/callback |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| google_placesB | Get Google Maps Places API data for a search query |
| verify_emailA | Verify if an email address is valid and active using SMTP verification. |
| generate_support_emailsC | generate group of support email addresses are valid and active at a domain. Checks common group email patterns. |
| guess_emailB | Guess an email address based on name and domain using common email patterns. |
| check_domain_catch_allB | Check if a domain has a catch-all email address. |
| get_mx_for_domainC | get MX records for a domain. |
| scrape_urlA | Scrape a URL and return the content as markdown |
| web_searchC | Search on web and return the results |
| google_serpB | Get Google search results for a query with page limit |
| google_mapC | Get Google Maps data for a location query, optionally at specific coordinates |
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 10 tools
Several tools have overlapping purposes: google_places and google_map both return Google Maps data for location queries, and web_search and google_serp both provide search results. Additionally, guess_email and generate_support_emails overlap in guessing email patterns. This creates multiple ambiguous boundaries that an agent must navigate.
Tool names follow no consistent pattern: some start with verbs (verify_email, scrape_url), others with nouns (web_search, google_map), and some are mixed (generate_support_emails, check_domain_catch_all). There is no uniform verb_noun structure, making the naming style chaotic.
With 10 tools, the count is within the ideal range for a utility server. However, the presence of redundant or overlapping tools (e.g., google_places vs google_map) indicates a slight over-scoping, so it earns a 4 rather than a 5.
The email/domain verification tools cover verification, guessing, catch-all detection, and MX checks, while web tools cover search, scraping, and Google-specific queries. Minor gaps exist, such as missing reverse geocoding or additional domain checks, but core workflows are well covered.