io.github.shashwatgtm/craft-content-mcp

MCPcommunity
v1.0.1io.github.shashwatgtmUnknownUpdated 5mo agonpmGitHub

8 content tools: Case Studies, Newsletters, Webinars, Repurposing, Thought Leadership

🎯 CRAFT Content Framework MCP Server - Complete redesign with user-centric inputs, actual content analysis, and publish-ready outputs. Every tool was redesigned using chain of thought from the user's perspective: 1. What does the user actually want? (Not what looks impressive in a demo) 2. What do they already know? (Keep inputs simple - don't ask for things they need to figure out) 3. Does the…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.shashwatgtm
LicenseUnknown
Version1.0.1
Sourcemcp-registry
npm@shashwatgtmalpha/craft-content-mcp
GitHubshashwatgtm/craft-content-mcp
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
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 surface8 tools · none privileged
Security scan✓ Cleanv2.0.1 · 20d ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

🎯 CRAFT Content Framework MCP Server - Complete redesign with user-centric inputs, actual content analysis, and publish-ready outputs. Every tool was redesigned using chain of thought from the user's perspective: 1. What does the user actually want? (Not what looks impressive in a demo) 2. What do they already know? (Keep inputs simple - don't ask for things they need to figure out) 3. Does the output save them work? (Publish-ready, not templates to fill) Tool | Before | After |…

Keywords
mcp