Skills/PyPI/mseep-prometheus-mcp-server

mseep-prometheus-mcp-server@1.2.9

VERIFIED· not started

Publisher claims: "MCP server for Prometheus integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher mseep-support · publishing for 578 daysInstalls 21Last detonated 46 h ago
$claude mcp add mseep-prometheus-mcp-server -- uvx mseep-prometheus-mcp-server
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
PROMETHEUS_PASSWORDPROMETHEUS_TOKENConfiguration, not credentials: ORG_ID, PROMETHEUS_MCP_BIND_HOST, PROMETHEUS_MCP_BIND_PORT, PROMETHEUS_MCP_SERVER_TRANSPORT, PROMETHEUS_URL, PROMETHEUS_USERNAME
Where it talks to
no vendor host named in the code
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for PROMETHEUS_PASSWORD, PROMETHEUS_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- uvx mseep-prometheus-mcp-server

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-12 and scored it 81/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Collapsed <details> block carrying instructionsREADME.md:79 · Collapsed <details> block carrying instructions<summary><b>VS Code / Cursor / Windsurf</b></summary> Add to your MCP settings in the respective IDE: ```json { "prometheus": { "command": "docker", "args": [ "Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Collapsed <details> block carrying instructionsREADME.md:42 · Collapsed <details> block carrying instructions<summary><b>Claude Desktop</b></summary> Add to your Claude Desktop configuration: ```json { "mcpServers": { "prometheus": { "command": "docker", "args": [ "runFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathssrc/prometheus_mcp_server/main.py:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslogger.info("Environment configuration loaded", source=".env file")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Collapsed <details> block carrying instructionsREADME.md:121 · Collapsed <details> block carrying instructions<summary><b>Manual Docker Setup</b></summary> Run directly with Docker: ```bash # With environment variables docker run -i --rm \ -e PROMETHEUS_URL="http://yourFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Access to sensitive file pathssrc/prometheus_mcp_server/main.py:14 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system fileslogger.info("Environment configuration loaded", source="environment variables", note="No .env file found")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Collapsed <details> block carrying instructionsREADME.md:69 · Collapsed <details> block carrying instructions<summary><b>Claude Code</b></summary> Install via the Claude Code CLI: ```bash claude mcp add prometheus --env PROMETHEUS_URL=http://your-prometheus:9090 -- docFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
HIGH
Collapsed <details> block carrying instructionsREADME.md:104 · Collapsed <details> block carrying instructions<summary><b>Docker Desktop</b></summary> The easiest way to run the Prometheus MCP server is through Docker Desktop: <a href="https://hub.docker.com/open-desktoFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_main.py:126 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_server_transport="http",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_main.py:162 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_server_transport="http",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_main.py:89 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_server_transport="HTTP",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_main.py:69 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_server_transport="http",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_main.py:116 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_server_transport="http",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_docker_integration.py:326 · MCP server using network transport (SSE/HTTP) — data sent over network'PROMETHEUS_MCP_SERVER_TRANSPORT': 'http',Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_docker_integration.py:392 · MCP server using network transport (SSE/HTTP) — data sent over network'PROMETHEUS_MCP_SERVER_TRANSPORT': 'http'Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_docker_integration.py:258 · MCP server using network transport (SSE/HTTP) — data sent over network'PROMETHEUS_MCP_SERVER_TRANSPORT': 'http',Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_docker_integration.py:180 · MCP server using network transport (SSE/HTTP) — data sent over network'PROMETHEUS_MCP_SERVER_TRANSPORT': 'http',Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_docker_integration.py:361 · MCP server using network transport (SSE/HTTP) — data sent over network'PROMETHEUS_MCP_SERVER_TRANSPORT': 'http'Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_mcp_protocol_compliance.py:369 · MCP server using network transport (SSE/HTTP) — data sent over networkassert mcp_config.mcp_server_transport == "http"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04
MEDIUM
MCP server using network transport (SSE/HTTP)tests/test_mcp_protocol_compliance.py:365 · MCP server using network transport (SSE/HTTP) — data sent over networkmcp_server_transport="http",Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

Cost to the agent

Instructions loaded
≈53 tok
1 file · 22 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for mseep-prometheus-mcp-server@1.2.9 as of 45 h ago. This is the package itself, not its dependencies.