@systemdox/mcp-server

MCPcommunity
v0.1.35io.github.pugliesewebUnknownUpdated 15d agonpmGitHub

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

Works in
ClaudeCursorCopilotGemini

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
15d agoLast update
Needs 1 credential before it runs
  • SYSTEMDOX_API_KEYAPI keyrequired

    SystemDox 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.

Package
Authorio.github.puglieseweb
LicenseUnknown
Version0.1.35
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface16 tools · none privileged
Security scan✓ Cleanv0.1.32 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

16 tools · none privileged
Statically extracted from the published packagev0.1.32 · 1mo ago

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 published

This tool published no description. Forge does not invent one.

get_guardrailsNo description published

This tool published no description. Forge does not invent one.

get_specsNo description published

This tool published no description. Forge does not invent one.

get_docsNo description published

This tool published no description. Forge does not invent one.

get_tech_stackNo description published

This tool published no description. Forge does not invent one.

get_planning_contextNo description published

This tool published no description. Forge does not invent one.

get_plan_boardNo description published

This tool published no description. Forge does not invent one.

get_contextNo description published

This tool published no description. Forge does not invent one.

create_checkNo description published

This tool published no description. Forge does not invent one.

create_guardrailNo description published

This tool published no description. Forge does not invent one.

update_specNo description published

This tool published no description. Forge does not invent one.

report_decisionNo description published

This tool published no description. Forge does not invent one.

get_project_rulesNo description published

This tool published no description. Forge does not invent one.

create_project_ruleNo description published

This tool published no description. Forge does not invent one.

get_prompt_templatesNo description published

This tool published no description. Forge does not invent one.

create_prompt_templateNo description published

This 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.

About

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.