siemens-graph-studio-mcp-server@0.6.3
VERIFIED· not startedPublisher claims: "An MCP server for Altair Graph Studio (AGS) providing intelligent SPARQL query capabilities via the Model Context Protocol." 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
ANZO_PASSWORDConfiguration, not credentials: ANZO_PORT, ANZO_SERVER, ANZO_USERNAME, ENABLE_AGENT_DEBUG, ENABLE_LOGGING_DEBUG, GRAPHMART_URI- Where it talks to
- no vendor host named in the codeAlso cambridgesemantics.com, purl.org, openanzo.org, siemens.com, agent.memory — 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 cambridgesemantics.com, purl.org, openanzo.org, siemens.com, agent.memory as well as its own vendor. The guard injects ANZO_PASSWORD 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-18 and scored it 93/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
### Rule #1: Foreign Keys and Shared Attributes FirstFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule #4: Single Unified Cross-Domain ArchitectureFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule #2: Validate with SELECT COUNT Before Creating LinksFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule #5: Refresh Only, Never ReloadFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.### Rule #3: Avoid Cartesian ProductsFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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 siemens-graph-studio-mcp-server@0.6.3 as of 53 min ago. This is the package itself, not its dependencies.