Remote MCP server: 19 domain-hygiene and email-auth tools (DNS, SPF, DMARC, DKIM, TLS).
Communicationv1.0.0streamable-httpwww.domainposture.com
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 509ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo domainposture.com@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 19 tools e.g. "ip_lookup"; 19/19 described, 19/19 fully-typed schemas, median description 531 chars |
| latency | 7 / 10 | initialize round-trip 509ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace com.domainposture matches endpoint/repo |
Score 94/100 · latency 509ms · 19 tools · auth: open
Claude Code:
claude mcp add --transport http mcp https://www.domainposture.com/mcp/mcp
Generic MCP client config:
{ "mcpServers": { "mcp": { "type": "http", "url": "https://www.domainposture.com/mcp/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/com.domainposture/mcp · referral link https://mcpqueen.com/go/com.domainposture/mcp (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.domainposture/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-13 01:00 | A | 94 | 509ms |