Skills/npm/foundryvtt-mcp

foundryvtt-mcp@2.1.0

CAUTION· not started

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

Registry npm (MCP server)Publisher g33ks · publishing for 9 daysInstalls 229Last detonated 7d ago
What would fix thisWatchDispute verdict

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: Caution 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

Code inventory arrives with this version's next honeypot run.
It will ask for
unknown until the next run
Where it talks to
unknown until the next run
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try foundryvtt-mcp` runs it now and prints the full answer.

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-08 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.8sprocessdependency install exit 1
0.8sprocessexec /usr/bin/date
0.8sprocessexec /usr/bin/timeout
0.8sclaimedno tools/list reply (exit 0)
0.8sprocessscript backend runs setup only
0.9sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathsdist/shared/paths.js:31 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* development `.env`, never from the configuration file it locates.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/shared/protocol.js:26 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesexport const SettingSourceSchema = z.enum(['env', '.env', 'file', 'default']);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/index.js:5 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* `.env`, configuration file, defaults) using Zod schemas.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/env-layers.js:33 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst file = path.join(cwd, '.env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/env-layers.js:16 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* Claude desktop starts MCP servers in `C:\Windows\System32`; a `.env` thereFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/env-layers.js:28 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files/** Settings of the `.env` file in `cwd`; empty when there is none (or `cwd` is System32). */Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/sources.js:57 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* `.env` only — the file cannot say where the file is.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/shared/relay-config.js:20 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files/** Resolves the configuration again from the environment, `.env` and the file. */Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/cli/init.js:67 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesreturn source === 'env' || source === '.env';Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/sources.js:6 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* own environment and an optional development `.env`. Per setting, the firstFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
MEDIUM
File permission modification commanddist/config/sources.js:104 · File permission modification command — agent changes file ownership/permissionsstate.warning = `${file} can be read by other users and holds passwords: run \`chmod 600 ${file}\``;Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
HIGH
Access to sensitive file pathsdist/config/sources.js:125 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesconst located = { ...dotenvFile.values, ...env };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/env-layers.js:4 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* a `.env` file in the working directory (handy for development).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/foundry/client.js:414 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* The two transports are additive, not exclusive (see `.env.example`: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 packagedist/cli/snippets.js:32 · npx invocation of non-well-known package — may execute untrusted codereturn `npx ${packageName()}`;Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsdist/shared/config-notice.js:11 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filescase '.env':Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/env-layers.js:6 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* `.env` is parsed, never loaded into `process.env`: a relay hands its ownFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/shared/config-notice.js:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesreturn 'the .env file of its working directory';Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathsdist/config/sources.js:131 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files['.env', dotenvFile.values],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 packagedist/cli/snippets.js:24 · npx invocation of non-well-known package — may execute untrusted code* the `bin` name for a global install, `npx <package>` from npx's cache,Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
HIGH
Access to sensitive file pathsdist/config/sources.js:10 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files* 2. `.env` in the working directoryFix: 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 packagedist/shared/build-order.js:13 · npx invocation of non-well-known package — may execute untrusted code* it was extracted, so a 2.0.0 extracted after a 2.1.0 (npx cache, a secondFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagedist/index.js:86 · npx invocation of non-well-known package — may execute untrusted code// Use realpath so the comparison works when npm/npx installs the bin as aFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
Process kill commanddist/shared/spawn.js:5 · Process kill command — agent can terminate processes* A direct detached child keeps the relay as its parent pid, so a tree killFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

Cost to the agent

Instructions loaded
≈53 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

No advisories in OSV for @g33ks/foundryvtt-mcp@2.1.0 as of 7d ago. This is the package itself, not its dependencies.

What would make this Verified

3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim g33ks: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
  3. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  4. File permission modification command≈ +2 on the totalRequest the narrowest permission that works; replace wildcards with the exact paths or hosts.
  5. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
  6. Process kill command≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim g33ksPropose a patch to the maintainer