mcp-context-server@2.2.2
VERIFIED· not startedPublisher claims: "MCP Context Server — a FastMCP-based server providing persistent multimodal context storage for LLM agents." 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 mcp-context-server` 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-07 and scored it 80/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
`server.json` enables MCP client discovery. Every `Field(alias=...)` in `app/settings.py` MUST have a corresponding entry in `server.json` `environmentVariables`. This invariant is enforced by `test_sFix: Pin versions and sources; vendor anything fetched at install time.'Set via environment variable or .env file.'Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Configuration via `.env` file or environment. **Canonical source**: `app/settings.py` — all env vars with defaults, descriptions, and validation.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# This enables LangSmith SDK auto-detection when users configure via .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.RUN chmod +x /docker-entrypoint.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.RUN mkdir -p /cache/flashrank && chown appuser:appuser /cache/flashrankFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.# Load .env file to make environment variables available for PostgreSQL testsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# reading STORAGE_BACKEND from environment (user may have postgresql in .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.This function bridges the gap when users configure via .env file or settings.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# CRITICAL: Force SQLite backend for ALL tests (override .env STORAGE_BACKEND=postgresql)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Force SQLite backend for tests (override .env setting)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Use `Path` objects (not string concat). Env vars: `set VAR=value &&` (cmd) or `$env:VAR="value";` (PowerShell). DB path: `%USERPROFILE%\.mcp\context_storage.db`. Docker Desktop for PostgreSQL.Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.RUN mkdir -p /data && chown appuser:appuser /dataFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.# reading STORAGE_BACKEND from environment (user may have postgresql in .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.schema_filename = 'postgresql_schema.sql' if backend_type == 'postgresql' else 'sqlite_schema.sql'Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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-context-server@2.2.2 as of 21 min ago. This is the package itself, not its dependencies.