Security Intel MCP server
com.datakoot/cve-vulnerability-lookupdatakoot.comstreamable-httpv2.1.0Scanned
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
5 tools: 2 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 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.
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 Security Intel MCP server can do
The Security Intel MCP server is published by datakoot.com, a domain the MCP Registry verified. It has 5 tools. It can create or change data (2 tools: known_exploited and audit_dependencies), but cannot delete data. 3 tools only read.
5 tools bring in text other people can write (cve_lookup, known_exploited, epss_score and 2 more).
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 10, 2026, version 2.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.
5 tools
Changes things 2Claude Code: ask
audit_dependenciesAudit a whole dependency manifest for known vulnerabilities in one call.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Audit a whole dependency manifest for known vulnerabilities in one call. Paste a package.json (as 'manifest'), or pass a 'dependencies' array of {name, version} objects. Returns per-package findings and a summary. Ecosystem defaults to npm.
Annotations the server declares
- title: Audit Dependencies
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
known_exploitedCheck whether a CVE is on the CISA Known Exploited Vulnerabilities (KEV) catalog — confirmed exploited in the wild — or list the most recently added exploited vulnerabilities.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check whether a CVE is on the CISA Known Exploited Vulnerabilities (KEV) catalog — confirmed exploited in the wild — or list the most recently added exploited vulnerabilities. Pass cve_id to check one; omit it to list recent (optionally filter by vendor/product, or ransomware_only). Source: CISA KEV, updated ~daily.
Annotations the server declares
- title: Known Exploited
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 3Show 3 read-only tools
cve_lookupLook up a CVE by ID and get a compact summary: description, CVSS score & severity, vector, CWE weakness, publish date, references — plus whether it is on the CISA Known-Exploited l…Reads text others writeNo findings
Why it is in this group
- The name "cve_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Look up a CVE by ID and get a compact summary: description, CVSS score & severity, vector, CWE weakness, publish date, references — plus whether it is on the CISA Known-Exploited list (actively exploited in the wild) and its EPSS exploit-probability. Sources: NVD (NIST), CISA KEV, FIRST EPSS.
Annotations the server declares
- title: CVE Lookup
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
epss_scoreGet the EPSS exploit-probability score (0-1) and percentile for one or more CVEs — the likelihood each is exploited in the next 30 days.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Get the EPSS exploit-probability score (0-1) and percentile for one or more CVEs — the likelihood each is exploited in the next 30 days. Use it to prioritize patching. Pass cve_id for one, or cve_ids (array or comma-separated) for many. Source: FIRST.org EPSS.
Annotations the server declares
- title: EPSS Score
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
package_vulnerabilitiesList known vulnerabilities for a software package (optionally a specific version) via OSV.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "list": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it List known vulnerabilities for a software package (optionally a specific version) via OSV. Ecosystems: npm, pypi, cargo, go, maven, rubygems, nuget, composer, pub, hex.
Annotations the server declares
- title: Package Vulnerabilities
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
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 private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 20, 2026, 18:36 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
- 2
- Protocol version
- 2025-06-18
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://security.datakoot.com/mcp: tools/list returned 5 tools to an anonymous client, including known_exploited (write), audit_dependencies (write)
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 2.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http cve-vulnerability-lookup https://security.datakoot.com/mcpclaude mcp add --transport http cve-vulnerability-lookup https://security.datakoot.com/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__cve-vulnerability-lookup__cve_lookup",
"mcp__cve-vulnerability-lookup__epss_score",
"mcp__cve-vulnerability-lookup__package_vulnerabilities"
],
"ask": [
"mcp__cve-vulnerability-lookup__known_exploited",
"mcp__cve-vulnerability-lookup__audit_dependencies"
],
"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 cve-vulnerability-lookup. Review it before you use it.
Capability tags behind 5 rules
- mcp__cve-vulnerability-lookup__cve_lookup untrusted-input
- mcp__cve-vulnerability-lookup__known_exploited untrusted-input
- mcp__cve-vulnerability-lookup__epss_score untrusted-input
- mcp__cve-vulnerability-lookup__package_vulnerabilities untrusted-input
- mcp__cve-vulnerability-lookup__audit_dependencies untrusted-input
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/com.datakoot/cve-vulnerability-lookup/verify?hash=ade6421321c39a2bf44e005bea3237201e4329bf8a5b8cc5c5045089d202d6b9" | jq -e '.changed == false'Pinned hash ade6421321c3, from Nov 10, 2026, 14:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.datakoot/cve-vulnerability-lookup/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.datakoot/cve-vulnerability-lookup)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:53 UTC.
Security Intel MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Security Intel MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 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 Security Intel MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Security Intel 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 Security Intel MCP server have?
- 5 tools: 2 write, 3 read. known_exploited, audit_dependencies, cve_lookup, epss_score and package_vulnerabilities.
Does the Security Intel MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Security Intel MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Security Intel MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.