Skip to content
vulntel logo

vulntel MCP server

Which MCP servers are vulntel's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-11-03

← Back to vulntel

Whose server it is
  • Registry namecom.vulntel/mcpverified in the MCP registry

The registry name sits under vulntel.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-11-03
  • Stateanswerschecked 2026-11-03
  • Tools12
  • Server calls itselfvulntel
  • Server version1.30.0
  • Protocol version2025-06-18

On 2026-11-03 the server answered initialize and tools/list without a sign-in. First answer in 369 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: rank CVEs by exploitation likelihood and known exploitation status; fact-check CVE claims an AI agent might invent.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "rank CVEs by exploitation likelihood and known exploitation status", the likely first call is enrich_cve.
  • For "fact-check CVE claims an AI agent might invent", the likely first call is verify_cve_claim.
  • Parameters are untyped or undescribed in 12 of 13 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-11-03
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer283 ms
  • Space in an agent's context≈ 5,341 tokensthe definitions of all its tools (13), which an agent carries on every turn
  • Tool definitionsB · 85 of 100
  • Typed results0 of 13 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 12 of 13

What an agent can do with it

  • can do · rank CVEs by exploitation likelihood and known exploitation status
  • can do · fact-check CVE claims an AI agent might invent
  • not sure · check whether a server banner's backported fix is actually patched

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers12 tools · read 2026-11-03
  • enrich_cve

    Full intelligence for a single CVE: CVSS, KEV status, EPSS, CISA SSVC (exploitation/automatable/technical_impact), P1-P4 priority with rationale, affected products/versions, Debian/Ubuntu/Alpine fixed builds per release (`distro_fixes`)…

  • check_technology

    Find vulnerabilities affecting a product across NVD (CPE) and OSV (package ecosystems), de-duplicated and ranked by priority/EPSS/CVSS. Distinct products that share a name are kept distinct. If one name maps to several VENDORS' unrelated…

  • hunt_plan

    Turn 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- active / high-EPSS first) AND its `recurring_loci` — the bug classes (CWE) this…

  • observe

    Scan 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 API endpoints homepage detection misses on SPAs), then ranks against live KEV /…

  • search_vulns

    Search the CVE corpus — one entry point, three retrieval modes picked from your arguments: - query= a concept / technique / weakness (e.g. "SSO SAML assertion replay", "deserialization gadget chain", "server-side request forgery cloud…

  • find_attack_approaches

    Find how bugs *like this* were actually FOUND — retrieve real disclosed bug-bounty report mechanic-cards whose approach is closest (by mechanism) to your query or a seed CVE. The "what approach worked on a bug like this, on which program…

  • find_continuations

    When you're STUCK mid-hunt: describe your POSITION — the attacker state/capabilities you hold, stripped of product names — and get the CONTINUATIONS that worked from positions like it, matched against the full disclosed-report BODIES (the…

  • assist_submission

    Submission & 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 built from the closest REAL disclosed reports: (1) precedent & validity — is this…

  • program_outcome_prior

    At 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 first and what to skip. Built from real HackerOne disclosed reports: the class…

  • verify_cve_claim

    Fact-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 the claimed version; is the severity right; is it actually KEV-exploited…

  • corpus_stats

    Corpus size and data freshness (CVE / KEV / EPSS counts and latest timestamps).

  • search_public_code

    Search 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 distinctive line or symbol from the vulnerable function, then FETCH AND READ the…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "vulntel": {
      "type": "http",
      "url": "https://mcp.vulntel.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http vulntel https://mcp.vulntel.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.vulntel.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.