Skills/PyPI/sienge-ecbiesek-mcp

sienge-ecbiesek-mcp@3.1.3

VERIFIED· not started

Publisher claims: "🏗️ Model Context Protocol (MCP) server for Sienge API integration - Brazilian construction ERP system. Connect Claude AI to Sienge with 60+ powerful tools including smart validation, error parsing, complete invoice pipeline, and advanced caching for comprehensive business management." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher inotech-ecbiesek · publishing for 424 daysInstalls 153Last detonated 1 h ago
$claude mcp add sienge-ecbiesek-mcp -- uvx sienge-ecbiesek-mcp
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
DATABASE_URLPGPASSWORDRAILWAY_DATABASE_URLRAILWAY_PGPASSWORDSIENGE_API_KEYSIENGE_PASSWORDConfiguration, not credentials: KPI_CRON_INTERVAL_HOURS, KPI_CRON_SCHEDULE, PGDATABASE, PGHOST, PGPORT, PGUSER, POSTGRES_URL, RAILWAY_PGDATABASE, RAILWAY_PGHOST, RAILWAY_PGPORT, RAILWAY_PGUSER, RAILWAY_POSTGRES_URL, REQUEST_TIMEOUT, SIENGE_BASE_URL, SIENGE_SUBDOMAIN, SIENGE_USERNAME, SUPABASE_SERVICE_ROLE_KEY, SUPABASE_URL
Where it talks to
no vendor host named in the codeAlso sienge.com.br — not the publisher's domain; check what for before connecting.
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, and read the third-party hosts first. The code names sienge.com.br as well as its own vendor. The guard injects DATABASE_URL, PGPASSWORD, RAILWAY_DATABASE_URL, RAILWAY_PGPASSWORD, SIENGE_API_KEY, SIENGE_PASSWORD only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- uvx sienge-ecbiesek-mcp

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-18 and scored it 86/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
Access to sensitive file pathssrc/sienge_mcp/server.py:328 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"message": "Configure SIENGE_API_KEY ou SIENGE_USERNAME/PASSWORD no .env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/sienge_mcp/server.py:180 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"message": "Configure SIENGE_API_KEY ou SIENGE_USERNAME/PASSWORD no .env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/sienge_mcp/server.py:99 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"action": "Verifique SIENGE_API_KEY ou SIENGE_USERNAME/PASSWORD no arquivo .env.",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/sienge_mcp/server.py:573 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"message": "Configure SIENGE_API_KEY ou SIENGE_USERNAME/PASSWORD no .env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/sienge_mcp/tools/supabase_tools.py:22 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Configurações do Supabase (lidas do .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈111 tok
1 file · 29 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 sienge-ecbiesek-mcp@3.1.3 as of 53 min ago. This is the package itself, not its dependencies.