mcp-quality@0.8.0
VERIFIED· not startedPublisher claims: "The CI quality suite for MCP servers — lint, contract-test, benchmark, and load-test your MCP server before you ship it." 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
ANTHROPIC_API_KEYOPENAI_API_KEYConfiguration, not credentials: GITHUB_SHA- Where it talks to
- no vendor host named in the codeAlso example.test — 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 example.test as well as its own vendor. The guard injects ANTHROPIC_API_KEY, OPENAI_API_KEY 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 83/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
constraining it, so ``../../etc/passwd`` escapes the intended root. We can't *prove* aFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."npx -y @modelcontextprotocol/server-sequential-thinking"),Fix: Pin versions and sources; vendor anything fetched at install time.ServerSpec("filesystem", "server-filesystem", "npx -y @modelcontextprotocol/server-filesystem /tmp"),Fix: Pin versions and sources; vendor anything fetched at install time."constraint — a traversal payload (e.g. '../../etc/passwd') could escape "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.ServerSpec("memory", "server-memory", "npx -y @modelcontextprotocol/server-memory"),Fix: Pin versions and sources; vendor anything fetched at install time.proc = subprocess.run( # noqa: S603 - invoking a user-approved scannerFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(step, check=True, capture_output=True, text=True) # noqa: S603Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.ServerSpec("everything", "server-everything", "npx -y @modelcontextprotocol/server-everything"),Fix: Pin versions and sources; vendor anything fetched at install time.for spec in specs: # sequential: parallel npx downloads thrash disk/networkFix: Pin versions and sources; vendor anything fetched at install time.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-quality@0.8.0 as of 6d ago. This is the package itself, not its dependencies.