Skip to content

sectora MCP server

io.github.megabrainee/sectoramegabraineestreamable-httpv1.1.0Scanned

Threat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST.

14 tools: 3 change things and 11 only read.

Tools: 0 delete, 0 irreversible, 3 write, 11 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the sectora MCP server can do

The sectora MCP server is published by the GitHub account megabrainee. It has 14 tools. It can create or change data (3 tools: assess_tech_risk, scan_url and assess_dependency), but cannot delete data. 11 tools only read.

1 tool reads private data (get_threat_stats); 1 tool can send data out of your system (scan_url).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Changes things 3Claude Code: ask
  • assess_dependencyCheck a single package@version for known vulnerabilities via OSV.dev (npm, PyPI, Go, Maven, NuGet, RubyGems, Packagist, crates.io, etc.).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • assess_tech_riskAssess security risk for a list of technologies.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Assess security risk for a list of technologies. Returns known CVEs affecting each technology with severity breakdown. Input: comma-separated technology names only.
  • scan_urlKick off a DAST security scan against a public URL the API key owner controls.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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, plus the plan's monthly scan limit. Requires an API key with the scans:create scope.
Only reads 11Show 11 read-only tools
  • get_kev_recentGet recently added entries to the CISA Known Exploited Vulnerabilities (KEV) catalog.No findings

    Why it is in this group

    • The name "get_kev_recent" says "get": a word for reading.
    Description, as the server wrote it
    Get recently added entries to the CISA Known Exploited Vulnerabilities (KEV) catalog.
  • get_my_postureGet Shield WAF posture score and breakdown for a domain registered under this account.No findings

    Why it is in this group

    • The name "get_my_posture" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_scanGet a scan with all its findings (full detail: title, description, evidence, remediation, CVSS).No findings

    Why it is in this group

    • The name "get_scan" says "get": a word for reading.
    Description, as the server wrote it
    Get a scan with all its findings (full detail: title, description, evidence, remediation, CVSS). Requires API key.
  • get_threat_statsGet statistics about the Sectora threat intelligence database including counts of EPSS scores, KEV entries, Nuclei templates, and exploits.Reads private dataNo findings

    Why it is in this group

    • The name "get_threat_stats" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "database": it reads databases.
    Description, as the server wrote it
    Get statistics about the Sectora threat intelligence database including counts of EPSS scores, KEV entries, Nuclei templates, and exploits. No input required.
  • get_weaponization_scoreGet the weaponization score (0-100) for a CVE.No findings

    Why it is in this group

    • The name "get_weaponization_score" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_my_findingsList the API key owner's open security findings across all scans.No findings

    Why it is in this group

    • The name "list_my_findings" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • list_my_scansList the API key owner's recent scans with summary counts.No findings

    Why it is in this group

    • The name "list_my_scans" says "list": a word for reading.
    Description, as the server wrote it
    List the API key owner's recent scans with summary counts. Requires API key.
  • lookup_cveGet full threat intelligence enrichment for a CVE including EPSS score, CISA KEV status, public exploits, Nuclei templates, risk level, and risk factors.No findings

    Why it is in this group

    • The name "lookup_cve" says "lookup": a word for reading.
    Description, as the server wrote it
    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.
  • lookup_ip_reputationLook up community IP reputation from Sectora Shield WAF network.No findings

    Why it is in this group

    • The name "lookup_ip_reputation" says "lookup": a word for reading.
    Description, as the server wrote it
    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).
  • search_cvesSearch for CVEs by keyword, severity, or other filters.No findings

    Why it is in this group

    • The name "search_cves" says "search": a word for reading.
    Description, as the server wrote it
    Search for CVEs by keyword, severity, or other filters. Query must be alphanumeric text.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:08 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.sectora.io/mcp: tools/list returned 14 tools to an anonymous client, including assess_tech_risk (write), scan_url (write), assess_dependency (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http sectora https://mcp.sectora.io/mcp
claude mcp add --transport http sectora https://mcp.sectora.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__sectora__lookup_cve",
      "mcp__sectora__search_cves",
      "mcp__sectora__get_kev_recent",
      "mcp__sectora__get_trending_cves",
      "mcp__sectora__get_weaponization_score",
      "mcp__sectora__lookup_ip_reputation",
      "mcp__sectora__get_threat_stats",
      "mcp__sectora__list_my_findings",
      "mcp__sectora__list_my_scans",
      "mcp__sectora__get_scan",
      "mcp__sectora__get_my_posture"
    ],
    "ask": [
      "mcp__sectora__assess_tech_risk",
      "mcp__sectora__scan_url",
      "mcp__sectora__assess_dependency"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sectora. Review it before you use it.

Capability tags behind 2 rules
  • mcp__sectora__get_threat_stats private-data
  • mcp__sectora__scan_url outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.megabrainee/sectora/verify?hash=8107e70a5ef2bcebd0cfc05472f44c297a8d2e68d41295886acb252510fca587" | jq -e '.changed == false'

Pinned hash 8107e70a5ef2, from Nov 20, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.megabrainee/sectora/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.megabrainee/sectora
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.megabrainee/sectora.svg)](https://radar.anlyon.com/servers/io.github.megabrainee/sectora)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:40 UTC.

sectora MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the sectora MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the sectora MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the sectora MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the sectora MCP server have?

14 tools: 3 write, 11 read. assess_tech_risk, scan_url, assess_dependency, lookup_cve, search_cves, get_kev_recent, get_trending_cves, get_weaponization_score and 6 more.

Does the sectora MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the sectora MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): scan_url.

Has the sectora MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.