Tistory MCP (Unofficial)
PYPI · TISTORY-MCP
Unofficial MCP server for Tistory blogs: publish, edit, drafts, images. Private by default.
Available components
Last scanned (15 hours ago)
Scores higher than 61% of PyPI servers
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 2 of 39 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to jangsejong/tistory-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2010 tokens (~182/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed pypi/tistory-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | jangsejong/tistory-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/jangsejong/tistory-mcp/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 3533991737 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6c52391c53aac5e3e6f3aca97256f26edc78c3fef886c3eb5bb632e31032a6ab |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 39 packages
| Packages resolved | 39 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tistory_delete_post Delete a post (글 삭제) ~84
Permanently delete a post. Cannot be undone. Ask the user to confirm in chat, then call with confirm=true.
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL of the post to delete |
| confirm | boolean | – | Must be true to actually delete. Ask the user in chat first |
| post_id | string | yes | Post number (글 번호) |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_fetch_public_posts Fetch public posts via RSS (공개 글 RSS) ~82
Fetch the latest public posts of any Tistory blog from its RSS feed. No login needed.
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
| include_content | boolean | – | Include each item's RSS description (body HTML) |
| limit | integer | – | Max items to return |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_get_categories List categories (카테고리) ~67
Return the category tree flattened to id / name / parent id. Use the integer id here as `category` when publishing or updating (names are not accepted).
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_get_post Get a post (글 조회) ~127
Return one post's metadata (from the admin list) and its body HTML (from the post page). Works for private posts with the saved session. The body is the skin-rendered HTML, not the original markdown (Tistory keeps no markdown). To edit, write the new body yourself and send it with tistory_update_post rather than echoing content_html back.
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
| post_id | string | yes | Post number (글 번호), digits only |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_list_posts List posts (글 목록) ~144
List posts from the admin side (includes private and protected posts), one page at a time. Bodies are not included — use tistory_get_post for the body.
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
| category | integer | – | Category id filter; -3 = all categories |
| keyword | string | – | Server-side search keyword; empty string = all posts |
| page | integer | – | Page number, 1-based |
| search_type | string | – | Where to search the keyword: post title, body, or tag |
| visibility | string | – | Visibility filter |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_publish_post Publish a new post (새 글 발행) ~314
Create a NEW post. Every call creates a new post — this is not a draft and not an update. Do not retry after an error or timeout without checking tistory_list_posts first, or the post may be duplicated. Defaults to private so the user can review it before switching to public with tistory_update_post. Rate-limited (default 60 s apart, 20 per day).
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | – | – | attachment_ref of every image used in content (from tistory_upload_image) |
| blog_url | string | yes | Target blog host or URL — required to prevent mis-publishing |
| category | integer | – | Category id from tistory_get_categories; 0 = none |
| content | string | yes | Post body. Markdown by default (converted to HTML by the tool). For images, paste the `substitution` from tistory_upload_image verbatim |
| content_format | string | – | 'markdown' (default) or 'html' |
| password | – | – | Password for visibility='protected' |
| post_type | string | – | 'post' (default) or a static 'page' |
| slogan | string | – | URL slug; empty = generated from the title by the server |
| tags | – | – | Tags (태그), one per item, without '#' and without commas |
| title | string | yes | Post title (제목) |
| visibility | string | – | Default 'private' (비공개). Use 'public' only when the user explicitly asks; 'protected' needs password |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_save_draft Save autosave draft (자동저장 초안) ~174
Write a draft into the editor's single autosave slot. No post is created. The next time the user opens the editor it offers to restore this draft. There is only one slot, so saving again overwrites the previous draft. For several reviewable drafts, publish with visibility='private' instead.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | – | – | attachment_ref of images used in content |
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
| category | integer | – | Category id; 0 = none |
| content | string | yes | Draft body (markdown by default) |
| content_format | string | – | 'markdown' (default) or 'html' |
| tags | – | – | Tags, one per item |
| title | string | yes | Draft title |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_session_init Log in to Tistory (로그인) ~208
Open a browser for the Kakao login (카카오 로그인 + 카카오톡 승인) and save the cookies. Blocks until the user finishes or timeout_sec passes — tell the user to look for the browser window and approve the KakaoTalk push before calling. The KakaoTalk 2-factor approval cannot be automated. Once saved, other tools work without a browser until the session expires (it can be as short as an hour or so); call again when a tool reports an expired session.
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
| cdp_url | – | – | CDP address of a browser that is already running with --remote-debugging-port, e.g. http://127.0.0.1:9222. Use when no browser window can be shown (WSL, SSH, containers) |
| timeout_sec | integer | – | How long to wait for the login (seconds) |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_session_status Session status (세션 상태) ~70
Report whether a saved session exists, when it was saved and when it expires. Also makes one admin API call to tell whether it is live right now (valid/expired).
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_update_post Update a post (글 수정) ~271
Update an existing post. The body must be sent in full (the server does not merge). Title, category, visibility and slug keep their current values when omitted; tags are kept by reading them from the post page (pass [] to clear). Rate-limited together with publish.
| Name | Type | Req | Description |
|---|---|---|---|
| attachments | – | – | attachment_ref of images used in the new content |
| blog_url | string | yes | Blog host or URL of the post to update |
| category | – | – | New category id; omit to keep the current one |
| content | string | yes | The complete new body — the server overwrites the whole post. Do not echo content_html from tistory_get_post; write the new body yourself |
| content_format | string | – | Default 'html'. Set 'markdown' when sending markdown, or it is posted as raw text |
| password | – | – | Password for visibility='protected' |
| post_id | string | yes | Post number (글 번호) |
| slogan | – | – | New URL slug; omit to keep |
| tags | – | – | New tags; omit to keep the current tags (read from the post page), pass [] to clear |
| title | – | – | New title; omit to keep the current one |
| visibility | – | – | New visibility; omit to keep the current one. 'public' makes it live |
Structured output declared, but exposes no named fields.
No examples provided.
tistory_upload_image Upload an image (이미지 업로드) ~184
Upload an image and return `substitution` (paste into the body) and `attachment_ref`. Put `substitution` verbatim where the image goes, and pass `attachment_ref` in `attachments` when publishing/updating — otherwise the image is garbage-collected after about 15 days. Do not put the returned URL into the body directly.
| Name | Type | Req | Description |
|---|---|---|---|
| blog_url | string | yes | Blog host or URL (블로그 주소). e.g. myblog.tistory.com |
| file_path | string | yes | Local image path (png/jpg/jpeg/gif/webp, up to 20MB) |
| height | – | – | Pixel height; read from the file header if omitted |
| style | string | – | Alignment: alignCenter (default), alignLeft, alignRight, widthOrigin |
| width | – | – | Pixel width; read from the file header if omitted |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Tistory MCP (Unofficial) server?
Tistory MCP (Unofficial) runs locally as a PyPI package, launched with uvx tistory-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · tistory-mcp
claude mcp add jangsejong-tistory-mcp -- uvx tistory-mcp
What is the Tistory MCP (Unofficial) server?
Tistory MCP (Unofficial) is listed in the public MCP registry as io.github.jangsejong/tistory-mcp. Unofficial MCP server for Tistory blogs: publish, edit, drafts, images. Private by default. This page covers its PyPI package (tistory-mcp).
Is the Tistory MCP (Unofficial) server safe to use?
Tistory MCP (Unofficial) scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Tistory MCP (Unofficial) server expose?
Tistory MCP (Unofficial) exposes 11 tools: tistory_session_init, tistory_session_status, tistory_get_categories, tistory_list_posts, tistory_get_post, and 6 more. Their descriptions and schemas cost roughly 1,725 tokens of context every time the server is loaded.
Is the Tistory MCP (Unofficial) server still maintained?
Tistory MCP (Unofficial) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Tistory MCP (Unofficial) server under?
Tistory MCP (Unofficial) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.