io.github.postmcp/postmcp-mcp-server
NPM · @POSTMCPAI/SERVER · SCANNED SEP 20
Publish and schedule posts to LinkedIn, X, Facebook, Instagram, Threads, Bluesky and YouTube Shorts.
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 96 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 17 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2653 tokens (~165/item across 16 items; 16 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 Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_post_now" implies "publish" 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 16 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.postmcp/postmcp-mcp-server server?
io.github.postmcp/postmcp-mcp-server runs locally as an npm package, launched with npx -y @postmcpai/server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @postmcpai/server
claude mcp add postmcp-postmcp-mcp-server -- npx -y @postmcpai/server
{
"mcpServers": {
"postmcp-postmcp-mcp-server": {
"command": "npx",
"args": [
"-y",
"@postmcpai/server"
]
}
}
} {
"servers": {
"postmcp-postmcp-mcp-server": {
"command": "npx",
"args": [
"-y",
"@postmcpai/server"
]
}
}
} codex mcp add postmcp-postmcp-mcp-server -- npx -y @postmcpai/server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"postmcp-postmcp-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@postmcpai/server"
],
"enabled": true
}
}
} openclaw mcp add postmcp-postmcp-mcp-server --command npx --arg -y --arg @postmcpai/server
mcp_servers:
postmcp-postmcp-mcp-server:
command: "npx"
args: ["-y", "@postmcpai/server"] {
"McpServers": {
"postmcp-postmcp-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@postmcpai/server"
]
}
}
} assistant mcp add postmcp-postmcp-mcp-server -t stdio -c npx -a -y @postmcpai/server
{
"mcpServers": {
"postmcp-postmcp-mcp-server": {
"command": "npx",
"args": [
"-y",
"@postmcpai/server"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 3 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Sept 26 53
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 20 Sept 2026 · Analysed npm/@postmcpai/server@1.0.1
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 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
create_post ~516
Schedule or immediately publish a post to specific connected social profiles. Prefer targetAccounts so the post lands only on the profiles you name. Every targeted profile becomes its own post with its own id, so each can be edited, retried or cancelled on its own - the response lists them all. With publishImmediately, each delivered profile comes back with a `url` to the live copy; pass those on to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text body / commentary of the post. Used for any profile that does not carry its own content. On YouTube the first line becomes the Short's title (cut at 100 characters) and the whole body become… |
| mediaUrl | string | – | Optional public URL of an image/video to attach. Use the mediaUrl returned by generate_image to attach a generated image. Video is uploaded natively to every platform, but each has its own ceiling -… |
| platforms | array | – | Whole platforms to post to. Every connected profile on each platform listed here receives the post - use targetAccounts instead unless that fan-out is what you want. |
| publishImmediately | boolean | – | If true, publishes immediately. Otherwise schedules for later. |
| scheduleDate | string | – | Schedule date in YYYY-MM-DD format (required if publishImmediately is false). |
| scheduleTime | string | – | Schedule time in 24-hour HH:MM format (required if publishImmediately is false). |
| targetAccounts | array | – | The profiles to post to, each with platform and the profileId from get_connected_accounts. Only these profiles receive the post. |
| timezone | string | – | IANA timezone the schedule above is expressed in, e.g. "Asia/Kolkata". Defaults to UTC on the server, so pass the user's own zone whenever a wall-clock time matters. |
| variants | object | – | Per-platform copy, keyed by platform name (or "platform:profileId" for one profile), e.g. { "twitter": "short punchy version", "linkedin": "longer version" }. Overrides content for those destinations. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
delete_post ~80
Cancel and delete a scheduled or failed post from the database.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The Database ObjectId of the post to delete. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
generate_image ~170
Generate an image for a post from a text prompt and return its hosted URL, ready to pass to create_post as mediaUrl. Pass a brandingId from list_brandings to match the workspace's visual style. Spends AI tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| brandingId | string | – | Brand kit id from list_brandings, whose reference image steers the visual style. |
| prompt | string | yes | What the image should show. Be specific about subject, composition, and mood. |
| styleImageUrl | string | – | Public URL of a reference image to steer style directly, instead of a brand kit. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
get_account_health ~95
Report connections whose access token has expired or is about to, and which therefore need the user to reconnect. Check this before scheduling anything far out - a post scheduled onto a dead connection fails silently at publish time.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
get_connected_accounts ~91
List every connected social profile in the workspace with the profileId needed to target it. Call this before creating a post so the post reaches the intended profile rather than every account on a platform.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
get_post ~96
Fetch a single post by id, including per-profile delivery status, the live URL of each published copy, and the error for any profile that failed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The Database ObjectId of the post. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
get_user_info ~83
Retrieve details of the logged-in user including subscription plan, credit balance, AI token count, the active workspace, and the caller's role in it.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
list_brandings ~94
List the workspace's brand kits: tone of voice, audience, keywords, and reference style images. Use one to keep drafted copy on-brand, and pass its id to generate_image for on-brand visuals.
| Name | Type | Req | Description |
|---|---|---|---|
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
list_posts ~178
Retrieve scheduled, published, draft, and failed posts, newest first, with per-profile delivery status. Every profile that received a post carries `url`, the link to the live copy - give the user that link when they ask where a post went. Returns pagination plus counts per status.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Return every matching post in one response, ignoring pagination. |
| limit | number | – | Posts per page. Defaults to 9 on the backend. |
| page | number | – | 1-based page number. Defaults to 1. |
| status | string | – | Only return posts in this state. Defaults to all. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
list_workspaces ~58
List every workspace (project) the user belongs to, with the id to pass as workspaceId, the caller's role, and which one is the default. Call this first whenever the user mentions a client, brand, or workspace by name.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
multicall ~216
Run several PostMCP tools in one request, in the order given. Use it whenever a task needs more than one call - scheduling a week of posts, checking accounts then publishing, or cancelling a handful of posts - instead of one round trip per call. Calls run sequentially and every tool name is validated before anything executes, so a typo cannot leave half a batch written. Cannot nest: a call inside a batch may not itself be multicall.
| Name | Type | Req | Description |
|---|---|---|---|
| calls | array | yes | The calls to run, in order. Between 1 and 20. |
| stopOnError | boolean | – | Stop the batch at the first failing call and skip the rest (default true). Set false to attempt every call regardless - right for independent work like cancelling several posts, wrong when a later ca… |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
preflight_post ~216
Dry-run a post before creating it: checks copy against each platform's character limit, flags profiles that are not connected or need reconnecting, warns when a platform requires media, reports each target's video limit when a video is attached, and reports the credit cost against the workspace balance. Costs nothing and publishes nothing. Run this before create_post whenever the copy is long, carries a link, or targets several platforms.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The post copy to check. |
| mediaUrl | string | – | Media that would be attached, if any. A video URL makes the check report per-platform video limits. |
| platforms | array | – | Whole platforms the post would go to, same shape as create_post. |
| targetAccounts | array | – | Profiles the post would go to, same shape as create_post. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
publish_post_now ~128
Broadcast an existing scheduled post immediately to its platforms. Also the way to retry a failed post: profiles that already received it are skipped, so only the stragglers go out. The returned post carries a `url` per delivered profile - report those links rather than only saying it published.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The Database ObjectId of the post to publish. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
reschedule_post ~197
Move a post to a different date and time, keeping its copy and target profiles. A failed or draft post is re-armed by this and will go out at the new slot; profiles that already received it are not sent to again. Published posts and posts currently publishing cannot be moved.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The Database ObjectId of the post to move. |
| scheduleDate | string | yes | New date in YYYY-MM-DD format. |
| scheduleTime | string | yes | New time in 24-hour HH:MM format. |
| timezone | string | – | IANA timezone the new slot is expressed in, e.g. "Asia/Kolkata". Omit to keep the zone the post was scheduled in. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
reset_stuck_post ~165
Release a post left stuck mid-publish so it can be retried. Profiles that already went out keep their delivered state, so retrying afterwards will not double-post. Only use this on a post whose status is 'processing'; if it started publishing recently the call is refused unless force is true.
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Reset even if the post may still be publishing. Only set this after the user confirms - a run that is genuinely in flight can then deliver twice. |
| id | string | yes | The Database ObjectId of the stuck post. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
update_post ~270
Update the fields (content, target profiles, schedule date/time) of an existing post. To move a post to a different slot without touching anything else, use reschedule_post.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Updated text body of the post. |
| id | string | yes | The Database ObjectId of the post to update. |
| mediaUrl | string | – | Replacement media URL to attach. |
| platforms | array | – | Replacement platform list; each platform expands to all of its connected profiles. |
| scheduleDate | string | – | Updated schedule date in YYYY-MM-DD format. |
| scheduleTime | string | – | Updated schedule time in HH:MM format. |
| status | string | – | Reset status of the post. |
| targetAccounts | array | – | Replacement profile list, each with platform and profileId. Supplying this re-points the post at exactly these profiles. |
| timezone | string | – | IANA timezone the schedule above is expressed in, e.g. "Asia/Kolkata". Defaults to UTC on the server, so pass the user's own zone whenever a wall-clock time matters. |
| workspaceId | string | – | Workspace (project) id to act on, from list_workspaces. Omit to use the caller's default workspace. Always pass this when the user belongs to more than one workspace. |
No output schema declared.
No examples provided.
What is the io.github.postmcp/postmcp-mcp-server server?
io.github.postmcp/postmcp-mcp-server is listed in the public MCP registry as io.github.postmcp/postmcp-mcp-server. Publish and schedule posts to LinkedIn, X, Facebook, Instagram, Threads, Bluesky and YouTube Shorts. This page covers its npm package (@postmcpai/server).
Is the io.github.postmcp/postmcp-mcp-server server safe to use?
io.github.postmcp/postmcp-mcp-server scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.postmcp/postmcp-mcp-server server expose?
io.github.postmcp/postmcp-mcp-server exposes 16 tools: get_user_info, list_workspaces, get_connected_accounts, get_account_health, list_brandings, and 11 more. Their descriptions and schemas cost roughly 2,653 tokens of context every time the server is loaded.
Is the io.github.postmcp/postmcp-mcp-server server still maintained?
io.github.postmcp/postmcp-mcp-server is still listed as active in the MCP registry. We last reached this channel on 20 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.postmcp/postmcp-mcp-server server under?
io.github.postmcp/postmcp-mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.