@superdoc/mcp
BMCP server package @superdoc-dev/mcp
Install
agr install @superdoc/mcp --target claudeThis artifact does not publish files for Claude.
Document
{ "name": "@superdoc-dev/mcp", "version": "0.17.1", "type": "module", "engines": { "node": ">=20" }, "bin": { "superdoc-mcp": "./dist/index.js" }, "files": [ "dist" ], "scripts": { "dev": "bun run src/index.ts", "build": "bun build src/index.ts --outdir dist --target node --format esm", "test": "NODE_ENV=test bun test", "typecheck": "tsc --noEmit" }, "dependencies": { "@modelcontextprotocol/sdk": "^1.26.0", "@superdoc-dev/sdk": "workspace:", "zod": "^4.3.6" }, "devDependencies": { "@superdoc/document-api": "workspace:", "@superdoc/super-editor": "workspace:", "superdoc": "workspace:", "@types/bun": "catalog:", "@types/node": "catalog:", "typescript": "catalog:" }, "publishConfig": { "access": "public" } }
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- warnType matchbest-effort: server code not analyzed
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicensecopyleft/unknown — index-and-link only
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-f145d9dffffd2026-08-03