debounce-mcp.yml
DeBounce serves two Model Context Protocol endpoints from its own hosts. The developer-portal server is anonymous and answers tools/list live — its three tools are documentation-retrieval tools, not email-validation tools. The marketing-site server is a WordPress-hosted, OAuth-gated endpoint whose tool set could not be enumerated anonymously. Neither server exposes the validation, bulk, enrichment or account operations as MCP tools; an agent that needs to actually validate an email still calls the REST API directly.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Documentation
Documentation link · transport
Tools
search_de_bounce_api— Search across the DeBounce API knowledge base to find relevant information, code examples, API references, and guides. Returns contextual content with titles and direct links to the documentation pages.query_docs_filesystem_de_bounce_api— Run a read-only shell-like query (rg / tree / ls / head / cat) against a virtualized in-memory filesystem containing only the DeBounce API documentation pages and OpenAPI specs. Pages are read by passing their .mdx path to head or cat.submit_feedback— Report a problem with this documentation site so the docs team can fix it.
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.