Skills/npm/foundryvtt-mcp

foundryvtt-mcp@3.0.0

CAUTION

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 10 daysInstalls 934Last detonated 1 h ago

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
no credential variables read in the code
Where it talks to
no vendor host named in the codeAlso foundryvtt.com, githubusercontent.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
what the tools do when called with real credentials

Connect it under the guard; read the third-party hosts first. The code names foundryvtt.com, githubusercontent.com as well as its own vendor. The guard pins the network to the hosts the honeypot saw.

$vet-skills run --net declared -- npx -y @g33ks/foundryvtt-mcp

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

What changed since 2.1.0

vet-skills diff foundryvtt-mcp 2.1.0 3.0.0

This version reaches for something 2.1.0 did not: 2 new hosts (foundryvtt.com, githubusercontent.com). Compared from the two recorded runs, not from source.

New hosts
foundryvtt.com, githubusercontent.com

2.1.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) on 2026-11-16 and scored it 70/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 · 33 s · 2 scenarios
t+CategoryObserved action
0.0sprocessno install scripts in bundle
13sprocessdependency install exit 0
33sfilesystemread ~/.config/foundryvtt-mcp/config.env outside project
33sfilesystemwrote ~/.local/state/foundryvtt-mcp/relay.log
33sclaimed115 tools: roll_dice, search_actors, get_actor_details, get_actor_inventory, update_actor_attributes, create_world_actor, create_full_actor, delete_world_actor, search_items, search_compendium, create_actor_item, update_actor_item, delete_actor_item, get_scene_info, create_scene, switch_scene, delete_scene, set_scene_lighting, reset_fog, set_scene_weather, list_walls, create_wall, delete_wall, set_door_state, list_scene_assets
33stoolsc4bb169ba97048e8
33stools82c39c41c2e1b3e5
33stools3211ca900769c087
33stools69872263704f2e3e
33stools729844b99a8aa85a
33stools9cb5bb8fdd80b8ff
33stools01e168d5bafdef5d
33stools5a4476afe7e8ecaf
33stools52746e9e717666e7
33stools10a182ea01ea7e26
33stoolsf3312dd1f7416f15
33stoolsac92fa4bf75707db
33stools7cccf78a9c7d4c8d
33stools2e8fd64d82e54b4c
33stools3a28a74252e960ad
33stools98f47833cd39e3d8
33stoolsdb733f3cac235cb1
33stools7b9322466345a51d
33stoolsccbc6e9da87bdd55
33stoolsa4d6f8659e65a94c
33stoolsb17b0900edf02900
33stools5111e97879c4cd49
33stools15ae985cf672add8
33stoolsc39018831b847e41
33stools2f865657f57bc541
33stools5e4bfa5d2a1f8794
33stools480255e20ebe67a7
33stools4b5c972a7a4a8bb7
33stools64e8204dafc54d5f
33stools9eeec4e4c2e304f9
33stoolsa65bdb7e8e08a0a5
33stoolse21e42a18deb9a1c
33stools859560245aea939e
33stools0ece4dfc792da164
33stools189cda6038d71f5f
33stoolsd04b28b0ef71045c
33stoolsaf88fc99b80fc306
33stools016ae94bad260383
33stools629de89e0cc3f417
33stools4bcdd7bdafb3c209
33stools230b3e382daa47de
33stools55a840f1a580294f
33stools0cfcb2953b649a34
33stools753c01d5ae1262e7
33stools807f8ba068c0cd68
33stools84f5121badce924a
33stoolsfb990d25d9994096
33stools4e0c79232818ac9e
33stools51e5e99b93e5054c
33stools8912da0780a9b813
33stools88f52e25bdc35b70
33stools29832eb27903eb6c
33stoolsd75195bb50669aad
33stools7b18f7eda5b7bf26
33stools5d22f84e7061c254
33stools4538c67818ffa4e1
33stoolsd5374c0fe5a658a5
33stools01bb3f874a99a9b0
33stools35610f269209b649
33stools4aec75f8872a5d02
33stoolsb7760d878127a28f
33stoolscb73e8c2dc66fbc0
33stools5e1b426f58d3cac1
33stools8e0ccdb0255eec43
33stools687ea82530450123
33stools7d15881b037173a8
33stools9611d9ddb7f958c8
33stools4b84cc77aa39aa44
33stools645b01744880af56
33stools0a4e4130f3aba1d9
33stoolsd4200ca4d0fe9e3d
33stoolsdb0fa351c6ba707d
33stools9f80af8869203d68
33stoolsb0375a4d66561716
33stoolsde68a3c1c5aff1f0
33stoolsa050fade88154ad8
33stoolsf086a5a22b3ce11a
33stoolsd639ff4b6b0f56d3
33stools27ea6d06487398d0
33stools599ac97f0b738c7e
33sprocessscript backend runs setup only
33sprocessno install scripts to re-run

Static findings

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
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: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
HIGH
Access to sensitive file pathsdist/config/sources.js:132 · 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
HIGH
Access to sensitive file pathsdist/config/sources.js:126 · 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/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/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/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/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: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/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/foundry/client.js:420 · 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
HIGH
Access to sensitive file pathsdist/config/sources.js:58 · 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/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/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
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
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
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
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
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
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
MEDIUM
File permission modification commanddist/config/sources.js:105 · 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/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
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

Cost to the agent

Instructions loaded
≈53 tok
1 file · 81 in bundle
Tool list per prompt
≈31,431 tok
115 tools · 273 per tool
Handshake
2170 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 563

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

Not checked against OSV yet; the weekly check has not reached this version.

What would make this Verified

10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Reads credential files≈ +27 on the totalThe sandbox saw reads under ~/.ssh, ~/.aws, ~/.npmrc, ~/.config or similar. Read only files inside the project, and only the ones the task needs. Seen: ~/.config/foundryvtt-mcp/config.env.
  2. 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.
  3. Touches files outside the project≈ +7 on the totalKeep reads and writes inside the working directory, or declare the exact paths in `filesystem:` and explain why in the README.
  4. 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.
  5. 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.
  6. npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
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