openspec-mcp (Lumiaqian/openspec-mcp) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 40 tools. No publisher has claimed this listing.
Enables spec-driven development with task tracking, approval workflows, and real-time progress monitoring through OpenSpec CLI functionality. Includes a web dashboard for visual management of change proposals and specifications.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
Lumiaqian
Source: Glama · also listed on ModelScope
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
When Vitest UI server is listening, arbitrary file can be read and executed
@fastify/static vulnerable to route guard bypass via path traversal
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability
Fastify's Content-Type header tab character allows body validation bypass
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
40/40 tools missing one or more hints — openspec_ai_analyze_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); openspec_get_approval_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); openspec_request_approval (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +37 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool test coverage
Only 0/40 tools referenced in tests (0%)
Write tests that reference each tool by name so every tool has at least one test.
Shell command execution
1 call in production code run through a shell (src/core/openspec-cli.ts:102)
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
Production dependencies are patched
0 critical, 4 high severity in production deps — @fastify/static@7.0.4 (high), @modelcontextprotocol/sdk@1.24.3 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dev dependencies
1 critical/high in dev-only deps (does not ship to users)
Upgrade dev dependencies when convenient.
Dependency freshness
1/9 production deps stale: gray-matter@2023-07-12 (3.1y)
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/lumiaqian/openspec-mcp)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check