Oxiploitability runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 23 Oct 2026.
Sourced, evidence-aware CVE research for CVEs, products, SBOMs and images via NVD, EPSS, KEV, OSV.
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
result = subprocess.run([os.path.abspath(sys.argv[1])], input=messages, text=True, capture_output=True, cwd=directory, env=env, timeout=15, check=False)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Oxiploitability
same job, measured the same wayRead-only vulnerability intelligence: CVEs, exploitation evidence, fixes and product matches.
Agent accountability for product teams: specs, evidence, and ship readiness over MCP.
Agent research API for 15 disease areas, plus a T1D cure lab, sourced evidence ledger and models.
CVE & vulnerability search: 365k+ CVEs/NotCVEs, CVSS, EPSS, CISA KEV, exploits, patches, versions.
CISA KEV status and EPSS scores for CVE IDs, ranked P1/P2/P3 for patching, via Apify.
Source-traced evidence research for AI agents. We organise the evidence; you decide.
Confirmed vulnerabilities and exposure for IPs, domains and software versions (NVD, CISA KEV, EPSS)
Sourced public knowledge for AI agents: search and read records with evidence; moderated writes.
Oxiploitability — questions
Answers built from our own checks of this server.