Read-only by design.
The Precursor Intelligence MCP server is read-only. All 41 tools query intelligence and return data; none can write to your systems, modify your data, or trigger scans. Access uses a bearer API key that is scoped, IP-allowlisted, logged on every request and revocable at any time.
What the MCP can and cannot do
A useful way to reason about any agent tool is the blast radius. Here the radius is zero: the server can read intelligence, and nothing else.
It can
- Look up any CVE with EPSS, CVSS and CISA KEV status
- Return Shadowserver honeypot activity for a CVE or vendor
- Read MITRE ATT&CK techniques, threat actors and IOCs
- Return AI-generated remediation summaries that already exist
It cannot
- Write, edit or delete any of your data
- Trigger network or attack surface scans
- Reach into your code, repositories or infrastructure
- Change triage, watchlists or platform settings
The access model
Every connection runs over Streamable HTTP, authenticated with a key you control end to end.
Manage your keys
Mint, allowlist and revoke keys in the dashboard under Settings, then API Keys.
Try it with a free key
Read-only access, revocable in seconds. Connect your agent and see exactly what it can pull.
Security questions, answered
What the Precursor Intelligence MCP can and cannot do.
No. All 41 tools are read-only queries. The server returns intelligence such as CVE, EPSS, KEV and honeypot data. It has no tools that write, delete or change anything.
No. The MCP server does not scan. It cannot reach into your environment. Attack surface scanning exists in the platform dashboard as a separate, deliberate action and is not exposed through the MCP.
With a bearer API key you mint in the dashboard under Settings, then API Keys. It is passed in the Authorization header. There is no OAuth and no password exchange over the protocol.
Revoke it in the dashboard. Revocation takes effect within seconds. Since only a hash of the secret is stored, you mint a fresh key to restore access.
Yes. Keys have a default limit of 60 requests per minute. The limit, remaining count and reset window are returned with every response so a client can back off cleanly.