Non functional server (yet)
Web & Searchv0.0.14streamable-httpsub1.find-me.casa
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 3456ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo Resend Email@1.16.0 |
| tooling | 35 / 35 | tools/list OK: 1 tools e.g. "send_email"; 1/1 described, 1/1 fully-typed schemas, median description 385 chars |
| latency | 1 / 10 | initialize round-trip 3456ms |
| provenance | 10 / 15 | description present; no repository URL; version 0.0.14; namespace casa.find-me.sub1 matches endpoint/repo |
Score 86/100 · latency 3456ms · 1 tools · auth: open
Claude Code:
claude mcp add --transport http send-email-mcp https://sub1.find-me.casa
Generic MCP client config:
{ "mcpServers": { "send-email-mcp": { "type": "http", "url": "https://sub1.find-me.casa" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/casa.find-me.sub1/send-email-mcp · referral link https://mcpqueen.com/go/casa.find-me.sub1/send-email-mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/casa.find-me.sub1/send-email-mcp)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 21:01 | B | 86 | 3456ms |