Skip to main content
Glama

Server Details

Verify email addresses before you send: honest verdicts, no address kept, EU-hosted.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 21 tools

Disambiguation5/5

Each tool targets a distinct resource and action, and the potentially overlapping verification paths are explicitly bounded: verify_email vs. submit_batch, get_batch vs. get_batch_results, and get_verification vs. list_jobs each have clear separate purposes. The cross-references in descriptions make misselection unlikely.

Naming Consistency5/5

All tool names use snake_case with a predictable verb_noun pattern such as create_api_key, get_batch_results, list_webhooks, and revoke_api_key. The few multi-noun names like append_batch_emails remain readable and consistent with the same convention.

Tool Count4/5

At 21 tools, the surface is slightly larger than the ideal compact range, but the breadth is justified by several distinct functional areas: single and bulk verification, billing/usage, API keys, and webhooks. Each cluster appears to earn its tools, though the set is somewhat heavy.

Completeness5/5

The server covers the full verification lifecycle: single verification, batch submission/append/cancel, job and batch retrieval, results pagination, listing, billing, usage, API key lifecycle, and webhook CRUD. No obvious dead ends remain for the stated email-verification domain.

Publisher details

Operator
PricklyMails · Publisher source
Operator website
https://pricklymails.com
Vendor relationship
First-party · Publisher source
Privacy policy
Not provided
Trust center
Unknown
Restrictions
Free: 1,000 tokens, one API key, one agent. Paid plans from 8 EUR/month (10,000 tokens) up to 400 EUR/month; pay-as-you-go 1 EUR per 1,000 tokens from 4,000. A verification costs 7 to 10 tokens; the catch-all check requires Pro or above. · Publisher source

Available Tools

21 tools
append_batch_emailsAInspect

Append a chunk of emails (up to 4096) to a batch created by submit_batch with final set to false, so a list can grow past the single-call cap. Use it only for a batch whose intake is still open; to start a batch use submit_batch. It reserves and queues the chunk exactly like submit_batch and runs the check set the batch was submitted with: omit checks on every chunk (naming another set is refused with append_batch_emails.checks_mismatch). Set final to true on the last chunk (an empty emails list is allowed) to close intake; the batch then completes once every job finishes. A final chunk that would leave the batch under 20 distinct valid addresses is refused and the batch stays open. Requires the email:verify:bulk scope.

Inputs: emails (required), batch_uuid (required), final, checks, +1 more.

cancel_batchAInspect

Cancel a batch by batch_uuid when the user no longer wants it verified, for example a list submitted by mistake. Every address no worker has started is canceled and the tokens it reserved go back to the wallet at once; an address already being verified finishes and is billed as usual. The batch ends canceled and takes no more append_batch_emails chunks. Canceling a canceled batch changes nothing; a batch that already completed or failed cannot be canceled (cancel_batch.not_cancelable). Returns the batch as get_batch does, with tokens_billed and tokens_reserved after the refund. Requires the email:verify:bulk scope.

Inputs: batch_uuid (required).

check_balanceAInspect

Read the caller's token wallet balance (available, reserved, total, average daily spend), active plan code, and the checks that plan allows (for example whether smtp or catchall are available). Use it before a large submit_batch to confirm the balance and which checks the plan allows; for spending history use list_transactions, and for verification counts by verdict use get_usage. Requires the billing:read scope.

Inputs: no named parameters.

create_api_keyAInspect

Create a new PricklyMails API key under the caller's account and return its raw value once (field raw_key); store it right away, it is never shown again. Use it to give an integration or script its own credential; the tools in this server do not need one. environment picks live (default, real billing and real SMTP) or test (a deterministic sandbox: no SMTP, no wallet debit). scopes default to the project defaults and enabled_checks to every check the plan allows when omitted, and the new key may hold only scopes the caller's session holds itself, the defaults included. Use list_api_keys to see existing keys and revoke_api_key to disable one. Requires the api_keys:create scope.

Inputs: name (required), scopes, expires_at, environment, +1 more.

