mcp@2.12.0

VERIFIED· not started

Publisher claims: "Rymi MCP server — manage AI voice agents via Model Context Protocol" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher rymi · publishing for 144 daysInstalls 1,539Last detonated 4d ago
$claude mcp add mcp -- npx -y @rymi/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
RYMI_API_KEYConfiguration, not credentials: BUSINESS_NAME_KEYS, RYMI_MCP_READONLY
Where it talks to
rymi.live (its own)Also acme.com — 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 acme.com as well as its own vendor. The guard injects RYMI_API_KEY only into requests to rymi.live (and its subdomains) and refuses the rest.

$vet-skills run --secrets RYMI_API_KEY=rymi.live -- npx -y @rymi/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-10 and scored it 93/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 · 2 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
1.5sprocessdependency install exit 1 · npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:* npm error A complete log of this run can be found in: /tmp/ks-detonate-ufOV28/task/home/.npm/_logs/2026-11-10T02_38_15_666Z-debug-0.log
1.5sclaimednot started: dependency install failed (exit 1); the server itself was not observed
1.5sprocessscript backend runs setup only
1.5sprocessno install scripts to re-run

Static findings

No findings across 9,959 lines in 6 files.

Cost to the agent

Instructions loaded
≈50 tok
1 file · 6 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 @rymi/mcp@2.12.0 as of 4d ago. This is the package itself, not its dependencies.