Skills/npm/grayboard-mcp-server

grayboard-mcp-server@0.5.10

VERIFIED· not started

Publisher claims: "Grayboard MCP Server for Claude Code" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher weolbu · publishing for 54 daysInstalls 1,393Last detonated 5d ago
$claude mcp add grayboard-mcp-server -- npx -y @weolbu/grayboard-mcp-server
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
GRAYBOARD_ACCESS_TOKENGRAYBOARD_REFRESH_TOKENConfiguration, not credentials: GRAYBOARD_API_URL, GRAYBOARD_FRONTEND_URL, GRAYBOARD_WORKSPACE_ID
Where it talks to
weolbu.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 GRAYBOARD_ACCESS_TOKEN, GRAYBOARD_REFRESH_TOKEN and talks to weolbu.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 GRAYBOARD_ACCESS_TOKEN=weolbu.com,GRAYBOARD_REFRESH_TOKEN=weolbu.com -- npx -y @weolbu/grayboard-mcp-server

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-09 and scored it 92/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 · 6 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
5.8sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-9d1pLn/task/home/.npm/_logs/2026-11-09T14_39_53_033Z-debug-0.log
5.8sclaimednot started: dependency install failed (exit 1); the server itself was not observed
5.9sprocessscript backend runs setup only
5.9sprocessno install scripts to re-run

Static findings

MEDIUM
Unicode escape sequence detecteddist/editor-syntax.d.ts:8 · Unicode escape sequence detected — may contain obfuscated payloads…4 \uBB38\uC790\uC5F4. \uC81C\uBAA9\uC740 h1~h3 \uAE4C\uC9C0\uB9CC \uB418\uACE0, \uCF5C\uC544\uC6C3\u00B7\uBAA9\uCC28\u00B7\uD2F0\uCF13/\uD504\uB85C\uC81D\uD2B8 \uCC38\uC870 \uB9C1\uD06C \uAC19\uC740 \uD655\uC7A5 \u…Fix: Put hosts, commands and strings in plain source. Decoding at runtime looks identical to malware and costs points on its own.
AST07

No other findings across 2,646 lines in 55 files.

Cost to the agent

Instructions loaded
≈51 tok
1 file · 55 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 @weolbu/grayboard-mcp-server@0.5.10 as of 5d ago. This is the package itself, not its dependencies.