When was npm:context-fabric last audited?

Last checked 2026-06-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

B+

npm:context-fabric

Item: npm:context-fabric
Rating: 89
Author: wmcp.sh

https://www.npmjs.com/package/context-fabric

89/100 · MCP Trust Grade · checked 1mo ago · MCP 1.0.7

Is the npm:context-fabric MCP server safe to use?

Independent trust grade B+ (89/100). Static analysis of npm package context-fabric@1.0.7 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured. wmcp.sh continuously watches npm:context-fabric for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

What it offers — 5 tools · Developer Tools

cf_capture

Capture current project state.

cf_drift

Check context drift. Returns severity.

cf_query

Get project context briefing.

cf_health

Report local database, capture, and hook health.

cf_log_decision

Log an architecture decision.

Spec / packaging20%100

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

Security (OWASP MCP)30%70

uses eval/exec/child_process (review for unsanitized input)
scanned 6 source files

Maintenance / popularity20%100

published within 90 days
8 published versions

Tool hygiene15%95

✓ ships TypeScript types
3 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license

Findings

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

Grade another server

We re-grade npm:context-fabric 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:context-fabric grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Acontext-fabric

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 B+](https://wmcp.sh/mcp/grade/npm%3Acontext-fabric/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Acontext-fabric)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Acontext-fabric"><img src="https://wmcp.sh/mcp/grade/npm%3Acontext-fabric/badge.svg" alt="MCP Trust Grade B+ · 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.