create_webhookAInspect

Create a webhook endpoint that receives job events such as job.completed and job.failed at an HTTPS URL. Use it to be notified instead of polling get_verification or get_batch. Returns the signing secret once (field secret); store it, it is never shown again. The number of active endpoints is capped by the plan. Use update_webhook to change an endpoint and list_webhooks to see them. Requires the webhooks:create scope.

Inputs: url (required), events (required), description.

delete_webhookAInspect

Delete a webhook endpoint by uuid, so it stops receiving events. Use it to remove an endpoint for good; to stop deliveries temporarily use update_webhook with status paused. Repeating the call on a deleted endpoint is safe. Requires the webhooks:delete scope.

Inputs: webhook_uuid (required).

get_batchAInspect

Fetch one batch's status, progress, and aggregated results by batch_uuid. Use it to check whether a batch has finished and how it is going; for the verdict of each address use get_batch_results, and to find a batch_uuid you lost use list_batches. Requires the results:read scope.

Inputs: batch_uuid (required).

get_batch_resultsAInspect

Fetch the per-email results of a batch (uuid, custom_id, status, score, verdict, recommendation and mailbox per row, mailbox saying whether the mail server confirmed the mailbox itself; custom_id echoes whatever was supplied at submit), paginated with limit (default 20, cap 96) and offset; total counts the matching rows across every page. Pass recommendation (send, review, remove) or verdict (valid, risky, invalid, unknown) to read only the rows to act on, for example the addresses to remove, instead of every page; a row still in progress matches neither. Pass status (pending, queued, processing, completed, failed, canceled) to find the rows that failed or are still waiting. Rows come in submission order unless sort (score, started_at) and order (desc, asc) say otherwise. Use it once get_batch shows the batch is done, or to page through results as they arrive; for the batch totals alone use get_batch. Requires the results:read scope.

Inputs: batch_uuid (required), sort, limit, order, +4 more.

get_pricingAInspect

Read the public plan grid, top-up pricing, and the per-check token costs. Use it before verifying to estimate what a verify_email or submit_batch call will cost and which plan unlocks a check; for the caller's own balance and plan use check_balance. Needs no scope and no credential.

Inputs: no named parameters.

get_usageAInspect

Read the caller's verification usage overview over the default window: verdict breakdown, per-check usage, totals, and only the non-zero days of the activity series. Use it to see how many verifications ran and with which verdicts; for the token balance use check_balance, and for individual token movements use list_transactions. Requires the usage:read scope.

Inputs: no named parameters.

get_verificationAInspect

Fetch a verification job and its results by job_uuid, without billing anything. Use it to poll a verify_email call that returned still processing, or to re-read an earlier result; to submit an address use verify_email, and for a batch use get_batch_results. Returns the job status and, once it is completed, the verdict, score, and checks. Requires the results:read scope.

Inputs: uuid (required).

get_webhookAInspect

Fetch a single webhook endpoint by uuid (url, events, status; never the signing secret). Use it when you already know the uuid; to discover endpoints use list_webhooks. Requires the webhooks:read scope.

Inputs: webhook_uuid (required).

list_api_keysAInspect

List the caller's API keys (uuid, name, active flag, scopes, enabled checks). Use it to find a key's uuid before revoke_api_key, or to audit what exists; it never returns a key's secret, which create_api_key shows only once. Requires the api_keys:read scope.

Inputs: no named parameters.

list_batchesAInspect

List the caller's bulk-verification batches, newest first, paginated with limit (default 20, cap 96) and offset, optionally narrowed by status, a part of the name (search) and a creation range (from, to), and sorted by created_at, name or total with order. Use it to find a batch_uuid or review recent bulk work; for single-address verifications use list_jobs instead, and for one batch's detail use get_batch. Requires the results:read scope.

Inputs: to, from, sort, limit, +4 more.

list_jobsAInspect

