MCP DOCS

Sectora Threat Intel MCP

Remote MCP server at https://mcp.sectora.io/mcp. JSON-RPC 2.0 over Streamable HTTP. Works with Claude Desktop, Cursor, Continue, Zed, and any MCP-compatible client.

1. Getting started

The free tier needs no signup — just point your client at the URL. For 10× higher rate limits and per-key usage analytics, create a key at Settings → API Keys.

Claude Desktop

Edit claude_desktop_config.json:

Copy

{
  "mcpServers": {
    "sectora": {
      "url": "https://mcp.sectora.io/mcp",
      "headers": { "X-API-Key": "sk_live_..." }
    }
  }
}

Cursor / Continue

Copy

mcpServers:
  sectora:
    url: https://mcp.sectora.io/mcp
    headers:
      X-API-Key: sk_live_...

Smithery (hosted)

Copy

smithery mcp add oversight/threat-intel

2. Authentication

Send your key in one of two headers (either works):

Copy

X-API-Key: sk_live_<40_hex>
Authorization: Bearer sk_live_<40_hex>

Never paste your key into chat or commit it to git. If a key is leaked, revoke it immediately from Settings → API Keys.

3. Tools

Eight tools are exposed. Your MCP client enumerates them via tools/list.

lookup_cve

cve_id

Full enrichment for a CVE — EPSS, KEV, exploits, Nuclei templates, risk level.

search_cves

query, severity?, is_kev?, has_exploit?

Keyword search across CVEs with filters.

get_weaponization_score

cve_id

Likelihood an attacker exploits this CVE in the next 30 days, scored 0–100.

lookup_ip_reputation

IP reputation — known scanner, malware host, TOR exit, recent abuse.

assess_tech_risk

technologies (csv, max 50)

CVEs affecting a tech stack, grouped by severity.

get_kev_recent

days (1–365)

Recent additions to the CISA KEV catalog.

get_trending_cves

limit (1–100)

CVEs with the most mentions in the last 30 days.

get_threat_stats

(none)

Aggregate stats: total CVEs, KEV count, last-sync times.

4. Rate limits

Enforced via a sliding 60-second window. Each response includes X-RateLimit-Remaining. When exceeded, HTTP 429 with Retry-After header.

Free

300 rpm / 10k/day

per IP

Pro

3,000 rpm / 100k/day

per API key

Enterprise

Custom

per key, negotiated

5. Errors

Responses follow JSON-RPC 2.0. Common error codes:

-32700 Parse error — invalid JSON

-32600 Invalid Request — missing jsonrpc/id/method

-32601 Method not found

-32602 Invalid params / validation failed

-32000 Server error / rate limit

-32001 Invalid or revoked API key

-32002 Missing required scope

-32003 Validation service unavailable

6. Privacy

We log the method, tool name, latency, status code, and a 12-char key prefix (never the full key). Logs are retained 30 days for debugging and abuse prevention, then deleted. See the privacy policy for details.