SpecLock - AI Constraint Engine (sgroy10/speclock) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
72/100
2 months ago

SpecLock - AI Constraint Engine

AI Constraint Engine with AI Patch Firewall. 42 MCP tools. Patch Gateway (ALLOW/WARN/BLOCK verdicts), diff-native review (10 scored signals, hard escalation rules), Spec Compiler, Code Graph, Typed constraints, Python SDK, ROS2. Works with Claude Code, Cursor, Windsurf, Cline, Bolt.new, Lovable. 1073 tests. Free and open source. By Sandeep Roy.

→ sgroy10/speclock· 3.7K installs· listed on smithery

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

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

sgroy10

Source: Smithery · also listed on Glama

Is this your MCP?

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 →

⚡ Connect GitHub for Live Monitored

Install from

SmitheryGlama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 10 credentials: ANTHROPIC_API_KEY, GEMINI_API_KEY, GOOGLE_API_KEY, OPENAI_API_KEY, SPECLOCK_API_KEY, SPECLOCK_AUDIT_SECRET, SPECLOCK_ENCRYPTION_KEY, SPECLOCK_LICENSE_KEY, SPECLOCK_LLM_KEY, SPECLOCK_SSO_CLIENT_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highesbuild@0.27.3GHSA-gv7w-rqvm-qjhr

esbuild: Missing binary integrity verification in Deno module enables remote code execution via NPM_CONFIG_REGISTRY

lowesbuild@0.27.3GHSA-g7r4-m6w7-qqqr

esbuild allows arbitrary file read when running the development server on Windows

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretANTHROPIC_API_KEY
🔐 secretGEMINI_API_KEYGoogle Gemini API key for hybrid conflict detection
🔐 secretGOOGLE_API_KEY
🔐 secretOPENAI_API_KEY
🔐 secretSPECLOCK_API_KEYAPI key for authenticated access
configSPECLOCK_API_URL
🔐 secretSPECLOCK_AUDIT_SECRET
configSPECLOCK_CLI_NO_AUTORUN
configSPECLOCK_CORS_ORIGINS
🔐 secretSPECLOCK_ENCRYPTION_KEYexport ="your-secret"
🔐 secretSPECLOCK_LICENSE_KEY
🔐 secretSPECLOCK_LLM_KEYYour own LLM API key (Gemini/OpenAI/Anthropic)
configSPECLOCK_LLM_PROVIDER
configSPECLOCK_NO_PROXYfalse Set true for heuristic-only mode (~250ms). Skips the Gemini proxy (~2s)
configSPECLOCK_PROJECT_ROOT
configSPECLOCK_PROXY_URL
configSPECLOCK_PUBLIC_URL
configSPECLOCK_RATE_LIMIT
configSPECLOCK_SAVES_DIR
configSPECLOCK_SSO_CLIENT_ID
🔐 secretSPECLOCK_SSO_CLIENT_SECRET
configSPECLOCK_SSO_ISSUER
configSPECLOCK_SSO_REDIRECT_URI
configSPECLOCK_STRICTDefault WARN mode — no more false-positive blocks. Loud warnings instead. Opt in to strict with --strict or =1.
configSPECLOCK_TELEMETRYfalse Opt-in anonymous usage analytics
configSPECLOCK_TELEMETRY_ENDPOINT
configSPECLOCK_VERBOSE
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

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

83/83 tools missing one or more hints — speclock_init (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); speclock_get_context (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); speclock_set_goal (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +80 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 inputs are validated

44/83 tool handlers declare input schemas (53%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 6/83 tool handlers wrap calls in try/catch (7%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 14/83 tools referenced in tests (17%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

6 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

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.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/sgroy10-speclock-uzstyv)](https://m8ven.ai/mcp/sgroy10-speclock-uzstyv)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: c92306a8c34f25da70034432909efe943f302319
code hash: 3cd8ee5871cf6abeba388aa28cd7b7578e3fd0d80d48d72dd7359d22a6a4681a
verified: 6/16/2026, 11:41:03 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

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
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client