mcp-registry/io.github.megabrainee/sectora · v1.0.0
As of 2026-10-22 00:07 UTC, the Megabrainee Sectora MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Threat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST.
Claude Code
claude mcp add --transport http megabrainee-sectora-mcp-server https://mcp.sectora.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"megabrainee-sectora-mcp-server": {
"type": "http",
"url": "https://mcp.sectora.io/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.megabrainee%2Fsectora/fixes
{
"name": "get_kev_recent",
"description": "Get recently added entries to the CISA Known Exploited Vulnerabilities (KEV) catalog.",
"inputSchema": {
"type": "object",
"properties": {
"days": {
"type": "string",
"pattern": "^\\d{1,3}$",
"maxLength": 3,
"description": "Number of days to look back (1-365, default: 30)"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_my_posture",
"description": "Get Shield WAF posture score and breakdown for a domain registered under this account. Returns 0-100 score, letter grade, per-component breakdown (origin lock, virtual patching, TLS, etc.), and edge_health (whether Shield is actually intercepting traffic). Requires API key.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"pattern": "^[a-z0-9.-]+$",
"maxLength": 253,
"description": "Domain registered under your Sectora account"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_scan",
"description": "Get a scan with all its findings (full detail: title, description, evidence, remediation, CVSS). Requires API key.",
"inputSchema": {
"type": "object",
"required": [
"scan_id"
],
"properties": {
"scan_id": {
"type": "string",
"pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$",
"maxLength": 36,
"description": "Scan UUID"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.megabrainee/sectora"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.megabrainee/sectora"}) over MCP.
scan_url ~269 tokenslist_my_findings ~216 tokensassess_dependency ~203 tokenssearch_cves ~174 tokensget_my_posture ~144 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.megabrainee%2Fsectora?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.megabrainee%2Fsectora?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.megabrainee%2Fsectora.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.megabrainee%2Fsectora.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.megabrainee%2Fsectora?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3d9aafc09baa5346…, first seen 2026-10-17, included at leaf 14892 of 42,329. Version history · verify what your client received.
Compare: most reliable security servers · most reliable search servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 00:07 UTC, the Megabrainee Sectora MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Megabrainee Sectora MCP server advertises 14 tools, including assess_dependency, assess_tech_risk, get_kev_recent, get_my_posture, get_scan.
Point your MCP client at this streamable-http endpoint: https://mcp.sectora.io/mcp
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.