Planify
NPM · @PLANIFYAPPS/MCP · SCANNED AUG 7
Schedule and publish social posts to Twitter, Instagram, LinkedIn, Pinterest, Bluesky and more.
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1029 tokens (~147/item across 7 items; 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @planifyapps/mcp
claude mcp add com-planifyapps-planify -- npx -y @planifyapps/mcp
codex mcp add com-planifyapps-planify -- npx -y @planifyapps/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-planifyapps-planify": {
"type": "local",
"command": [
"npx",
"-y",
"@planifyapps/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-planifyapps-planify --command npx --arg -y --arg @planifyapps/mcp
mcp_servers:
com-planifyapps-planify:
command: "npx"
args: ["-y", "@planifyapps/mcp"] {
"mcpServers": {
"com-planifyapps-planify": {
"command": "npx",
"args": [
"-y",
"@planifyapps/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.
- 7 Aug 26 +29
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 6 Aug 26 30
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 7 Aug 2026 · Analysed npm/@planifyapps/[email protected]
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Deprecated | 95 |
| Stale | 29 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
planify_channel_settings Planify: what this channel accepts ~91
Read this before writing a post. Returns, for one specific channel: the character limit, how much media it accepts, whether media is required, the rules that decide whether publishing succeeds, a JSON Schema for its platform settings, and any lookups it supports. Per channel, not per platform, because a Facebook Page and a profile differ.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | From planify_list_channels. |
No output schema declared.
No examples provided.
planify_channel_trigger Planify: run a channel lookup ~126
Fetches values that cannot be guessed — Pinterest boards, Twitter communities. Which lookups exist for a channel is listed as tools[].method_name by planify_channel_settings, and each says which post setting its result fills in. A Pinterest pin cannot be created without running the boards lookup first.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_id | string | yes | From planify_list_channels. |
| data | object | – | Arguments, matching that tool's input schema. Twitter communities needs { query }. |
| method_name | string | yes | E.g. "boards" for Pinterest, "communities" for Twitter. |
No output schema declared.
No examples provided.
planify_create_post Planify: create a post (draft, scheduled, or publish now) ~302
Creates a post. Defaults to a draft. content as a string sends the same copy to every channel in channel_ids. As an array of { channel_id, content } it gives per-platform copy — which is what you want when the same idea needs 280 characters on Twitter and 2,200 on Instagram. Call planify_channel_settings first and honour what it returns, including any required platform_settings such as a Pinterest board_id. type "now" publishes immediately and cannot be undone. Only use it when the user has confirmed this specific post should go out now; otherwise create a draft or schedule it.
| Name | Type | Req | Description |
|---|---|---|---|
| channel_ids | array | – | Required when content is a string. |
| content | – | yes | One string for all channels, or per-channel objects for different copy. |
| idempotency_key | string | – | Send a stable value so a retry cannot double-post. Generate one per intended post. |
| media_urls | array | – | From planify_upload_media_from_url. |
| platform_settings | object | – | Keyed by platform: { pinterest: { board_id } }. Shape comes from planify_channel_settings. |
| scheduled_at | string | – | UTC ISO-8601. Required when type is "schedule". planify_next_slot suggests one. |
| thread | array | – | Post as a thread where supported. Part one becomes the body. |
| type | string | – | Default draft. "now" needs the posts:publish scope and the user's confirmation. |
No output schema declared.
No examples provided.
planify_list_channels Planify: list connected channels ~54
Connected social accounts, with the channel id needed by every other tool. Channels the plan does not cover are included but marked available: false — so "not connected" and "not on your plan" stay distinguishable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
planify_me Planify: account and plan ~49
The plan, the permissions this API key holds, and quota remaining. Call this first if a later call fails with a payment or permission error — it says exactly what the key can and cannot do.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
planify_next_slot Planify: next free posting slot ~106
The next free time from the weekly posting schedule the user already set, skipping slots already taken. Prefer this over choosing a time yourself. Returns slot: null when the channel has no schedule — then ask the user, or send an explicit scheduled_at.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | ISO-8601. Search from later than now. |
| channel_id | string | yes | From planify_list_channels. |
| count | integer | – | How many slots to return. Default 1. |
No output schema declared.
No examples provided.
planify_upload_media_from_url Planify: add an image or video from a URL ~78
Planify downloads the file and returns media_urls to pass to planify_create_post. Use this when the image already exists at a public URL — the usual case after generating one. The URL must be publicly reachable; private and internal addresses are refused.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | One or more publicly reachable http(s) URLs. |
No output schema declared.
No examples provided.