MCP QUEEN
com.namingsignal/naming-signal C provisional — auth-gated, tooling unverifiable
Evidence-first naming: briefs, sprints, exact domain checks, finalist research. Read-only.
Cloud & Infrav0.2.0streamable-httpnamingsignal.com
Grade evidence — probed 2026-07-15 07:15 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 18 / 25 | HTTP 401 in 260ms — auth required; WWW-Authenticate present: "Bearer realm="NamingSignal", error="invalid_token", error_description="Create a NamingSignal API key at https://namingsi" |
| protocol | 0 / 15 | handshake not reachable behind auth — unverified |
| tooling | 0 / 0 | auth-gated — tooling unverifiable, excluded from score (grade marked provisional) |
| latency | 10 / 10 | initialize round-trip 260ms |
| provenance | 12 / 15 | description present; no repository URL; version 0.2.0; namespace com.namingsignal matches endpoint/repo |
Score 62/100 · latency 260ms · — tools · protocol access: auth-wellbehaved ⓘ
Trust receipt
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
No deterministic trust observations published yet. This means unaudited—not safe, unsafe, accurate, or inaccurate.
Machine-readable receipt: /api/trust/com.namingsignal/naming-signal.json
Own this server? Embed your grade badge
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:
[](https://mcpqueen.com/s/com.namingsignal/naming-signal)
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.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-15 07:15 | C | 62 | 260ms |