Skills/PyPI/gateco

gateco@1.14.0

VERIFIED· not started

Publisher claims: "Official Python SDK for the Gateco API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server) · listed in the official MCP RegistryPublisher fortisil · publishing for 112 daysInstalls 268Last detonated 22 min ago
$claude mcp add gateco -- uvx gateco
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
GATECO_API_KEYGATECO_CREDENTIALS_FILE or --end-user-tokenConfiguration, not credentials: GATECO_BASE_URL
Where it talks to
gateco.ai (its own)
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 GATECO_API_KEY, GATECO_CREDENTIALS_FILE and talks to gateco.ai. 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 GATECO_API_KEY=gateco.ai,GATECO_CREDENTIALS_FILE=gateco.ai -- uvx gateco

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

What changed since 1.13.0

vet-skills diff gateco 1.13.0 1.14.0

In the sandbox, this version reached for nothing 1.13.0 did not. Compared from the two recorded runs, not from source.

1.13.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.

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-17 and scored it 91/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

MEDIUM
File type combined with upload actionsrc/gateco_sdk/cli.py:755 · File type combined with upload action — agent may exfiltrate local data files"file", help="Path to the file (.txt/.md are sent as text; other types are uploaded)"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
File type combined with upload actionsrc/gateco_sdk/cli.py:752 · File type combined with upload action — agent may exfiltrate local data files"ingest", help="Ingest a single file (.txt/.md as text; PDF, Office, CSV via upload)"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

Cost to the agent

Instructions loaded
≈43 tok
1 file · 81 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.