io.github.megabrainee/sectora
REMOTE · MCP.SECTORA.IO · SCANNED SEP 20
Threat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1197 tokens (~85/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.megabrainee/sectora MCP server?
io.github.megabrainee/sectora is a hosted endpoint at https://mcp.sectora.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.sectora.io
claude mcp add --transport http megabrainee-sectora 'https://mcp.sectora.io/mcp'
{
"mcpServers": {
"megabrainee-sectora": {
"url": "https://mcp.sectora.io/mcp"
}
}
} {
"servers": {
"megabrainee-sectora": {
"type": "http",
"url": "https://mcp.sectora.io/mcp"
}
}
} [mcp_servers.megabrainee-sectora] url = "https://mcp.sectora.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"megabrainee-sectora": {
"type": "remote",
"url": "https://mcp.sectora.io/mcp",
"enabled": true
}
}
} openclaw mcp add megabrainee-sectora --url 'https://mcp.sectora.io/mcp' --transport streamable-http
mcp_servers:
megabrainee-sectora:
url: "https://mcp.sectora.io/mcp" {
"McpServers": {
"megabrainee-sectora": {
"Transport": "http",
"Url": "https://mcp.sectora.io/mcp"
}
}
} assistant mcp add megabrainee-sectora -t streamable-http -u 'https://mcp.sectora.io/mcp'
{
"mcpServers": {
"megabrainee-sectora": {
"type": "http",
"url": "https://mcp.sectora.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.sectora.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sectora.io | CN=WE1,O=Google Trust Services,C=US | 3 Aug 2026 | 1 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ee3193b4ca5498ba136ebe800bee7261 |
| SANs: sectora.io, *.sectora.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.sectora.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| sectora.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.sectora.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.sectora.io/mcp | HTTPS enforced | 301 | https://mcp.sectora.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_dependency ~145
Check a single package@version for known vulnerabilities via OSV.dev (npm, PyPI, Go, Maven, NuGet, RubyGems, Packagist, crates.io, etc.). Returns advisories with CVE IDs, severity, fixed versions, and references. Free tier eligible.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem: npm, PyPI, Go, Maven, NuGet, RubyGems, Packagist, crates.io |
| name | string | yes | Package name (e.g., "lodash", "django", "github.com/gorilla/mux") |
| version | string | yes | Exact version (e.g., "4.17.20") |
No output schema declared.
No examples provided.
assess_tech_risk ~71
Assess security risk for a list of technologies. Returns known CVEs affecting each technology with severity breakdown. Input: comma-separated technology names only.
| Name | Type | Req | Description |
|---|---|---|---|
| technologies | string | yes | Comma-separated list of technology names (e.g., "Apache HTTP Server, OpenSSL, nginx"). Max 50 technologies. |
No output schema declared.
No examples provided.
get_kev_recent ~52
Get recently added entries to the CISA Known Exploited Vulnerabilities (KEV) catalog.
| Name | Type | Req | Description |
|---|---|---|---|
| days | string | – | Number of days to look back (1-365, default: 30) |
No output schema declared.
No examples provided.
get_my_posture ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain registered under your Sectora account |
No output schema declared.
No examples provided.
get_scan ~44
Get a scan with all its findings (full detail: title, description, evidence, remediation, CVSS). Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| scan_id | string | yes | Scan UUID |
No output schema declared.
No examples provided.
get_threat_stats ~42
Get statistics about the Sectora threat intelligence database including counts of EPSS scores, KEV entries, Nuclei templates, and exploits. No input required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trending_cves ~52
Get currently trending CVEs based on recent KEV additions, high EPSS scores, and exploit availability.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Maximum results to return (1-100, default: 20) |
No output schema declared.
No examples provided.
get_weaponization_score ~88
Get the weaponization score (0-100) for a CVE. Factors in EPSS, KEV status, exploit availability, Nuclei templates, and CVSS. Input must be a valid CVE ID.
| Name | Type | Req | Description |
|---|---|---|---|
| cve_id | string | yes | CVE identifier in format CVE-YYYY-NNNNN (e.g., CVE-2024-3400) |
No output schema declared.
No examples provided.
list_my_findings ~129
List the API key owner's open security findings across all scans. Use this to answer "what's my current exposure?" Filter by severity, status, or domain. Returns finding summaries; call get_scan for full detail. Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Limit to a single domain (e.g., app.example.com) |
| limit | string | – | Max findings (1-100, default: 25) |
| severity | string | – | Comma-separated severities to include: critical, high, medium, low, info |
| status | string | – | Filter by confirmation status |
No output schema declared.
No examples provided.
list_my_scans ~61
List the API key owner's recent scans with summary counts. Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Max scans (1-100, default: 25) |
| status | string | – | Filter by status (queued, running, completed, failed) |
No output schema declared.
No examples provided.
lookup_cve ~86
Get full threat intelligence enrichment for a CVE including EPSS score, CISA KEV status, public exploits, Nuclei templates, risk level, and risk factors. Input must be a valid CVE ID.
| Name | Type | Req | Description |
|---|---|---|---|
| cve_id | string | yes | CVE identifier in format CVE-YYYY-NNNNN (e.g., CVE-2024-3400) |
No output schema declared.
No examples provided.
lookup_ip_reputation ~89
Look up community IP reputation from Sectora Shield WAF network. Shows if an IP has been reported for attacks. Accepts IPv4 or IPv6 (the Shield network sees both).
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | yes | IPv4 (e.g., 1.2.3.4) or IPv6 (e.g., 2606:4700::1) address to look up |
No output schema declared.
No examples provided.
scan_url ~164
Kick off a DAST security scan against a public URL the API key owner controls. Two-step flow: first call returns a preview (target, profile, ETA, quota remaining); confirm by calling again with confirm:true to actually start the scan. Returns scan_id; poll status with get_scan. Domain must be verified in the Sectora account. Daily quota: 25 scans/24h per user. Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | string | – | Set to "true" to actually execute the scan. Without this, the call returns a preview only. |
| profile | string | – | Scan profile: quick (~2 min), standard (~10 min), deep (~30 min) |
| url | string | yes | Full URL to scan (must start with http:// or https://) |
No output schema declared.
No examples provided.
search_cves ~93
Search for CVEs by keyword, severity, or other filters. Query must be alphanumeric text.
| Name | Type | Req | Description |
|---|---|---|---|
| has_exploit | string | – | Only show CVEs with public exploits |
| is_kev | string | – | Only show CVEs in CISA KEV catalog |
| query | string | yes | Search keyword (CVE ID, technology name, or description) |
| severity | string | – | Filter by severity |
No output schema declared.
No examples provided.
What is the io.github.megabrainee/sectora MCP server?
io.github.megabrainee/sectora is an MCP server listed in the public MCP registry as io.github.megabrainee/sectora. Threat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST. This page covers its hosted endpoint (https://mcp.sectora.io/mcp).
Is the io.github.megabrainee/sectora MCP server safe to use?
io.github.megabrainee/sectora scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.megabrainee/sectora MCP server expose?
io.github.megabrainee/sectora exposes 14 tools: lookup_cve, assess_tech_risk, search_cves, get_kev_recent, get_trending_cves, and 9 more. Their descriptions and schemas cost roughly 1,197 tokens of context every time the server is loaded.
Does the io.github.megabrainee/sectora MCP server require authentication?
No. We connected to io.github.megabrainee/sectora without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.megabrainee/sectora MCP server still maintained?
io.github.megabrainee/sectora is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.