List the caller's standalone verification jobs (jobs that belong to a batch are excluded; read those with get_batch_results), newest first, paginated with limit (default 20, cap 96) and offset, optionally narrowed by status, verdict, a job_uuid prefix (search) and a creation range (from, to), and sorted by created_at or score with order. Use it to find a job_uuid or review recent single verifications; for bulk work use list_batches, and to read one job use get_verification. Requires the results:read scope.

Inputs: to, from, sort, limit, +5 more.

list_transactionsAInspect

List the caller's token wallet ledger transactions (type, amount, context, time, linked job), newest first, paginated with limit (default 20, cap 96) and offset, and sorted by occurred_at, amount or transaction_type with order. Use it to see where tokens went, one entry per movement; for the current balance use check_balance, and for aggregate verification counts use get_usage. Requires the billing:read scope.

Inputs: sort, limit, order, offset.

list_webhooksAInspect

List every webhook endpoint owned by the caller (uuid, url, events, status; never the signing secret). Use it to find an endpoint's uuid or to audit what receives events; for one endpoint use get_webhook. Requires the webhooks:read scope.

Inputs: no named parameters.

revoke_api_keyAInspect

Revoke one of the caller's API keys by uuid, so it stops authenticating at once. Use it to retire a leaked or unused key; find the uuid with list_api_keys. Repeating the call on an already revoked key returns the same result. Requires the api_keys:revoke scope.

Inputs: key_uuid (required).

submit_batchAInspect

Submit a list of emails (up to 4096 per call) for bulk verification and return a batch_uuid. Use it for 20 or more addresses; for fewer use verify_email, since a batch closed by this call needs at least 20 distinct valid addresses. Billed per unique valid address, and governed by the plan's batch_max (see get_pricing). The optional checks list picks which checks run (syntax, mx, smtp, disposable, role, free, catchall). Each check is billed at its own price, returned by get_pricing. Omitting checks runs every check your plan allows, which is the most reliable answer and costs the most tokens; naming fewer costs less. A check outside your plan is refused. Processing is asynchronous: follow progress with get_batch and read per-email results with get_batch_results. Set final to false to keep intake open and feed more chunks with append_batch_emails. Requires the email:verify:bulk scope.

Inputs: emails (required), final, checks, custom_ids.

update_webhookAInspect

Update a webhook endpoint's url, events, description, or status (active or paused). Use it to repoint an endpoint or to pause deliveries without deleting it; unset fields keep their current value. The signing secret does not change. To remove an endpoint use delete_webhook. Requires the webhooks:update scope.

Inputs: webhook_uuid (required), url, events, status, +1 more.

verify_emailAInspect

Verify one email address and return its verdict, score, and per-check results, waiting up to about 8 seconds for the job. Its mailbox field says whether the mail server confirmed the mailbox itself: a valid address at Microsoft or Yahoo, which are not asked, or at a catch-all domain, which accepts every address, is unconfirmed. Use it for a single address or a few; for 20 or more addresses use submit_batch, which is built for lists. If the job is still running it returns a job_uuid and a note: then call get_verification with that job_uuid instead of resubmitting. The optional checks list picks which checks run (syntax, mx, smtp, disposable, role, free, catchall). Each check is billed at its own price, returned by get_pricing. Omitting checks runs every check your plan allows, which is the most reliable answer and costs the most tokens; naming fewer costs less. A check outside your plan is refused. Requires the email:verify:single scope.

Inputs: email (required), checks, idempotency_key.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Verify email addresses in real time, without sending anything: a valid, risky, invalid or unknown status with a score, disposable, role-based and catch-all detection, and typo suggestions. Official local server of the MailProbe API, hosted in France.
      2
      64 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Real-time email verification API with syntax, MX, disposable detection, role-based flags, quality score 0-100. Built for agent outreach pipelines with pay-per-call via x402 (USDC on Base L2) -- no API key, no signup, no rate-limit wall.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to verify email addresses through a multi-signal probabilistic pipeline, returning confidence scores and honest statuses (safe/risky/invalid/unknown) with evidence.
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources