Publishing Pitfalls

● Active

io.github.dpcnsg/pub-pitfalls-mcp

53 verified book/e-book registration blocks (KDP, Korean ISBN, Kyobo, Payhip) with fixes.

Category
Content & Publishing
Version
0.1.0
Registry
active
Published
11/14/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 17, 2026

Looks healthy: Publishing Pitfalls is maintained, open source.

Maintained
Active
Last commit 8 days ago (Nov 14, 2026), 0 open issues.
Official registry
Active
Published as io.github.dpcnsg/pub-pitfalls-mcp in the official MCP registry, version 0.1.0.
Source
Open source, MIT
Public repository under the MIT licence, 0 stars, 0 forks.
Runs
On your machine
A local mcpb package started by your client; it can reach whatever your user account can.
Credentials
None declared
The registry entry declares no required environment variables.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 17, 2026
Stars
0
Forks
0
Last push
Nov 14, 2026
License
MIT

JavaScript

From the README

pub-pitfalls-mcp 한국어 1인 출판사가 책·전자책을 판매처에 등록하다 막힌 실제 사례(53건)를 AI 에이전트가 조회하는 MCP 서버입니다. 대상: Amazon KDP, 국립중앙도서관 ISBN, 교보문고 전자책 파트너, 크몽, Payhip, Google Play Books, Netlify. 설치·실행 (Node.js 18 이상, 외부 패키지 없음) MCP 클라이언트 설정 예: {"command": "node", "args": [" /index.js"]} 도구 3개 • search_pitfalls(query, platform?) : 증상 문구(한국어·영어)로 상위 5건 검색 • get_pitfall(id) : 사례 1건 • list_platforms() : 플랫폼별 건수 고지 이 자료는 1인 출판사가 2026년 10~11월 실제로 겪은 기록이며 각 플랫폼 정책은 바뀔 수 있습니다. 공식 안내를 함께 확인하세요. 라이선스 코드(index.js 등)는 MIT, 사례 자료(data/pitfalls.json)는 CC BY 4.0 — 출처 "victorview pub-pitfalls"를 밝히면 누구나 쓸 수 있습니다. 새로 막힌 사례·바뀐 정책 제보는 Issues로 받습니다. English An MCP server that lets AI agents look up 53 real cases where a one-person publisher got blocked while registering books and e-books (Amazon KDP, Korean National Library ISBN, Kyobo eBook partner, Kmong, Payhip, Google Play Books, Netlify). Case text is in Korean. Install / run (Node.js 18+, no dependencies): node index.js starts the stdio server; node test.js runs the tests. Tools: searchpitfalls(query, platform?) returns the top 5 matches for a Korean or English symptom text; getpitfall(id) returns one case; list_platforms() returns case counts per platform. Notice This data records what a one-person publisher actually experienced in Oct-Nov 2026. Platform policies may change; always check the official guidance too. License Code: MIT. Case data (data/pitfalls.json): CC BY 4.0 — credit "victorview pub-pitfalls".…

Read the full README on GitHub →

The most-starred Content & Publishing servers in the index, with their live-check result.

ServerStarsLast pushLive check
AIHOT11,205Nov 2026Working
OpenPost919Nov 2026Needs sign-in
Frontman for WordPress728Nov 2026Needs sign-in
xbbg MCP703Nov 2026Local / not checked
xbbg MCP703Nov 2026Local / not checked

Publishing Pitfalls: questions people ask

Is Publishing Pitfalls a remote or a local MCP server?
According to its entry in the official MCP registry, Publishing Pitfalls ships as a local package (mcpb) that your client starts on your machine.
Is Publishing Pitfalls safe to use?
Looks healthy: Publishing Pitfalls is maintained, open source. In detail — maintained: Active; official registry: Active; source: Open source, MIT; runs: On your machine; credentials: None declared. Serverdex check of Nov 17, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Publishing Pitfalls still maintained?
Active: the repository's last commit 8 days ago. Last push Nov 14, 2026, 0 GitHub stars, MIT licence. Read from GitHub on Nov 17, 2026.
How do I add Publishing Pitfalls to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Content & Publishing →

Add the badge to your site

Show visitors that Publishing Pitfalls is listed here — it’s also the link we check for a free listing.

Publishing Pitfalls — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-dpcnsg-pub-pitfalls-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Publishing Pitfalls — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Publishing Pitfalls — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-dpcnsg-pub-pitfalls-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).