3 of its last 5 updates changed what the agent reads: 2 tool descriptions rewritten, up to 1.6.2.
PyPI package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability.PyPI page · Method and limits · this data as JSON.
Release by release
1.6.1 → 1.6.2
patch release, 3 August 2026
execute_query: title, annotations or output schema changed
execute_range_query: title, annotations or output schema changed
get_metric_metadata: title, annotations or output schema changed
get_targets: description and input schema changed; new arguments: limit, offset, scrape_pool, state
Before (1.6.1)
Get information about all scrape targets
After (1.6.2)
Get scrape targets, with state/pool filtering and optional pagination
health_check: title, annotations or output schema changed
list_metrics: title, annotations or output schema changed
1.6.0 → 1.6.1
patch release, 1 May 2026
execute_query: title, annotations or output schema changed
execute_range_query: title, annotations or output schema changed
get_metric_metadata: title, annotations or output schema changed
get_targets: title, annotations or output schema changed
health_check: title, annotations or output schema changed
list_metrics: title, annotations or output schema changed
1.5.3 → 1.6.0
minor release, 7 March 2026
get_metric_metadata: description and input schema changed; new arguments: filter_pattern, limit, offset
Before (1.5.3)
Get metadata for a specific metric
After (1.6.0)
Get metadata (type, help, unit) for metrics. Returns all metric metadata when no metric name is provided. Use filter_pattern to search metric names and descriptions.
list_metrics: input schema changed; new arguments: refresh_cache
The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.
Tools in 1.6.2
Tool
Description
Pin
health_check
Health check endpoint for container monitoring and status verification
757b9a14aad4
execute_query
Execute a PromQL instant query against Prometheus
e3839649fcf4
execute_range_query
Execute a PromQL range query with start time, end time, and step interval
9ec97ac3572d
list_metrics
List all available metrics in Prometheus with optional pagination support
8848b6c9a557
get_metric_metadata
Get metadata (type, help, unit) for metrics. Returns all metric metadata when no metric name is provided. Use filter_pattern to search metric names and descriptions.
9b9e9fa5486e
get_targets
Get scrape targets, with state/pool filtering and optional pagination
47d645eb8f99
Lock these tools
Pin what prometheus-mcp-server serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.
$ pip install verfy
$ verfy lock check --update # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout- uses: verfy-dev/verfy-action@v1
Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.