MCP QUEEN
io.github.megabrainee/sectora A
Threat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST.
Dev & Codev1.1.0streamable-httpmcp.sectora.io repository
Grade evidence — probed 2026-07-14 06:30 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 155ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-03-26, serverInfo sectora-mcp-server@1.0.0 |
| tooling | 35 / 35 | tools/list OK: 14 tools e.g. "lookup_cve"; 14/14 described, 14/14 fully-typed schemas, median description 163 chars |
| latency | 10 / 10 | initialize round-trip 155ms |
| provenance | 8 / 15 | description present; repository linked; version 1.1.0; namespace io.github.megabrainee does NOT match remote host (expected *.megabrainee.github.io) |
Score 93/100 · latency 155ms · 14 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http sectora https://mcp.sectora.io/mcp
Generic MCP client config:
{ "mcpServers": { "sectora": { "type": "http", "url": "https://mcp.sectora.io/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.megabrainee/sectora · referral link https://mcpqueen.com/go/io.github.megabrainee/sectora (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.megabrainee/sectora)
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-14 06:30 | A | 93 | 155ms |