Skip to main content
Glama
MCP Maintainer Tools

MCP Maintainer Tools

by No3214

MCP Vulnerability Research

MCP Maintainer Tools is the Python package and CLI behind this repository.

Investigate package advisories from your MCP client, with the sources in view.

Seven read-only Model Context Protocol tools connect your client to OSV, NVD, CISA KEV, FIRST EPSS, and deps.dev. Retrieve advisory records, inspect known-exploitation context and exploit-probability scores, and keep provider meanings separate.

Checks

Get started · Usage guide · Contribute · Security · Brand assets

A concrete research question

You have an exact public package version and want to inspect its advisories, then enrich any CVE aliases with NVD, KEV, and EPSS context. The server returns source context and explicit pagination over local stdio.

Question

Tools

Which advisories does OSV return for this package version?

osv_query, osv_batch, osv_vuln

What does NVD report, and is the CVE in the fetched KEV catalog?

nvd_cve, kev_check

What EPSS score and package metadata are available?

epss, depsdev_package

Start here: install and connect your client, then try the example research prompt. No API key is required; an optional NVD key is supported.

Results are available as both structured MCP objects and JSON text, with an object output schema for every tool.

This is an early public release. It supplies research inputs; release approval, remediation, and risk decisions remain with the maintainer. It does not inspect a local repository, install dependencies, or apply patches.

Existing scanners and MCP servers address overlapping workflows. The validation plan compares alternatives and defines a real-user pilot; external adoption and a measurable advantage have not yet been established.

Related MCP server: clearlydefined

Get started

You need Git, Python 3.11 or newer, an MCP client with stdio support, and HTTPS access to the providers. Install from this repository; a PyPI release is not provided by this project at present.

macOS or Linux

git clone https://github.com/No3214/mcp-vulnerability-research.git mcp-maintainer-tools
cd mcp-maintainer-tools
python3 -m venv .venv
./.venv/bin/python -m pip install .

Windows PowerShell

git clone https://github.com/No3214/mcp-vulnerability-research.git mcp-maintainer-tools
Set-Location mcp-maintainer-tools
py -3 -m venv .venv
.\.venv\Scripts\python.exe -m pip install .

Confirm that the chosen Python installation is 3.11 or newer. These commands call the environment's interpreter directly, so shell activation is unnecessary.

Connect your MCP client

Use the absolute path to the installed environment's Python executable. For a client that uses the common mcpServers configuration shape:

{
  "mcpServers": {
    "maintainer-tools": {
      "command": "/absolute/path/to/mcp-maintainer-tools/.venv/bin/python",
      "args": ["-m", "mcp_maintainer_tools"]
    }
  }
}

Replace the example path with your actual path. Windows uses .venv\Scripts\python.exe; escape backslashes in JSON. Ready-to-edit examples are available for macOS/Linux and Windows. Configuration formats vary by client.

The installed mcp-maintainer-tools command is also available. The minimal configuration works when this command is on the client's PATH.

The process speaks MCP, not an interactive shell. Your client starts it and exchanges protocol messages over stdin/stdout. Starting it directly may look idle because it is waiting for an MCP request. No HTTP listener is opened. Use python -m mcp_maintainer_tools --help or --version with the installed environment's interpreter to check the command without starting the server.

No API key is required. An optional NVD_API_KEY can be supplied through the server process environment or your client's secret settings. Keep the key out of repository files, example configurations, and diagnostic output.

By default, the transport ignores environment proxy and custom-CA settings. If your network requires them, explicitly set MCP_MAINTAINER_TOOLS_TRUST_ENV=true in the server environment and supply only trusted proxy/CA settings. TLS verification remains enabled. Restart the server after changing the setting; see network configuration for the accepted values and variables.

Seven tools, one research workflow

Tool

Input

What it returns

osv_query

Package name, version, optional ecosystem and page_token

One page of matching advisories, identifiers, and continuation metadata.

osv_batch

Up to 100 package objects

One page of advisory identifiers per package, with independent continuation tokens.

osv_vuln

vuln_id

The OSV record, retaining package-specific affected ranges and references, or explicit absence when OSV reports the ID as unknown.

