Publish articles to Qiita via MCP tools. Minimal, fast, and focused on Qiita authoring.
1. Enable developer mode: Settings > Connector > Developer mode 2. Select Developer mode 4. Input name, MCP Server URL, Auth and I believe and Create | | -------------- | ------------------------------------------------------- | name | Qiita | Auth | No Auth | You can create token here.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
1. Enable developer mode: Settings > Connector > Developer mode 2. Select Developer mode 4. Input name, MCP Server URL, Auth and I believe and Create | | -------------- | ------------------------------------------------------- | name | Qiita | Auth | No Auth | You can create token here.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.