B2B lead generation — prospect discovery, ICP scoring, outreach, and pipeline management.
Dev & Codev1.0.0streamable-httpse.phos.nz
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 643ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo Phos Sales Engine@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 4 tools e.g. "find_prospects"; 4/4 described, 4/4 fully-typed schemas, median description 155 chars |
| latency | 7 / 10 | initialize round-trip 643ms |
| provenance | 5 / 15 | description present; no repository URL; version 1.0.0; namespace io.github.albermm does NOT match remote host (expected *.albermm.github.io) |
Score 87/100 · latency 643ms · 4 tools · auth: open
Claude Code:
claude mcp add --transport http phos-sales-engine https://se.phos.nz/mcp/
Generic MCP client config:
{ "mcpServers": { "phos-sales-engine": { "type": "http", "url": "https://se.phos.nz/mcp/" } } }
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/io.github.albermm/phos-sales-engine · referral link https://mcpqueen.com/go/io.github.albermm/phos-sales-engine (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.albermm/phos-sales-engine)
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-13 21:02 | B | 87 | 643ms |