Project (PyPI) MCP Server
project-mcp
PyPI
v0.1.7
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
把一个本地项目作为 token 保护的 MCP 服务暴露给 ChatGPT。
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 8 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 7
high Reads a sensitive credential path or dumps the environment (src/project_mcp/config.py)MTC-SRC-006
In the server's implementation (`src/project_mcp/config.py:25`): Reading private keys / cloud credentials, or serializing the whole environment, is a sensitive-data source that becomes exfiltration when combined with any egress. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: , "**/.ssh/*", "id_rsa", "id_rsa.*", "id_ed25519", "id_ed25519.*", "node_modules", "node_mod
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/project_mcp/config.py
high Shell/command execution in server code (src/project_mcp/cli.py)MTC-SRC-002
In the server's implementation (`src/project_mcp/cli.py:252`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: yan]") server = subprocess.Popen( [ sys.executable, "-m",
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/project_mcp/cli.py
high Shell/command execution in server code (src/project_mcp/workspace.py)MTC-SRC-002
In the server's implementation (`src/project_mcp/workspace.py:264`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: 5) -> str: result = subprocess.run( ["git", *args], cwd=config.real_root, text=True,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server src/project_mcp/workspace.py
medium Tool "write_file" can modify the filesystemMTC-CAP-002
Tool "write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool write_file
medium Tool "edit_file" can modify the filesystemMTC-CAP-002
Tool "edit_file" can write, overwrite or delete files (keyword "edit_file" in tool name). Verify it is scoped to a safe directory.
Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.
Location: tool edit_file
low Mutating tool "write_file" declares no destructiveHintMTC-CAP-005
Tool "write_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool write_file
low Mutating tool "edit_file" declares no destructiveHintMTC-CAP-005
Tool "edit_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.
Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.
Location: tool edit_file
Tools 10
Each tool and what it can reach — statically extracted from the published source.
edit_filewrites filesread_filereads sensitive datawrite_filewrites filesgrepno sensitive capabilityrun_checkno sensitive capabilitysearchno sensitive capabilityserver_configno sensitive capabilityshow_changesno sensitive capabilitytreeno sensitive capabilityworkspace_infono sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.7 latest |
A 92/100 | 7 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan project-mcp --online --registry pypiOther implementations of Project 3
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
Intent-based MCP server for project documentation search. Maps natural language queries to the right sources automatically—no configuration needed. The standard for AI agent documentation search.
A ModelContextProtocol server to let agents discover your project, such as APIs (using OpenAPI) or other resources.
MCP server con inteligencia de proyecto para Next.js + Prisma. Setup interactivo con OpenSpec, Engram, Skills comunitarios y Guardian Angel.
More in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.
A standalone MCP stdio bridge for Affinity by Canva's local MCP SSE server.