# Planify (npm · @planifyapps/mcp)

Schedule and publish social posts to Twitter, Instagram, LinkedIn, Pinterest, Bluesky and more.

- Trust score: 59/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-07

## Components

- npm · `@planifyapps/mcp`: 59/100 (this document), [markdown](https://verifymcp.io/servers/com-planifyapps-planify/planifyapps-mcp.md), [page](https://verifymcp.io/servers/com-planifyapps-planify/planifyapps-mcp)

## Channel facts

- Registry: `npm`
- Package: `@planifyapps/mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-07.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### Claude

```bash
claude mcp add com-planifyapps-planify -- npx -y @planifyapps/mcp
```

### Codex

```bash
codex mcp add com-planifyapps-planify -- npx -y @planifyapps/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-planifyapps-planify": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@planifyapps/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-planifyapps-planify --command npx --arg -y --arg @planifyapps/mcp
```

### Hermes

```yaml
mcp_servers:
  com-planifyapps-planify:
    command: "npx"
    args: ["-y", "@planifyapps/mcp"]
```

### Other

```json
{
  "mcpServers": {
    "com-planifyapps-planify": {
      "command": "npx",
      "args": [
        "-y",
        "@planifyapps/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-07 (score 59, +29)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-08-06 (score 30)

First indexed and scored.

## MCP tools (7)

### `planify_me` (~49 tokens)

Planify: account and plan

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.

### `planify_list_channels` (~54 tokens)

Planify: list connected channels

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.

### `planify_channel_settings` (~91 tokens)

Planify: what this channel accepts

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.

Input parameters:

- `channel_id` (string, required): From planify_list_channels.

### `planify_channel_trigger` (~126 tokens)

Planify: run a channel lookup

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.

Input parameters:

- `channel_id` (string, required): From planify_list_channels.
- `data` (object): Arguments, matching that tool's input schema. Twitter communities needs { query }.
- `method_name` (string, required): E.g. "boards" for Pinterest, "communities" for Twitter.

### `planify_next_slot` (~106 tokens)

Planify: next free posting slot

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.

Input parameters:

- `after` (string): ISO-8601. Search from later than now.
- `channel_id` (string, required): From planify_list_channels.
- `count` (integer): How many slots to return. Default 1.

### `planify_upload_media_from_url` (~78 tokens)

Planify: add an image or video from a URL

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.

Input parameters:

- `urls` (array, required): One or more publicly reachable http(s) URLs.

### `planify_create_post` (~302 tokens)

Planify: create a post (draft, scheduled, or publish now)

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.

Input parameters:

- `channel_ids` (array): Required when content is a string.
- `content` (required): 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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-planifyapps-planify/planifyapps-mcp#diagnostics

## Score history

- 2026-08-07: 59
- 2026-08-06: 30

## Links

- npm package: https://www.npmjs.com/package/@planifyapps/mcp
- Socket report: https://socket.dev/npm/package/@planifyapps/mcp
- Website: https://planifyapps.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-planifyapps-planify/planifyapps-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-planifyapps-planify/planifyapps-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-planifyapps-planify/planifyapps-mcp