Cisa Kev
Server Details
CISA KEV MCP.
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over 44 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-cisa-kev
- GitHub Stars
- 0
- Server Listing
- @pipeworx/cisa-kev
TDQS
Scored across 18 tools
Several tools overlap in purpose, e.g., `entity_profile`, `compare_entities`, `validate_claim`, and `ask_pipeworx` all handle company financial data. While detailed descriptions help, an agent could struggle to choose the optimal tool for a given query.
Names are inconsistent: some are verb phrases (`ask_pipeworx`, `bet_research`), some are nouns (`catalog`, `entry`), and others are compound phrases (`recent_changes`, `pipeworx_feedback`). No consistent convention is followed.
18 tools is a reasonable number for a data platform covering multiple domains (SEC, FDA, Polymarket, KEV). It is on the higher side but not excessive; each tool serves a specific purpose.
The tool set covers core workflows: company profiles, comparisons, fact-checking, betting analysis, and generic queries. Minor gaps exist (e.g., no direct tool for updating data), but the `ask_pipeworx` tool acts as a catch-all.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research1 field changed- added
Input schema / properties / include_rawAdded value: +{ + "description": "Default false. When false (recommended), FRED/FDA/GDELT/Federal-Register evidence is summarized to the few fields agents actually use — keeps responses under ~20KB. Pass true to get full upstream payloads (50KB-500KB) when you need to recompute deltas, cite specific observations, or post-process.", + "type": "boolean" +}
2 tool updates
- Changed
ai_visibility_check4 fields changed- added
Input schema / properties / _apiKeyAdded value: +{ + "description": "Optional Anthropic API key (sk-ant-...) — only needed if \"anthropic\" is in models. Passed straight through to api.anthropic.com.", + "type": "string" +} - changed
Input schema / properties / context / descriptionPrevious value: -"Optional: a phrase locating the entity (e.g. \"Boston restaurant\", \"B2B SaaS\", \"Polish painter\"). Helps disambiguate common names."New value: +"Optional: a phrase locating the entity (e.g. \"Boston restaurant\", \"B2B SaaS\"). Helps disambiguate common names." - changed
Input schema / properties / entity / descriptionPrevious value: -"The thing to ask about. Brand/business name, product name, person, or topic. E.g. \"Pipeworx\", \"OpenInvoice\", \"Acme Corp pricing\", \"the company behind ChatGPT\"."New value: +"The thing to ask about. Brand/business name, product name, person, or topic. E.g. \"Pipeworx\", \"OpenInvoice\", \"Acme Corp pricing\"." - added
Input schema / properties / modelsAdded value: +{ + "description": "Which models to probe. Supported: \"workers-ai\" (free default), \"anthropic\" (requires _apiKey). Omit for just workers-ai.", + "items": { + "type": "string" + }, + "type": "array" +}
- Added
scan_competitor_ai_presence
2 tool updates
- Added
ai_visibility_check - Added
generate_llms_txt
2 tool updates
- Added
pipeworx_trending - Added
polymarket_kalshi_spread
2 tool updates
- Changed
catalog2 fields changed- added
Input schema / examplesAdded value: +[ + {} +] - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "catalogVersion": { + "description": "Catalog version", + "type": "string" + }, + "count": { + "description": "Total vulnerability count", + "type": "number" + }, + "dateReleased": { + "description": "Release date", + "type": "string" + }, + "title": { + "description": "Catalog title", + "type": "string" + }, + "vulnerabilities": { + "description": "Array of known exploited vulnerabilities", + "items": { + "properties": { + "cveID": { + "description": "CVE identifier", + "type": "string" + }, + "cwes": { + "description": "Related CWE identifiers", + "items": { + "type": "string" + }, + "type": "array" + }, + "dateAdded": { + "description": "Date added to catalog (ISO format)", + "type": "string" + }, + "dueDate": { + "description": "Due date for remediation", + "type": "string" + }, + "knownRansomwareCampaignUse": { + "description": "Known ransomware campaign use", + "type": "string" + }, + "notes": { + "description": "Additional notes", + "type": "string" + }, + "product": { + "description": "Product name", + "type": "string" + }, + "requiredAction": { + "description": "Recommended action", + "type": "string" + }, + "shortDescription": { + "description": "Brief vulnerability description", + "type": "string" + }, + "vendorProject": { + "description": "Vendor or project name", + "type": "string" + }, + "vulnerabilityName": { + "description": "Vulnerability name", + "type": "string" + } + }, + "required": [ + "cveID", + "vendorProject", + "product", + "vulnerabilityName", + "dateAdded", + "shortDescription", + "requiredAction", + "dueDate" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "vulnerabilities" + ], + "type": "object" +}
- Changed
vendors2 fields changed- added
Input schema / examplesAdded value: +[ + {} +] - changed
Output schema / (root)Previous value: -nullNew value: +{ + "properties": { + "total_vendors": { + "description": "Total number of distinct vendors", + "type": "number" + }, + "vendors": { + "description": "Vendors sorted by entry count (descending)", + "items": { + "properties": { + "count": { + "description": "Number of entries for this vendor", + "type": "number" + }, + "vendor": { + "description": "Vendor name", + "type": "string" + } + }, + "required": [ + "vendor", + "count" + ], + "type": "object" + }, + "type": "array" + } + }, + "required": [ + "total_vendors", + "vendors" + ], + "type": "object" +}
18 tool updates
- First observed
ask_pipeworx - First observed
bet_research - First observed
catalog - First observed
compare_entities - First observed
discover_tools - First observed
entity_profile - First observed
entry - First observed
forget - First observed
pipeworx_feedback - First observed
polymarket_arbitrage - First observed
polymarket_edges - First observed
recall - First observed
recent - First observed
recent_changes - First observed
remember - First observed
resolve_entity - First observed
validate_claim - First observed
vendors
Related MCP Connectors
Moldova Government Procurement (MTender) MCP — keyless.
UK Health Security Agency (UKHSA) data dashboard MCP — keyless.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server for ECDSA cryptography enabling key generation, signing, and verification.11MIT
- MIT
- MIT
- Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.