io.github.rozetyp/vuln-intel
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
vuln-intel
Publisher-provided description
Free hosted CVE intel for bug-bounty agents: CVE fact-check, attack approaches from paid H1 reports
Summary by lookupd
Lets agents look up, fact-check, and prioritize CVEs, map recon'd stacks to vulnerabilities, and find bug-bounty attack approaches and…
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http vuln-intel https://mcp.rozetyp.com/mcp
Codex, remote (streamable-http)
codex mcp add vuln-intel --url https://mcp.rozetyp.com/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"vuln-intel": {
"url": "https://mcp.rozetyp.com/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (13 tools)
Publisher-provided text
enrich_cveFull intelligence for a single CVE: CVSS, KEV status, EPSS, CISA SSVC (exploitation/automatable/technical_impact), P1-P4 priority with rationale, affected producheck_technologyFind vulnerabilities affecting a product across NVD (CPE) and OSV (package ecosystems), de-duplicated and ranked by priority/EPSS/CVSS. Distinct products thathunt_planTurn a recon'd stack into a ranked dig-order for authorized bug-hunting. For each discovered component, returns its top high-risk CVEs (KEV / CISA-SSVC- activeobserveScan a host's exposed stack and join it to the CVE corpus — the recon workhorse. Fingerprints the homepage + JS bundles (recovering the backend identity and APIsearch_vulnsSearch the CVE corpus — one entry point, three retrieval modes picked from your arguments: - query= a concept / technique / weakness (e.g. "SSO SAML assertifind_attack_approachesFind how bugs *like this* were actually FOUND — retrieve real disclosed bug-bounty report mechanic-cards whose approach is closest (by mechanism) to your queryfind_continuationsWhen you're STUCK mid-hunt: describe your POSITION — the attacker state/capabilities you hold, stripped of product names — and get the CONTINUATIONS that workedassist_submissionSubmission & escalation co-pilot for a bug-bounty finding. Paste your DRAFT finding (and what you already tried / couldn't achieve) and get a grounded brief buiprogram_outcome_priorAt the START of an engagement on a bug-bounty PROGRAM, get a grounded prior over what bug classes have historically LANDED there — to decide what to look at firnew_in_scopeFind FRESH attack surface: bounty-eligible assets that entered a public bug-bounty program's scope in the last `days` (HackerOne, Bugcrowd, Intigriti, YesWeHackverify_cve_claimFact-check a claim about a CVE against the corpus — catch hallucinations before they ship. Verifies: does the CVE exist; does it affect the claimed product at tcorpus_statsCorpus size and data freshness (CVE / KEV / EPSS counts and latest timestamps).search_public_codeSearch public repositories for an exact code string; return WHERE it appears. Use it to hunt vendored / copy-pasted copies of known-vulnerable code: search a d
Details
- Version: 1.0.2
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 751 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/rozetyp/vuln-intel-mcp
- Website: https://vulntel.com
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.github.rozetyp/vuln-intel)
- 62092 servers
- Last crawl: 2026-11-11T17:17:22.074Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp