io.github.bitsandtea/postking-mcp
NPM · POSTKING-MCP · 2 COMPONENTS · SCANNED SEP 30
PostKing MCP server for managing brands, generating posts, scheduling content, and publishing blogs.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 84 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 32233 tokens (~146/item across 220 items; 220 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 25 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_theme" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 221 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.bitsandtea/postking-mcp server?
io.github.bitsandtea/postking-mcp runs locally as an npm package, launched with npx -y postking-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · postking-mcp
claude mcp add bitsandtea-postking-mcp -- npx -y postking-mcp
{
"mcpServers": {
"bitsandtea-postking-mcp": {
"command": "npx",
"args": [
"-y",
"postking-mcp"
]
}
}
} {
"servers": {
"bitsandtea-postking-mcp": {
"command": "npx",
"args": [
"-y",
"postking-mcp"
]
}
}
} codex mcp add bitsandtea-postking-mcp -- npx -y postking-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bitsandtea-postking-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"postking-mcp"
],
"enabled": true
}
}
} openclaw mcp add bitsandtea-postking-mcp --command npx --arg -y --arg postking-mcp
mcp_servers:
bitsandtea-postking-mcp:
command: "npx"
args: ["-y", "postking-mcp"] {
"McpServers": {
"bitsandtea-postking-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"postking-mcp"
]
}
}
} assistant mcp add bitsandtea-postking-mcp -t stdio -c npx -a -y postking-mcp
{
"mcpServers": {
"bitsandtea-postking-mcp": {
"command": "npx",
"args": [
"-y",
"postking-mcp"
]
}
}
} 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.
- 30 Sept 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 −3
- Stability: pass → 0.77 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 30 Sept 2026 · Analysed npm/postking-mcp@1.1.7
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| Stale | 31 |
| 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 →
template_list ~193
List the brand's saved content templates. short {id,title,category}; medium adds platforms,isFavorite,bodyPreview (160 chars); full = raw. Pass category to filter (e.g. 'hook', 'cta', 'thread'). Results are ordered by isFavorite desc, then usageCount desc.
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | – | Brand ID (defaults to active brand) |
| category | string | – | Filter templates by category (e.g. 'hook', 'cta', 'thread'). Omit for all. |
| detail | string | – | Verbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "short". Lists… |
No output schema declared.
No examples provided.
template_pick ~186
RE-RANKER: AI scores a caller-supplied list of candidate templates and picks the N best-fitting ones for a given theme or topic. This tool does NOT read stored templates server-side — the caller must supply the candidates explicitly (e.g. call template_list first, then pass the results here). Synchronous — no polling needed. Pass the templates array from template_list (full detail) as candidates. Returns { templateIds } — an ordered array of the winning template IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | – | Brand ID (defaults to active brand) |
| count | integer | yes | How many templates to pick (1–20). |
| templates | array | yes | Candidate templates to evaluate. Use template_list with detail='full' and pass the relevant fields. |
| theme | string | yes | The topic or theme the agent should optimise for (e.g. 'AI productivity tips'). |
No output schema declared.
No examples provided.
template_update ~146
Update an existing content template. All fields are optional — only supplied fields are changed. Use isFavorite=true/false to toggle favorite status.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | New template body. |
| brandId | string | – | Brand ID (defaults to active brand) |
| category | string|null | – | New category label. |
| example | string|null | – | New example post. |
| isFavorite | boolean | – | Set true to favorite, false to un-favorite. |
| pattern | string|null | – | New pattern description. |
| platforms | array | – | Updated platform list. |
| templateId | string | yes | ID of the content template to update. |
| title | string | – | New title. |
No output schema declared.
No examples provided.
trends_list ~224
Browse top-trending posts (with deconstructions) for a niche + platform. Account/niche-scoped — NOT tied to a specific brand. Each post includes hook, template, pattern, and virality reason from the deconstruction. The crawler runs every 3 days; use days=3 (default) for the freshest batch. Supported niches: ai-saas, marketing, web3. Supported platforms: x.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Look-back window in days (1–30). Defaults to 3 (the freshest crawler batch). |
| limit | integer | – | Maximum number of posts to return (1–50). Defaults to 20. |
| niche | string | – | Niche to filter by. One of: ai-saas, marketing, web3. Defaults to ai-saas. |
| platform | string | – | Platform to filter by. Currently only 'x' is supported. Defaults to x. |
| sort | string | – | Sort order: 'engagement' = highest engagement score first (default); 'recent' = newest crawled first. |
No output schema declared.
No examples provided.
update_blog_article ~163
Edit a blog article — title, content, excerpt, SEO fields, status, author, or category. Set status='published' to make it live on your PostKing blog.
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | Blog article ID |
| authorId | string | – | Author ID (from list_blog_authors) |
| brandId | string | – | Brand ID (uses active brand if omitted) |
| categoryId | string | – | Category ID (from list_blog_categories) |
| content | string | – | Full post body (HTML or markdown) |
| excerpt | string | – | – |
| metaDescription | string | – | – |
| metaTitle | string | – | – |
| status | string | – | 'published' makes it live on your blog |
| title | string | – | – |
No output schema declared.
No examples provided.
update_publication ~158
Update an existing blog publication's metadata — title, description, domain/routing config, or layout. Only the fields you pass are changed (partial update). Distinct from create_publication (which creates a new one). publicationId comes from list_publications or list_blogs.
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | – | Brand ID (uses active brand if omitted) |
| description | string | – | Publication description / tagline |
| domainId | string | – | Custom domain ID to route this publication under |
| layout | string | – | – |
| pathPrefix | string | – | – |
| publicationId | string | yes | Blog publication ID (from list_publications or list_blogs) |
| routingType | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
upload_asset ~299
Upload an asset to the brand library from a local file path or base64-encoded content. Prefer filePath for local files: the server reads and base64-encodes the file itself, avoiding truncation of large base64 strings over the tool_call boundary. fileBase64 is still supported for remote/inline use where no local path is available. For large files over the remote/HTTP transport, a single fileBase64 string can get truncated crossing the LLM→tool_call boundary — use the chunked flow instead: upload_asset_begin → upload_asset_chunk (× N) → upload_asset_finish. Provide exactly one of filePath or fileBase64. Returns the new asset ID and URL.
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | – | Brand ID (defaults to active brand) |
| description | string | – | – |
| fileBase64 | string | – | Base64-encoded file content. Use filePath instead when the file is local. |
| fileName | string | – | Original file name including extension, e.g. 'logo.png'. Derived from filePath if omitted. |
| filePath | string | – | Absolute path to a local file to upload. Preferred over fileBase64 for local files. |
| mimeType | string | – | MIME type of the file, e.g. 'image/png' |
| name | string | – | Display name for the asset |
| tags | array | – | Tags to apply, e.g. ['logo', 'brand'] |
No output schema declared.
No examples provided.
upload_asset_abort ~38
Cancel a chunked asset upload in progress and discard any buffered chunks.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadId | string | yes | Upload ID returned by upload_asset_begin |
No output schema declared.
No examples provided.
upload_asset_begin ~249
Start a chunked asset upload. Use this instead of upload_asset's fileBase64 param for large files over the remote/HTTP transport, where a single large base64 string can get truncated crossing the LLM→tool_call boundary. Flow: upload_asset_begin (once) → upload_asset_chunk (once per chunk, in order) → upload_asset_finish (once). Returns an uploadId that expires after 10 minutes of inactivity.
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | – | Brand ID (defaults to active brand) |
| description | string | – | – |
| fileName | string | yes | Original file name including extension, e.g. 'logo.png'. |
| fileSize | number | – | Raw decoded byte length of the original file. Recommended — enables truncation/corruption detection at finish time. |
| mimeType | string | – | MIME type of the file, e.g. 'image/png' |
| name | string | – | Display name for the asset |
| sha256 | string | – | Sha256 hex digest of the original file's decoded bytes. Recommended — enables end-to-end integrity verification at finish time. |
| tags | array | – | Tags to apply, e.g. ['logo', 'brand'] |
No output schema declared.
No examples provided.
upload_asset_chunk ~94
Send one chunk of a base64-encoded file previously started with upload_asset_begin. Chunks must be sent in order, index starting at 0, with no gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| fileBase64Chunk | string | yes | A slice of the full base64 string for this chunk |
| index | integer | yes | 0-based, contiguous chunk index |
| uploadId | string | yes | Upload ID returned by upload_asset_begin |
No output schema declared.
No examples provided.
upload_asset_finish ~59
Finalize a chunked asset upload: reassembles the buffered chunks, verifies integrity, and uploads the asset to the brand library. Returns the new asset ID and URL.
| Name | Type | Req | Description |
|---|---|---|---|
| uploadId | string | yes | Upload ID returned by upload_asset_begin |
No output schema declared.
No examples provided.
verify_domain ~48
Check DNS verification for a domain. Returns whether it's pointing to PostKing servers and what A record is needed if not.
| Name | Type | Req | Description |
|---|---|---|---|
| domainId | string | yes | Domain ID to verify (from list_domains) |
No output schema declared.
No examples provided.
vibe_edit_landing_page ~128
Use AI to edit a landing page based on natural-language instructions. Returns an operationId — poll with get_vibe_edit_status or get_job until status is 'completed'. Optionally limit to a specific scope ('headline' | 'cta' | 'full') or a single sectionId.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | yes | Natural-language edit instructions, e.g. 'Make the CTA more urgent' |
| scope | string | – | Restrict edits to a specific section type |
| sectionId | string | – | Specific section ID to edit |
| slug | string | yes | Landing page slug |
No output schema declared.
No examples provided.
view_asset ~146
View details of a single asset by ID. Supports detail param: short=id+type+name, medium=key fields, full=raw.
| Name | Type | Req | Description |
|---|---|---|---|
| assetId | string | yes | Asset ID from list_assets |
| brandId | string | – | Brand ID (defaults to active brand) |
| detail | string | – | Verbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "full". Lists d… |
No output schema declared.
No examples provided.
view_landing_page ~154
Fetch a landing page by slug. detail='full' (default) returns full data JSONB; 'medium' returns summary + sectionKeys/sectionWordCounts; 'short' returns id/slug/name/status. Section bodies and rendered HTML appear only at full.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Verbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "full". Lists d… |
| slug | string | yes | Landing page slug |
No output schema declared.
No examples provided.
view_lp_draft ~144
View the unpublished draft of a landing page. detail='full' (default) includes full versionData; 'medium' adds sectionKeys/sectionWordCounts; 'short' is id/slug/name/status only.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Verbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "full". Lists d… |
| slug | string | yes | Landing page slug |
No output schema declared.
No examples provided.
view_lp_version ~143
View a specific LP version. detail='full' (default) returns full data; 'medium' adds sectionKeys/sectionWordCounts.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Verbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "full". Lists d… |
| slug | string | yes | Landing page slug |
| versionId | integer | yes | Numeric version ID from list_lp_versions |
No output schema declared.
No examples provided.
view_side_page ~171
View a side page including sections and rendered HTML. detail='full' (default) includes rendered HTML and full overrides; 'medium' gives summary + overrideSectionKeys; 'short' gives id/slug/name/type/isPublished. Rendered HTML appears only at full.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Verbosity of returned item(s): "short" = id + primary label + status (cheap list scan); "medium" = key summary fields + counts (a useful glance); "full" = the complete object. Default "full". Lists d… |
| sideKey | string | yes | Side page key (from list_side_pages) |
| slug | string | yes | Parent landing page slug |
No output schema declared.
No examples provided.
web_search ~170
Perform a live, real-time web search and get back a raw answer with sources — for questions like 'find me the top 10 places to share/index my MCP', 'what's the latest on X', or 'where can I find Y'. Distinct from search_web_images, which only returns images — this tool returns a synthesized text answer plus the sources it drew from (each with title, url, and optional description), and optionally related follow-up prompts. Results are returned as-is (unsummarized) — pass the answer and sources straight through to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| brandId | string | – | Brand ID (defaults to active brand) |
| prompt | string | yes | The search query or question to answer via live web search, e.g. 'top 10 places to share/index my MCP' |
No output schema declared.
No examples provided.
whoami ~29
Return the profile of the currently authenticated PostKing user (email, plan, credit balance, token source).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.bitsandtea/postking-mcp server?
io.github.bitsandtea/postking-mcp is listed in the public MCP registry as io.github.bitsandtea/postking-mcp. PostKing MCP server for managing brands, generating posts, scheduling content, and publishing blogs. This page covers its npm package (postking-mcp).
Is the io.github.bitsandtea/postking-mcp server safe to use?
io.github.bitsandtea/postking-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 September 2026. It declares no install or post-install scripts. 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 io.github.bitsandtea/postking-mcp server expose?
io.github.bitsandtea/postking-mcp exposes 220 tools: login_start, login_complete, logout, whoami, list_brands, and 215 more. Their descriptions and schemas cost roughly 31,224 tokens of context every time the server is loaded.
Is the io.github.bitsandtea/postking-mcp server still maintained?
io.github.bitsandtea/postking-mcp is still listed as active in the MCP registry. We last reached this channel on 30 September 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 io.github.bitsandtea/postking-mcp server under?
io.github.bitsandtea/postking-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.