nvd_cve

cve_id

The NVD CVE record, preserving attribution for its metrics, or explicit absence.

kev_check

Up to 100 cve_ids

Matches against a fetched CISA KEV catalog, with catalog metadata and the actual source used.

epss

Up to 100 cve_ids, optional offset and limit

A page of FIRST EPSS scores and continuation metadata.

depsdev_package

Package name, optional system

Package identity and metadata for the provider-marked default version, if identified.

OSV defaults to ecosystem npm; deps.dev defaults to system npm. Their ecosystem/system identifiers are not interchangeable. The usage guide describes arguments and limits.

Try a research question

After connecting the server, ask your MCP client:

Look up OSV records for lodash version 4.17.21 in the npm ecosystem. Retrieve every page. For any advisory with a CVE alias, use NVD, KEV, and EPSS for additional context. Preserve sources and unknowns; do not call the package safe merely because a lookup is empty.

This demonstrates a research workflow. It is not a current assessment or recommendation of the example package version. Individual OSV records can be retrieved with osv_vuln after the query or batch lookup.

Read the evidence correctly

Result

Interpretation

OSV has_more: true

Fetch the next page using next_page_token, even when the current page has no records.

EPSS has_more: true

Repeat the same CVE query with next_offset.

NVD found: false

This lookup did not return a CVE record. It is not a clean bill of health.

A CVE in not_in_kev

It was absent from the fetched KEV catalog. Check catalog date and source; this does not establish that it has never been exploited.

deps.dev default: null

The provider did not identify a default version. The tool does not choose one for you.

A failed tool call

The request or response could not be used. Do not replace the failure with an empty success.

Provider coverage and update timing differ. Upstream text and references are untrusted data, not instructions to an assistant or authorization to execute commands. The tools do not supply a complete inventory scan or a guarantee that software is secure.

kev_check tries CISA's canonical feed first. For specific availability failures, it can use CISA's official GitHub mirror. It reports source_url, canonical_source_url, and fallback_used so the source remains visible. The mirror may lag the canonical feed; retrieval time alone does not establish catalog freshness. Malformed, unsafe, or inconsistent data is rejected rather than hidden by a fallback. See the KEV source policy for the exact conditions.

Where your queries go

Calls make outbound HTTPS requests. A package name or version can reveal a dependency, including a private one. Query only information you are comfortable sending to the relevant provider.

Provider

Data sent

Official documentation

OSV — api.osv.dev

Package names, versions, ecosystems, continuation tokens, or advisory identifiers.

OSV API

NVD — services.nvd.nist.gov

CVE ID and the optional API key in a request header.

NVD vulnerability API

CISA KEV — www.cisa.gov; fallback hosted at raw.githubusercontent.com

Request for the full public catalog, first from CISA and, on eligible failures, from its official cisagov/kev-data mirror. Your CVE list is matched locally and is not sent to either host.

KEV catalog, official mirror

FIRST — api.first.org

CVE IDs and pagination parameters.

EPSS API

deps.dev — api.deps.dev

Package name and system; default version when identified.

deps.dev API v3

Development and project health

From a checkout, install the development dependencies and run the tests:

./.venv/bin/python -m pip install -e '.[dev]'
./.venv/bin/python -m pytest -q

On Windows, use .\.venv\Scripts\python.exe in place of ./.venv/bin/python. Tests use mocked provider responses, including a real MCP stdio client/server exchange; they do not require API keys. See CONTRIBUTING.md for change and testing guidance, and the CI workflow for the current validation matrix.

CI is configured for Python 3.11–3.14 on Ubuntu, plus Python 3.12 on Windows and macOS. Additional jobs check lint and formatting, Bandit security patterns, build and Twine package validation, CLI/stdio behavior using the built wheel, and known vulnerabilities in the resolved runtime dependencies. The workflow badge links to actual run results; configuration alone does not establish that a revision passed.

The Required checks job succeeds only when every prerequisite job succeeds. Job logs record the tested interpreter, resolved dependencies, commit, and package origin; package verification also records archive digests. See the 0.1.4 interoperability audit for the current change and measured results, the 0.1.3 protocol logging audit for logging boundaries, and the 0.1.2 dispatch audit for concurrency and verified repository protection.

