INDIVIDUAL MCP TOOL
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.
LIVE ENDPOINT
https://mcp.rozetyp.com/mcp
Connect to this endpoint to inspect the live schema for program_outcome_prior and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vulntel]
url = "https://mcp.rozetyp.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vulntel": {
"type": "http",
"url": "https://mcp.rozetyp.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vulntel
Remote MCP URL: https://mcp.rozetyp.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vulntel": {
"url": "https://mcp.rozetyp.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vulntel": {
"type": "http",
"url": "https://mcp.rozetyp.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vulntel",
"transport": "streamable-http",
"url": "https://mcp.rozetyp.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
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`), and (live) public-exploit signal.check_technology— Find vulnerabilities affecting a product across NVD (CPE) and OSV (package ecosystems), de-duplicated and ranked by priority/EPSS/CVSS.hunt_plan— Turn a recon'd stack into a ranked dig-order for authorized bug-hunting.observe— Scan a host's exposed stack and join it to the CVE corpus — the recon workhorse.search_vulns— Search the CVE corpus — one entry point, three retrieval modes picked from your arguments: - query= a concept / technique / weakness (e.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.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 concrete step/payload/precondition), not just the distilled card.assist_submission— Submission & escalation co-pilot for a bug-bounty finding.