luiccian-vulcan-mcp@0.3.3
VERIFIED· not startedPublisher claims: "Vulcan 12 integration through the Model Context Protocol (MCP)" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
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 luiccian-vulcan-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 83/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 · 0 s · 2 scenarios · 0 deviationsStatic findings
* **No Plaintext Secrets in Workspace**: Never store GitHub tokens in committed `.env` files.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.You will follow this process for every documentation request:Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.## 3. Security & Zero `.env` PhilosophyFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Hot-reload handlers in the running Vulcan listener so latest on-disk handlers are activeFix: Pin versions and sources; vendor anything fetched at install time.Path('graphify-out/.graphify_ast.json').write_text(json.dumps({'nodes':[],'edges':[],'input_tokens':0,'output_tokens':0}, ensure_ascii=False), encoding="utf-8")Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Before traversal, expand the question against the graph's own vocabulary so a wording mismatch does not collapse the answer to noise. If the `graphify query` CLI is unavailable, fall back to an inlineFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.Path('graphify-out/.graphify_semantic.json').write_text(json.dumps({'nodes':[],'edges':[],'hyperedges':[],'input_tokens':0,'output_tokens':0}), encoding='utf-8')Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.- **No `.env` Files**: Do NOT create `.env` files in the repository to prevent committing plain-text secrets and ensure direct compatibility with `uvx`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 luiccian-vulcan-mcp@0.3.3 as of 7d ago. This is the package itself, not its dependencies.