Skills/npm/mcp-grocy

mcp-grocy@2.10.0

VERIFIED· not started

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

Registry npm (MCP server)Publisher miguelangel-nubla · publishing for 433 daysInstalls 619Last detonated 2 h ago
$claude mcp add mcp-grocy -- npx -y mcp-grocy
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
GROCY_API_KEYMCP_HTTP_ACCESS_TOKENMCP_OAUTH_ALLOWED_SUBJECTSMCP_OAUTH_AUDIENCEMCP_OAUTH_ISSUERMCP_OAUTH_REQUIRED_SCOPESMCP_OAUTH_RESOURCE_URLConfiguration, not credentials: ENABLE_HTTP_SERVER, GROCY_BASE_URL, GROCY_ENABLE_DEV_TOOLS, GROCY_ENABLE_SSL_VERIFY, GROCY_MAX_RESPONSE_BYTES, HTTP_CORS_ORIGIN, HTTP_SERVER_PORT, LOG_CATEGORIES, MCP_HTTP_TRANSPORT_ONLY, MCP_SESSION_IDLE_TIMEOUT_MS, MCP_SESSION_SWEEP_INTERVAL_MS, REST_RESPONSE_SIZE_LIMIT, SERIALIZE_STRUCTURED_TO_CONTENT
Where it talks to
no vendor host named in the code
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 GROCY_API_KEY, MCP_HTTP_ACCESS_TOKEN, MCP_OAUTH_ALLOWED_SUBJECTS, MCP_OAUTH_AUDIENCE, MCP_OAUTH_ISSUER, MCP_OAUTH_REQUIRED_SCOPES, MCP_OAUTH_RESOURCE_URL and talks to its vendor. 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 --net declared -- npx -y mcp-grocy

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

What changed since 2.8.0

vet-skills diff mcp-grocy 2.8.0 2.10.0

This version reaches for something 2.8.0 did not: 5 new credential variables (MCP_OAUTH_ALLOWED_SUBJECTS, MCP_OAUTH_AUDIENCE, MCP_OAUTH_ISSUER, MCP_OAUTH_REQUIRED_SCOPES, …). Compared from the two recorded runs, not from source.

New credential variables
MCP_OAUTH_ALLOWED_SUBJECTS, MCP_OAUTH_AUDIENCE, MCP_OAUTH_ISSUER, MCP_OAUTH_REQUIRED_SCOPES, MCP_OAUTH_RESOURCE_URL

2.10.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only. Only one of the two runs produced a tool list; tools are not compared.

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-19 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 · 61 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
60sprocessdependency install exceeded 60s
60sclaimednot started: dependency install timed out; the server itself was not observed
60sprocessscript backend runs setup only
60sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsbuild/config/index.js:25 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst resolved = { ...env };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 8,435 lines in 48 files.

Cost to the agent

Instructions loaded
≈49 tok
1 file · 48 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 mcp-grocy@2.10.0 as of 2 h ago. This is the package itself, not its dependencies.