mcp-ambari-api@3.8.6
VERIFIED· not startedPublisher claims: "Model Context Protocol (MCP) server for Apache Ambari API integration. Provides comprehensive tools for managing Hadoop clusters including service operations, configuration management, status monitoring, and request tracking." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
REMOTE_AUTH_ENABLEREMOTE_SECRET_KEYConfiguration, not credentials: AMBARI_CLUSTER_NAME, AMBARI_HOST, AMBARI_METRICS_COLLECTOR_PORT, AMBARI_METRICS_HOST, AMBARI_METRICS_METADATA_TTL, AMBARI_METRICS_PORT, AMBARI_METRICS_PROTOCOL, AMBARI_METRICS_TIMEOUT, AMBARI_PASS, AMBARI_PORT, AMBARI_USER, FASTMCP_HOST, FASTMCP_PORT, FASTMCP_TYPE, GITHUB_REPOSITORY, MCP_LOG_LEVEL- 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 REMOTE_AUTH_ENABLE, REMOTE_SECRET_KEY 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.
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-11 and scored it 84/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 deviationsStatic findings
# Run with .env configFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx -y "$cli" pack "$stage" "$output_dir/mcp-ambari-api-$version.mcpb"Fix: Pin versions and sources; vendor anything fetched at install time.---Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.npx -y "$cli" validate "$stage/manifest.json"Fix: Pin versions and sources; vendor anything fetched at install time.All configuration is via environment variables (see `.env.example`). Key variables:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.npx -y @modelcontextprotocol/inspector \Fix: Pin versions and sources; vendor anything fetched at install time.npx -y @modelcontextprotocol/inspector \Fix: Pin versions and sources; vendor anything fetched at install time.- ./.env:/app/.env:roFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file: .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.source .env && PYTHONPATH=./src uv run python -m mcp_ambari_api --type ${FASTMCP_TYPE} --host ${FASTMCP_HOST} --port ${FASTMCP_PORT}Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file: .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file: .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "error: .env not found: $env_file" >&2Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.return subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Read and display all environment variables from .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.source .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "📄 Loading environment from .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# 어디서 실행하든지, 스크립트 위치의 상위 경로에 있는 .env 파일 export 로드Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load environment variables if .env existsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.if [ -f ".env" ]; thenFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env_file="${script_dir%/*}/.env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.echo "Starting OpenStack MCP server with environment variables from .env:"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.**NEVER REFUSE API CALLS** - When users ask for cluster information, alerts, services, etc., you MUST call the appropriate API tools to get real data.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
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 mcp-ambari-api@3.8.6 as of 3d ago. This is the package itself, not its dependencies.