Skills/PyPI/treasy-mcp

treasy-mcp@0.5.0rc1

VERIFIED· not started

Publisher claims: "Servidor MCP do Treasy: o seu Treasy FP&A dentro do Claude Code, com login pelo navegador" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher treasy · publishing for 16 daysInstalls 264Last detonated 1 h ago
$claude mcp add treasy-mcp -- uvx treasy-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
TREASY_CLIENT_SECRETTREASY_CLIENT_SECRET_QATREASY_CLIENT_SECRET_SANDBOXConfiguration, not credentials: MCP_HOST, MCP_HTTP_PATH, MCP_PORT, MCP_TRANSPORT, TREASY_AMBIENTE, TREASY_API_BASE_URL_LOCAL, TREASY_API_BASE_URL_PROD, TREASY_API_BASE_URL_QA, TREASY_API_BASE_URL_SANDBOX, TREASY_CREDENCIAIS_FILE, TREASY_ENV_FILE, TREASY_ENVIO_DIR, TREASY_EXPORTACAO_DIR, TREASY_GATEWAY_USAGE_LOG, TREASY_GATEWAY_WRITES, TREASY_MCP_MODO, TREASY_SSO_URL_SANDBOX, TREASY_XXX_LITE_MODO, TREASY_XXX_LITE_USUARIO_MAIL
Where it talks to
treasy.com.br (its own)
What we saw when it ran
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 TREASY_CLIENT_SECRET, TREASY_CLIENT_SECRET_QA, TREASY_CLIENT_SECRET_SANDBOX and talks to treasy.com.br. 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 --secrets TREASY_CLIENT_SECRET=treasy.com.br,TREASY_CLIENT_SECRET_QA=treasy.com.br,TREASY_CLIENT_SECRET_SANDBOX=treasy.com.br -- uvx treasy-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-20 and scored it 82/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 pathstreasy_mcp/sessao_auth.py:280 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesf"preencha {chave} no .env do Treasy MCP (ou aponte TREASY_ENV_FILE para ele)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Hidden zero-width characters detectedtreasy_mcp/login_navegador.py:787 · Hidden zero-width characters detected — may conceal contentif not any(padrao.match(linha.lstrip("")) for linha in linhas):Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.
AST07
HIGH
Access to sensitive file pathstreasy_mcp/modo.py:210 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# ── Segredos do client ambassador (.env do repositório) ─────────────────────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 pathstreasy_mcp/modo.py:44 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Chaves que o leitor do .env do repositório aceita: só as TREASY_* que o config.py usaFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathstreasy_mcp/modo.py:45 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# para falar com o SSO e com a API. Os headers XXX-LITE-* do .env são da stack DockerFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathstreasy_mcp/credenciais.py:235 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesf"preencha {SEGREDO_POR_AMBIENTE[ambiente]} no .env do Treasy MCP (ou aponte TREASY_ENV_FILE)"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 pathstreasy_mcp/modo.py:213 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""``TREASY_ENV_FILE`` ou o ``.env`` na raiz do repositório do MCP (derivado do módulo)."""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 pathstreasy_mcp/arquivos.py:86 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesif limpo in PASTAS_BLOQUEADAS or limpo.startswith(".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 pathstreasy_mcp/modo.py:23 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files- os segredos do client ``ambassador`` vêm do ``.env`` do repositório do MCPFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathstreasy_mcp/credenciais.py:3 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesA senha do usuário mora num arquivo ``.env`` fora de qualquer repositório, gravadoFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathstreasy_mcp/sessao_auth.py:272 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"""Quem tem a senha no arquivo é da casa e esqueceu o .env; os outros só têm o navegador."""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
≈59 tok
1 file · 51 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

Not checked against OSV yet; the weekly check has not reached this version.