veritasgraph-mcp@0.2.0
VERIFIED· not startedPublisher claims: "The first zero-trust, air-gapped Enterprise GraphRAG server for 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
- It will ask for
STUDIO_API_TOKENSSTUDIO_AUTHVG_SECRET_KEYVG_STRUCTURED_DSNConfiguration, not credentials: OLLAMA_HOST, STUDIO_CORS_ORIGINS, STUDIO_DATA_DIR, STUDIO_EVAL_STEP_SECONDS, STUDIO_FT_STEP_SECONDS, STUDIO_GRAPH_CHUNK_SIZE, STUDIO_TOOL_ALLOWED_NETWORKS, VERITASGRAPH_COMPILE_INTERVAL, VERITASGRAPH_DB, VERITASGRAPH_MCP_MODE, VERITASGRAPH_MODEL, VERITASGRAPH_PII_POLICY, VERITASGRAPH_PII_REVEAL_ROLE, VERITASGRAPH_SNAPSHOT_KEEP, VERITASGRAPH_TERM_MIN_DEGREE, VG_ASK_COVERAGE, VG_ASK_MIN_SIMILARITY, VG_EMBED_DOC_PREFIX, VG_EMBED_QUERY_PREFIX, VG_GRAPHRAG_CHAT, VG_LLM_ALLOW_REMOTE, VG_RERANK_MODE, VG_STRUCTURED_ALLOWED_NETWORKS, VG_STRUCTURED_AUTO_MIGRATE, VG_STRUCTURED_FILE_ROOT- Where it talks to
- no vendor host named in the codeAlso firecrawl.dev, tavily.com, exa.ai, e2b.dev, emkc.org, githubcopilot.com, example.local — 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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names firecrawl.dev, tavily.com, exa.ai, e2b.dev, emkc.org, githubcopilot.com, example.local as well as its own vendor. The guard injects STUDIO_API_TOKENS, STUDIO_AUTH, VG_SECRET_KEY, VG_STRUCTURED_DSN only into requests to the host you bind (and its subdomains) and refuses the rest.
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 85/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
<summary><b>Share with your team (free)</b></summary> | Method | Duration | Local Ollama | Setup | Best for | |--------|----------|:------------:|-------|------Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 veritasgraph-mcp@0.2.0 as of 5d ago. This is the package itself, not its dependencies.