kluno-verify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KLUNO_API_KEY | Yes | Your Kluno API key, from your dashboard at kluno.xyz. | |
| KLUNO_API_BASE | No | Overrides the API base URL (defaults to https://kluno.xyz). Only needed for local/staging testing against a non-production Kluno instance. | https://kluno.xyz |
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 |
|---|---|
| verify_emailA | Verify whether an email address is deliverable using Kluno. Returns an honest status (valid / invalid / catch-all / unknown) — Kluno never guesses a fake "valid" the way some verifiers do, so "unknown" is a real, meaningful answer (e.g. the mailbox sits behind a security gateway or the mail server would not give a clear answer). |
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, so there is no possibility of confusing it with another operation. Its purpose is clear and distinct.
The single tool name `verify_email` follows a clear verb_noun snake_case convention. No inconsistent naming exists to compare against.
A single-purpose email verification server can reasonably expose one focused tool. The count is minimal but not mismatched to the domain, though it offers no room for related operations like batch verification.
The tool covers the core verification operation and returns a rich status taxonomy including `valid`, `invalid`, `catch-all`, and `unknown`. Minor possible gaps such as bulk verification or historical results are not strictly required for the stated purpose.