Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
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.
SYSTEMDOX_API_KEYAPI keyrequiredSystemDox API key (generate in workspace settings). Scopes every tool call to the key's tenant.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
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.
get_checksNo description publishedThis tool published no description. Forge does not invent one.
get_guardrailsNo description publishedThis tool published no description. Forge does not invent one.
get_specsNo description publishedThis tool published no description. Forge does not invent one.
get_docsNo description publishedThis tool published no description. Forge does not invent one.
get_tech_stackNo description publishedThis tool published no description. Forge does not invent one.
get_planning_contextNo description publishedThis tool published no description. Forge does not invent one.
get_plan_boardNo description publishedThis tool published no description. Forge does not invent one.
get_contextNo description publishedThis tool published no description. Forge does not invent one.
create_checkNo description publishedThis tool published no description. Forge does not invent one.
create_guardrailNo description publishedThis tool published no description. Forge does not invent one.
update_specNo description publishedThis tool published no description. Forge does not invent one.
report_decisionNo description publishedThis tool published no description. Forge does not invent one.
get_project_rulesNo description publishedThis tool published no description. Forge does not invent one.
create_project_ruleNo description publishedThis tool published no description. Forge does not invent one.
get_prompt_templatesNo description publishedThis tool published no description. Forge does not invent one.
create_prompt_templateNo description publishedThis tool published no description. Forge does not invent one.
0 of 16 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.
Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.
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.