Skills/PyPI/sealmetrics-mcp

sealmetrics-mcp@0.4.0

VERIFIED· not started

Publisher claims: "DEPRECATED - use the hosted Sealmetrics MCP server at https://mcp.sealmetrics.com/mcp or the npm package @sealmetrics/mcp" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher sealmetrics · publishing for 341 daysInstalls 64Last detonated 57 min ago
$claude mcp add sealmetrics-mcp -- uvx sealmetrics-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
SEALMETRICS_API_TOKENSEALMETRICS_PASSWORDConfiguration, not credentials: SEALMETRICS_ACCOUNT_ID, SEALMETRICS_EMAIL
Where it talks to
sealmetrics.com (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 SEALMETRICS_API_TOKEN, SEALMETRICS_PASSWORD and talks to sealmetrics.com. 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 SEALMETRICS_API_TOKEN=sealmetrics.com,SEALMETRICS_PASSWORD=sealmetrics.com -- uvx sealmetrics-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-17 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 · 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 pathspyproject.toml:50 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"/.env*",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
npx invocation of non-well-known packageserver.py:1733 · npx invocation of non-well-known package — may execute untrusted code│ Or run it locally: npx -y @sealmetrics/mcp │Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈68 tok
1 file · 7 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 sealmetrics-mcp@0.4.0 as of 21 min ago. This is the package itself, not its dependencies.