C-

npm:speclock

Item: npm:speclock
Rating: 72
Author: wmcp.sh

https://www.npmjs.com/package/speclock

72/100 · MCP Trust Grade · checked 3h ago · MCP 5.5.7

What it offers — 30 tools · Developer Tools

speclock_init

Initialize SpecLock in the current project directory.

speclock_get_context

THE KEY TOOL. Returns the full structured context pack.

speclock_set_goal

Set or update the project goal.

speclock_add_lock

Add a non-negotiable constraint (SpecLock).

speclock_remove_lock

Remove (deactivate) a SpecLock by its ID.

speclock_add_decision

Record an architectural or design decision.

speclock_add_note

Add a pinned note for reference.

speclock_set_deploy_facts

Record deployment configuration facts.

speclock_log_change

Manually log a significant change.

speclock_get_changes

Get recent file changes tracked by SpecLock.

speclock_get_events

Get the event log, optionally filtered by type.

speclock_check_conflict

Check if a proposed action conflicts with any active SpecLock. Uses fast heuristic + Gemini LLM for universal domain coverage. In hard enforcement mod

speclock_session_briefing

Start a new session and get a full briefing.

speclock_session_summary

End the current session and record what was accomplished.

speclock_checkpoint

Create a named git tag checkpoint for easy rollback.

speclock_repo_status

Get current git repository status.

speclock_suggest_locks

AI-powered lock suggestions based on project patterns.

speclock_detect_drift

Scan recent changes for constraint violations.

+12 more tools

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 30 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 5 source files

Maintenance / popularity20%100

published within 90 days
68 published versions

Tool hygiene15%70

no TypeScript types
3 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license
56 weekly downloads

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package speclock@5.5.7 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:speclock on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:speclock grade C-

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Aspeclock

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C-](https://wmcp.sh/mcp/grade/npm%3Aspeclock/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Aspeclock)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Aspeclock"><img src="https://wmcp.sh/mcp/grade/npm%3Aspeclock/badge.svg" alt="MCP Trust Grade C- · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.