The dev, audit, and build extras provide the corresponding local tools. The contribution guide lists the commands. The MCP SDK is constrained to the 1.30 series while its typed-input, protocol-version, and log/error adapters are reviewed against that series.

Report implementation vulnerabilities through SECURITY.md. Use GitHub issues for reproducible bugs, documentation improvements, and proposed changes to scope.

License and identity

Project code and original brand assets are available under the MIT License. Data returned by external services may have separate attribution and use terms. Provider names identify integrations and do not imply affiliation or endorsement.

The brand guide contains editable SVG assets, colors, typography, and claim boundaries for project communications.

Available Tools

7 tools
depsdev_packageC
Read-onlyIdempotent

Get deps.dev version metadata. Only a provider-marked default is used; no latest-version guess is made.

Inputs: name (required), system. Returns: object

epssA
Read-onlyIdempotent

Fetch one FIRST EPSS page for up to 100 CVEs. Scores estimate exploitation probability, not environment-specific risk.

Inputs: cve_ids (required), limit, offset. Returns: object

kev_checkA
Read-onlyIdempotent

Check up to 100 CVEs against a freshly fetched CISA KEV catalog. Absence is not proof of no exploitation.

Inputs: cve_ids (required). Returns: object

nvd_cveB
Read-onlyIdempotent

Get an NVD CVE, preserving metric-source attribution. Optional NVD_API_KEY is read from the environment.

Inputs: cve_id (required). Returns: object

osv_batchC
Read-onlyIdempotent

One OSV page per package: [{name, version, ecosystem?, page_token?}], at most 100. Follow each token separately.

Inputs: packages (required). Returns: object

osv_queryB
Read-onlyIdempotent

Fetch one OSV page for a package version. Repeat with next_page_token until has_more is false.

Inputs: name (required), version (required), ecosystem, page_token. Returns: object

osv_vulnA
Read-onlyIdempotent

Get an OSV record, retaining package-specific affected ranges, fixed events, and references.

Inputs: vuln_id (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct data source or operation: OSV package-page query, OSV record lookup, OSV batch query, NVD CVE lookup, CISA KEV check, EPSS scoring, and deps.dev package metadata. The OSV trio is the closest overlap, but their descriptions distinguish single-page query, record retrieval, and multi-package batching well enough.

    Naming Consistency3/5

    All names use snake_case, which is helpful, but the patterns are mixed: some are source-prefixed with an action or object (osv_query, osv_vuln, osv_batch, nvd_cve, kev_check, depsdev_package), while epss is just a bare acronym. The convention is readable but not consistently predictable across the set.

    Tool Count5/5

    Seven tools is well-scoped for a vulnerability and dependency-intelligence server, with each tool covering a meaningful source or operation. There is no obvious filler or excessive breadth.

    Completeness4/5

    The surface covers vulnerability lookup across OSV, NVD, KEV, and EPSS plus deps.dev package metadata, which supports common security-maintenance workflows. Minor gaps remain, such as higher-level dependency graph or package-version resolution support, but agents can work around them with existing tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      Unifies NVD, EPSS, CISA KEV, GitHub Advisory, and OSV into a single MCP server, enabling AI agents to query vulnerability intelligence conversationally with 23 tools for incident response, prioritization, dependency audits, and threat monitoring.
      41
      1,150 npm
      32
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching and retrieving curated open-source package license, copyright attribution, and provenance information, including detailed definitions and harvest scanner status, from the Linux Foundation's dataset via MCP tools.
      89 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes the code-and-dependency graph over MCP so clients can list and explain CVE findings from public endpoints, find supply-chain hubs, recommend and plan upgrades, verify a fix in a rebuilt scratch graph, and propose a draft fix PR. Queries are read-only and no tool executes an action.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Connects AI agents to structured vulnerability intelligence from NVD, EPSS, KEV, and OSV, enabling deterministic, policy-scored incident triage, CVE lookup, vulnerability search, and package scanning through auditable MCP tools.
      6
      1
      MIT