mcp-memgraph@0.4.1
VERIFIED· not startedPublisher claims: "MCP integration and utilities for Memgraph MCP server" 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
MCP_AUTH_AUDIENCEMCP_AUTH_DEFAULT_TENANT_CLAIMMCP_AUTH_ENABLEDMCP_AUTH_ISSUERMCP_AUTH_JWKS_URLMCP_AUTH_REQUIRED_SCOPEMCP_AUTH_STATIC_CLIENT_IDMCP_AUTH_TENANTS_CLAIMMEMGRAPH_PASSWORDConfiguration, not credentials: MCP_HOST, MCP_LOG_FILE, MCP_LOG_LEVEL, MCP_PORT, MCP_READ_ONLY, MCP_SERVER, MCP_TENANT_CATALOG, MCP_TRANSPORT, MEMGRAPH_DATABASE, MEMGRAPH_URL, MEMGRAPH_USER- Where it talks to
- no vendor host named in the codeAlso keycloak.svc, default.svc — 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 keycloak.svc, default.svc as well as its own vendor. The guard injects MCP_AUTH_AUDIENCE, MCP_AUTH_DEFAULT_TENANT_CLAIM, MCP_AUTH_ENABLED, MCP_AUTH_ISSUER, MCP_AUTH_JWKS_URL, MCP_AUTH_REQUIRED_SCOPE, MCP_AUTH_STATIC_CLIENT_ID, MCP_AUTH_TENANTS_CLAIM, MEMGRAPH_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-08 and scored it 91/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
load_dotenv() # load environment variables from .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.load_dotenv() # Load environment variables from .envFix: 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 mcp-memgraph@0.4.1 as of 6d ago. This is the package itself, not its dependencies.