Archived listing / no verified MCP endpoint/Development

BurnerCheck listing

No MCP endpoint is published. This listing is retained for reference.

BurnerCheck was a list-based disposable email checker that flagged disposable, role, free-mail and look-alike addresses without MX lookups. The provider discontinued it in October 2026: its documentation and MCP endpoint both return HTTP 410 with a notice that the API and MCP server are no longer available. There is no replacement endpoint to configure, and this page is retained as a historical record only.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.
Source checked Nov 12, 2026 No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Readers who need to identify a retired email-validation service; it cannot be connected.

  • Confirm that a BurnerCheck integration should be removed.
  • Recognize the HTTP 410 discontinuation response.
  • Find the historical purpose of the service.

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.

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.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • 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.