MCP compliance proxy between agent and tools: deterministic governance, fail-closed, audit trail.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
load-knowledgeNo description publishedThis tool published no description. Forge does not invent one.
harness_statusNo description publishedThis tool published no description. Forge does not invent one.
harness_sessionNo description publishedThis tool published no description. Forge does not invent one.
harness_budgetNo description publishedThis tool published no description. Forge does not invent one.
harness_temporal_checkNo description publishedThis tool published no description. Forge does not invent one.
harness_approvalsNo description publishedThis tool published no description. Forge does not invent one.
harness_assessNo description publishedThis tool published no description. Forge does not invent one.
kcp_planNo description publishedThis tool published no description. Forge does not invent one.
kcp_loadNo description publishedThis tool published no description. Forge does not invent one.
kcp_traceNo description publishedThis tool published no description. Forge does not invent one.
kcp_validateNo description publishedThis tool published no description. Forge does not invent one.
kcp_replayNo description publishedThis tool published no description. Forge does not invent one.
0 of 12 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP compliance proxy between agent and tools: deterministic governance, fail-closed, audit trail.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.