mcp-project-context-server@2.0.0
VERIFIED· not startedPublisher claims: "A Python MCP server that gives LLMs persistent, searchable access to project context — documentation, architecture decisions, and session notes." 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
COHERE_API_KEYGITHUB_TOKENGOOGLE_API_KEYMCP_AUTH_TOKENMCP_AUTH_TYPEOPENAI_API_KEYREPO_AUTH_TOKENVOYAGE_API_KEYConfiguration, not credentials: APPROVED_ORGS, APPROVED_REPOS, CHUNK_SIZE, COHERE_EMBED_MODEL, EMBED_CONCURRENCY, EMBED_MODEL, EMBED_PROVIDER, GOOGLE_APPROVED_SERVICE_ACCOUNTS, GOOGLE_EMBED_MODEL, GOOGLE_IAM_AUDIENCE, MCP_HOST, MCP_PORT, MCP_TRANSPORT, OLLAMA_EMBED_MODEL, OLLAMA_HOST, OPENAI_EMBED_MODEL, PROJECT_PATH, REPO_ADR_BRANCH, REPO_ADR_WRITE_MODE, REPO_BASE_URL, REPO_DEFAULT_BRANCH, REPO_MULTI_TENANT, REPO_PROVIDER, REPO_SESSION_BRANCH, REPO_SESSION_WRITE_MODE, VECTOR_STORE_PROVIDER, VERTEXAI_EMBED_MODEL, VERTEXAI_LOCATION, VERTEXAI_PROJECT, VOYAGE_BACKOFF_INITIAL_DELAY, VOYAGE_EMBED_MODEL- Where it talks to
- no vendor host named in the code
- 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. It asks for COHERE_API_KEY, GITHUB_TOKEN, GOOGLE_API_KEY, MCP_AUTH_TOKEN, MCP_AUTH_TYPE, OPENAI_API_KEY, REPO_AUTH_TOKEN, VOYAGE_API_KEY and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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
result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.No other findings across 10,301 lines in 81 files.
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-project-context-server@2.0.0 as of 6d ago. This is the package itself, not its dependencies.