Email Finder API
REMOTE · EMAIL-FINDER.API.KLYMAX402.COM · SCANNED SEP 20
Find email addresses from name and company domain. x402 paid.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Email Finder API MCP server?
Email Finder API is a hosted endpoint at https://email-finder.api.klymax402.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · email-finder.api.klymax402.com
claude mcp add --transport http br0ski777-email-finder 'https://email-finder.api.klymax402.com/mcp'
{
"mcpServers": {
"br0ski777-email-finder": {
"url": "https://email-finder.api.klymax402.com/mcp"
}
}
} {
"servers": {
"br0ski777-email-finder": {
"type": "http",
"url": "https://email-finder.api.klymax402.com/mcp"
}
}
} [mcp_servers.br0ski777-email-finder] url = "https://email-finder.api.klymax402.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"br0ski777-email-finder": {
"type": "remote",
"url": "https://email-finder.api.klymax402.com/mcp",
"enabled": true
}
}
} openclaw mcp add br0ski777-email-finder --url 'https://email-finder.api.klymax402.com/mcp' --transport streamable-http
mcp_servers:
br0ski777-email-finder:
url: "https://email-finder.api.klymax402.com/mcp" {
"McpServers": {
"br0ski777-email-finder": {
"Transport": "http",
"Url": "https://email-finder.api.klymax402.com/mcp"
}
}
} assistant mcp add br0ski777-email-finder -t streamable-http -u 'https://email-finder.api.klymax402.com/mcp'
{
"mcpServers": {
"br0ski777-email-finder": {
"type": "http",
"url": "https://email-finder.api.klymax402.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 0
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Transport: Transport check failed: declared sse, but we couldn't connect to verify it. security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://email-finder.api.klymax402.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of email-finder.api.klymax402.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| klymax402.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://email-finder.api.klymax402.com/mcp | Unreachable | ||
| http (plaintext) | http://email-finder.api.klymax402.com/mcp | HTTPS enforced | 308 | https://email-finder.api.klymax402.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
No tool schema has been captured from this endpoint yet.
What is the Email Finder API MCP server?
Email Finder API is an MCP server listed in the public MCP registry as io.github.Br0ski777/email-finder. Find email addresses from name and company domain. x402 paid. This page covers its hosted endpoint (https://email-finder.api.klymax402.com/mcp).
Is the Email Finder API MCP server safe to use?
Email Finder API scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the Email Finder API MCP server require authentication?
Its publisher declares no required credentials for Email Finder API. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Email Finder API MCP server still maintained?
Email Finder API is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 17 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.