VEPmcp
Related Servers
Alternatives to VEPmcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API for vendors, products, vulnerabilities by vendor and product, specific CVE IDs, recent CVEs with CAPEC/CWE/CPE expansions, and database update information.-
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API for vendors, products, vulnerabilities by vendor and product, specific CVE IDs, recent CVEs with CAPEC/CWE/CPE expansions, and current database metadata.-
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to browse vendors and products, retrieve vulnerabilities by vendor/product or CVE ID, fetch the latest CVEs with CAPEC/CWE/CPE expansions, and inspect current database information.-
- FlicenseNot gradedqualityAmaintenanceEnables querying a CVE-Search API to browse vendors and products, retrieve vulnerabilities by vendor/product or CVE ID, and fetch recent CVEs with CAPEC, CWE, and CPE expansions plus database update details.-
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to retrieve vendors, vendor-associated products, vulnerabilities by vendor/product or CVE ID, recently updated CVEs with CAPEC/CWE/CPE expansions, and database metadata.-
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to browse vendors and products, retrieve vulnerabilities by vendor/product or CVE ID, list recent CVEs with CAPEC/CWE/CPE expansions, and inspect database update status.-
TDQS
Scored across 9 tools
Each tool targets a distinct action and input type. The three 'get_' tools retrieve metadata, while the six 'vep_' tools annotate variants and are clearly separated by input format (HGVS, ID, region) and batching mode. No two tools overlap in purpose.
Naming follows a consistent pattern: 'get_' for informational queries and 'vep_<format>_<mode>' for annotation tools. All names use snake_case and clearly convey the action and target resource, making the set predictable.
With nine tools, the server is well-scoped for its domain. The three metadata tools and six annotation tools (covering three input formats, each with batch and single variants) provide a complete set without excessive or insufficient endpoints.
The tool set covers core VEP functionality: metadata retrieval (assembly, consequences, species) and annotation via common input formats (HGVS, identifiers, regions) with both single and batch modes. No obvious gaps exist for a standard VEP annotation server.