granttap-mcp@0.8.159
CAUTION· startup onlyPublisher claims: "Commercial computer runtime connecting local coding agents to GrantTap on Mac, iPhone, iPad and Apple Watch." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
- It will ask for
- no credential variables read in the code
- Where it talks to
- granttap.com (its own)Also chatgpt.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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable and talks to granttap.com, its own; the guard pins the network to what the honeypot saw and logs every call.
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; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 71/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: Pipe-to-shell pattern; Access to sensitive file paths; Auto-update or dynamic fetch configuration. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 30 s · 2 scenarios · 0 deviationsStatic findings
+ "In a trusted terminal: curl -fsSL https://chatgpt.com/codex/install.sh | sh";Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.const updaterEnv = { ...env, PATH: [nodeDirectory, env.PATH ?? ''].join(delimiter) };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.&& process.env.GRANTTAP_DISABLE_AUTO_UPDATE !== "1" && !process.env.NODE_TEST_CONTEXT;Fix: Pin versions and sources; vendor anything fetched at install time.cwd, env: { ...env, NO_COLOR: "1", CI: "1" }, stdio: ["ignore", "pipe", "pipe"],Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.+ "In a trusted terminal: curl -fsSL https://chatgpt.com/codex/install.sh | sh";Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.import { startHttpMcpServer } from "../http/http-server";Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.const npx = first(roots.map((root) =>Fix: Pin versions and sources; vendor anything fetched at install time.…p\")));\n if (installed) return { command: installed, args: [] };\n const npx = first(roots.map((root) => join(root, \"npx\"))) || \"npx\";\n return { comma…Fix: Pin versions and sources; vendor anything fetched at install time.const npx = first(roots.map((root) => join(root, "npx"))) || "npx";Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
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 granttap-mcp@0.8.159 as of 5d ago. This is the package itself, not its dependencies.
What would make this Verified
9 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Pipe-to-shell pattern≈ +9 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- Unclaimed publisher≈ +8 on the totalClaim sergii-ziborov: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- 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.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Remote installer piped to shell≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.