Hosted MCP server/Cloud Service

InboxGuards Email Check MCP server

Hosted at api.inboxguardstest.com·Streamable HTTP

InboxGuards Email Check checks an email address before you send: validate_email runs a free offline syntax check, check_email_address adds MX and null-MX, disposable and role-inbox checks, and email_fix_plan returns the SPF, DKIM, and DMARC records to publish. A free pricing tool returns the per-call price. This is a different product from InboxGuard by IronVest and from the business-email-compromise monitoring sold on inboxguards.com. The MCP endpoint currently runs on the provider's test host, api.inboxguardstest.com; treat it as a test environment.

api.inboxguardstest.com Streamable HTTP No authentication Server not checked yet Reviewed 2026-11-16
About

Where it fits

Senders and developers who want email-address validation and deliverability fixes, not mailbox security monitoring.

  • Run the free validate_email syntax check.
  • Check an address for MX, disposable, and role-inbox issues.
  • Get SPF, DKIM, and DMARC records with email_fix_plan.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds InboxGuards Email Check as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http inboxguards-email-check https://api.inboxguardstest.com/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://api.inboxguardstest.com/mcp
Host
api.inboxguardstest.com · /mcp
Transport
Streamable HTTP
Authentication
No authentication
Server name
inboxguards-email-check
Listing type
Community or directory listing

The installer uses the server name inboxguards-email-check. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that inboxguards-email-check appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Run the free validate_email syntax check. Check the result before you give the server more access.

  3. 3
    Check permissions.

    The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.