isitdisposable-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ISITDISPOSABLE_API_KEY | Yes | Your isitdisposable.com API key. Required for checking email/domain disposability. Get a free key at https://isitdisposable.com. |
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 |
|---|---|
| check_emailA | Checks a single email address to see whether it is disposable. A disposable address is a throwaway or temporary inbox (for example from a burner mail service) that someone uses to receive a single signup message and evade normal registration requirements, rather than a real, ongoing mailbox. In the response, |
| check_domainA | Checks a single bare domain (no local part, for example when only a company's domain is known and not a specific address) to see whether it is disposable. A disposable address is a throwaway or temporary inbox (for example from a burner mail service) that someone uses to receive a single signup message and evade normal registration requirements, rather than a real, ongoing mailbox. In the response, |
| check_batchA | Checks up to 100 email addresses or domains at once in a single call, which is far more efficient than calling the single-item tools in a loop. Provide a mixed list in |
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 3 tools
Each tool has a clearly distinct purpose: check_email handles full addresses, check_domain handles bare domains, and check_batch handles mixed lists. While check_batch overlaps in capability, the single vs. batch distinction is explicit and unambiguous.
All tool names follow the same check_ prefix followed by a noun (email, domain, batch), creating a predictable and consistent verb-noun pattern.
Three tools are well-scoped for this service: single email, single domain, and batch. This covers the core use cases without bloat or unnecessary additions.
The tool surface fully covers the domain of disposable address checking: individual emails, individual domains, and batch processing. No obvious missing operations for a read-only verification service.