mcp-registry/app.vercel.exploitwatch-kappa/exploitwatch · v1.0.0
As of 2026-10-23 01:26 UTC, the Vercel Exploitwatch Kappa Exploitwatch MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Check dependencies against CISA's real Known Exploited Vulnerabilities feed.
Claude Code
claude mcp add --transport http vercel-exploitwatch-kappa-exploitwatch-m https://exploitwatch-kappa.vercel.app/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"vercel-exploitwatch-kappa-exploitwatch-m": {
"type": "http",
"url": "https://exploitwatch-kappa.vercel.app/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.vercel.exploitwatch-kappa%2Fexploitwatch/fixes
{
"name": "check_kev",
"description": "Check a comma-separated list of software dependency/product names (e.g. 'lodash, openssl, apache struts') against CISA's real, public Known Exploited Vulnerabilities (KEV) catalog. Returns any current matches with the CVE ID, description, date added, and known ransomware use -- grounded in CISA's live feed, not a guess. Useful for triaging whether a project's dependencies include anything under active exploitation right now.",
"inputSchema": {
"type": "object",
"required": [
"dependencies"
],
"properties": {
"dependencies": {
"type": "string",
"description": "Comma-separated dependency/product names, e.g. 'express, lodash, openssl'"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.vercel.exploitwatch-kappa/exploitwatch"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.vercel.exploitwatch-kappa/exploitwatch"}) over MCP.
check_kev ~185 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.vercel.exploitwatch-kappa%2Fexploitwatch?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.vercel.exploitwatch-kappa%2Fexploitwatch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.exploitwatch-kappa%2Fexploitwatch.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.exploitwatch-kappa%2Fexploitwatch.svg :target: https://glimind.com/server/mcp-registry%2Fapp.vercel.exploitwatch-kappa%2Fexploitwatch?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ccb09dd91d376d82…, first seen 2026-10-17, included at leaf 10027 of 49,223. Version history · verify what your client received.
Compare: most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 01:26 UTC, the Vercel Exploitwatch Kappa Exploitwatch MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Vercel Exploitwatch Kappa Exploitwatch MCP server advertises 1 tool, including check_kev.
Point your MCP client at this streamable-http endpoint: https://exploitwatch-kappa.vercel.app/api/mcp
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.