Skills/npm/automono-trans-mcp

automono-trans-mcp@0.1.4

VERIFIED· not started

Publisher claims: "Model Context Protocol (MCP) server for AutoMonoTrans Basque localization integration" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher oihu · publishing for 3 daysInstalls 631Last detonated 1 h ago
$claude mcp add automono-trans-mcp -- npx -y @oihu/automono-trans-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
AUTOMONO_TRANS_API_KEYConfiguration, not credentials: AUTOMONO_TRANS_API_URL, AUTOMONO_TRANS_PROJECT_ID
Where it talks to
no vendor host named in the codeAlso automono.io — not the publisher's domain; check what for before connecting.
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, and read the third-party hosts first. The code names automono.io as well as its own vendor. The guard injects AUTOMONO_TRANS_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y @oihu/automono-trans-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-21 and scored it 90/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 · 8 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
7.4sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-rZOE12/task/home/.npm/_logs/2026-11-21T22_39_37_810Z-debug-0.log
7.4sclaimednot started: dependency install failed (exit 1); the server itself was not observed
7.5sprocessscript backend runs setup only
7.5sprocessno install scripts to re-run

Static findings

No findings across 2,817 lines in 5 files.

Cost to the agent

Instructions loaded
≈62 tok
1 file · 5 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 @oihu/automono-trans-mcp@0.1.4 as of 26 min ago. This is the package itself, not its dependencies.