Mailcheck MCP integration for AI agents.
Connect AI agents to Mailcheck through 3 structured actions, including get status, validate domain, and verify email. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Mailcheck integration exposes
The Mailcheck Agent App exposes 3 provider-backed actions for communication and security work. Its current contract lets an authorized agent retrieve usercheck account information, plan details, and current api usage, validate a domain and return usercheck domain-level risk and mx signals, and validate a single email address and return usercheck deliverability and risk signals. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Mailcheck account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Mailcheck capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_statusREADRetrieve UserCheck account information, plan details, and current API usage.
validate_domainREVIEWValidate a domain and return UserCheck domain-level risk and MX signals.
INPUTS: domain
verify_emailREVIEWValidate a single email address and return UserCheck deliverability and risk signals.
INPUTS: email
INPUT CONTRACTS
Know what the action needs before it runs.
validate_domain
domainREQUIRED- The domain to validate with UserCheck.
verify_email
emailREQUIRED- The email address to validate with UserCheck.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Status
Retrieve UserCheck account information, plan details, and current API usage. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_statusVerify with Validate Domain
Validate a domain and return UserCheck domain-level risk and MX signals. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
validate_domainSAFETY BOUNDARY
Operate Mailcheck with explicit limits
- Authorize Mailcheck with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Mailcheck data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Mailcheck rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Mailcheck task completed successfully.
CONNECTION MODEL
API key
UserCheck API key used with the Authorization Bearer header. Generate it in the API Keys section of your dashboard: https://www.usercheck.com/docs/api/authentication.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Mailcheck.