Prometheus MCP Server
OCI · DOCKER.IO/PROM/PROMETHEUS-MCP
An API-complete MCP server to manage Prometheus-compatible backends.
Available components
Last scanned (7 hours ago)
Scores higher than 45% of OCI servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 4 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3250 tokens (~83/item across 39 items; 30 tools + 9 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety85
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "exemplar_query" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 32 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed oci/docker.io/prom/prometheus-mcp@v0.19.0-rc.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
alertmanagers ~18
Get overview of Prometheus Alertmanager discovery
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
build_info ~14
Get Prometheus build information
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
clean_tombstones ~44
Removes the deleted data from disk and cleans up the existing tombstones. I/O- and CPU-intensive; prefer low-traffic periods and confirm with the user before calling.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
config ~12
Get Prometheus configuration
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delete_series ~234
Deletes data for a selection of series in a time range. Both start_time and end_time are required to prevent accidental deletion of all data. Deletion creates tombstones; run clean_tombstones or wait for compaction to reclaim disk space. Confirm the time range and matchers with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | end timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to current t… |
| matches | array | yes | series selector arguments for series to delete,required |
| start_time | string | – | start timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to 5m ago. |
No output schema declared.
No examples provided.
docs_list ~16
List of Official Prometheus Documentation Files.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
docs_read ~40
Read the named markdown file containing official Prometheus documentation from the prometheus/docs repo
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | the name of the documentation file to read |
No output schema declared.
No examples provided.
docs_search ~52
Search the markdown files containing official Prometheus documentation from the prometheus/docs repo
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | maximum number of search results to return |
| query | string | yes | the query to search for in documentation |
No output schema declared.
No examples provided.
exemplar_query ~234
Execute an exemplar query against the Prometheus datasource to find trace exemplars associated with metric samples
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | end timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to current t… |
| query | string | yes | the PromQL query to execute |
| start_time | string | – | start timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to 5m ago. |
| truncation_limit | integer | – | truncation limit for query response in number of lines/entries; use lower limits (e.g. 50-100) for initial exploration, set to -1 to disable truncation |
No output schema declared.
No examples provided.
flags ~11
Get runtime flags
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
healthy ~20
Management API endpoint that can be used to check Prometheus health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
label_names ~235
Returns the unique label names present in the block in sorted order by given time range and matches
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | end timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to current t… |
| matches | array | – | series selector arguments to filter label names |
| start_time | string | – | start timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to 5m ago. |
| truncation_limit | integer | – | truncation limit for query response in number of lines/entries; use lower limits (e.g. 50-100) for initial exploration, set to -1 to disable truncation |
No output schema declared.
No examples provided.
label_values ~247
Performs a query for the values of the given label, time range and matches
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | end timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to current t… |
| label | string | yes | the label to query values for,required |
| matches | array | – | series selector arguments to filter label values |
| start_time | string | – | start timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to 5m ago. |
| truncation_limit | integer | – | truncation limit for query response in number of lines/entries; use lower limits (e.g. 50-100) for initial exploration, set to -1 to disable truncation |
No output schema declared.
No examples provided.
list_alerts ~14
List all active alerts
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_rules ~19
List all alerting and recording rules that are loaded
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_targets ~16
Get overview of Prometheus target discovery
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
metric_metadata ~50
Returns metadata about metrics currently scraped by the metric name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | maximum number of metrics to return |
| metric | string | – | metric name to retrieve metadata for, all metrics if empty |
No output schema declared.
No examples provided.
query ~160
Execute an instant query against the Prometheus datasource, returning one value per series at a single point in time
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | the PromQL query to execute |
| timestamp | string | – | evaluation timestamp for the instant query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now e.g. 5m, 1h30m, etc. Defaults… |
| truncation_limit | integer | – | truncation limit for query response in number of lines/entries; use lower limits (e.g. 50-100) for initial exploration, set to -1 to disable truncation |
No output schema declared.
No examples provided.
quit ~34
Management API endpoint that can be used to trigger a graceful shutdown of Prometheus. Only call this when the user explicitly requests a shutdown.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
range_query ~275
Execute a range query against the Prometheus datasource, returning values over a time window; use for graphing and trend analysis
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | end timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to current t… |
| query | string | yes | the PromQL query to execute |
| start_time | string | – | start timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to 5m ago. |
| step | string | – | query resolution step width in Go duration format (e.g. '30s', '5m', '1h'), auto-set if unspecified |
| truncation_limit | integer | – | truncation limit for query response in number of lines/entries; use lower limits (e.g. 50-100) for initial exploration, set to -1 to disable truncation |
No output schema declared.
No examples provided.
ready ~31
Management API endpoint that can be used to check Prometheus is ready to serve traffic (i.e. respond to queries.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reload ~34
Management API endpoint that can be used to trigger a reload of the Prometheus configuration and rule files. Safe; applies changes without downtime.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
runbooks_list ~100
List the runbooks embedded in this server: guided workflows (Agent Skills) for common Prometheus tasks - investigating error rates and alert spikes, finding top CPU/memory/disk consumers, troubleshooting missing metrics or empty query results, health-checking Prometheus, reducing high-cardinality metrics, reviewing and drafting recording and alerting rules, and tuning Prometheus configuration. Call this and read the matching runbook with runbooks_read before starting any of these tasks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
runbooks_read ~91
Read the named runbook: a guided workflow (Agent Skill) for a common Prometheus task, expressed in terms of this server's tools. Follow its guidance when a user request matches a runbook's purpose; runbooks_list shows what is available.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | the skill name of the runbook to read, as returned by runbooks_list (e.g. investigate-error-rates) |
No output schema declared.
No examples provided.
runtime_info ~14
Get Prometheus runtime information
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
series ~225
Finds series by label matches
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | end timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to current t… |
| matches | array | yes | series selector arguments that select the series to return,required |
| start_time | string | – | start timestamp for the query. Accepts: Unix epoch seconds, RFC3339, now, now-<duration>, now+<duration> (e.g. now-1h), or a duration string relative to now (e.g. 5m, 1h30m, etc). Defaults to 5m ago. |
| truncation_limit | integer | – | truncation limit for query response in number of lines/entries; use lower limits (e.g. 50-100) for initial exploration, set to -1 to disable truncation |
No output schema declared.
No examples provided.
snapshot ~61
creates a snapshot of all current data into snapshots/<datetime>-<rand> under the TSDB's data directory and returns the directory as response. Safe, but confirm with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| skip_head | boolean | – | skip data present in the head block |
No output schema declared.
No examples provided.
targets_metadata ~67
Returns metadata about metrics currently scraped by the target
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | maximum number of targets to match |
| match_target | string | – | label selectors to match targets, all targets if empty |
| metric | string | – | metric name to retrieve metadata for, all metrics if empty |
No output schema declared.
No examples provided.
tsdb_stats ~20
Get usage and cardinality statistics from the TSDB
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wal_replay_status ~16
Get current WAL replay status
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Prometheus MCP Server server?
Prometheus MCP Server runs locally as a container image, launched with docker run --rm -i docker.io/prom/prometheus-mcp:v0.19.0-rc.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · docker.io/prom/prometheus-mcp
claude mcp add prometheus-prometheus-mcp -- docker run --rm -i docker.io/prom/prometheus-mcp:v0.19.0-rc.0
What is the Prometheus MCP Server server?
Prometheus MCP Server is listed in the public MCP registry as io.github.prometheus/prometheus-mcp. An API-complete MCP server to manage Prometheus-compatible backends. This page covers its container image (docker.io/prom/prometheus-mcp).
Is the Prometheus MCP Server server safe to use?
Prometheus MCP Server scores 41 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Prometheus MCP Server server expose?
Prometheus MCP Server exposes 30 tools: alertmanagers, build_info, clean_tombstones, config, delete_series, and 25 more. Their descriptions and schemas cost roughly 2,404 tokens of context every time the server is loaded.
Is the Prometheus MCP Server server still maintained?
Prometheus MCP Server is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Prometheus MCP Server server?
VerifyMCP ran 12 checks on Prometheus MCP Server, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about Prometheus MCP Server: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.