Chirpie
NPM · @CHIRPIE/MCP · 2 COMPONENTS · SCANNED SEP 20
Post, schedule, and track social posts on X, Bluesky, LinkedIn, Instagram and more from AI agents.
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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1594 tokens (~75/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 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 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "chirpie_delete_post" 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 21 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 Chirpie MCP server?
Chirpie runs locally as an npm package, launched with npx -y @chirpie/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 · @chirpie/mcp
claude mcp add firefloco-chirpie -- npx -y @chirpie/mcp
{
"mcpServers": {
"firefloco-chirpie": {
"command": "npx",
"args": [
"-y",
"@chirpie/mcp"
]
}
}
} {
"servers": {
"firefloco-chirpie": {
"command": "npx",
"args": [
"-y",
"@chirpie/mcp"
]
}
}
} codex mcp add firefloco-chirpie -- npx -y @chirpie/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"firefloco-chirpie": {
"type": "local",
"command": [
"npx",
"-y",
"@chirpie/mcp"
],
"enabled": true
}
}
} openclaw mcp add firefloco-chirpie --command npx --arg -y --arg @chirpie/mcp
mcp_servers:
firefloco-chirpie:
command: "npx"
args: ["-y", "@chirpie/mcp"] {
"McpServers": {
"firefloco-chirpie": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@chirpie/mcp"
]
}
}
} assistant mcp add firefloco-chirpie -t stdio -c npx -a -y @chirpie/mcp
{
"mcpServers": {
"firefloco-chirpie": {
"command": "npx",
"args": [
"-y",
"@chirpie/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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 6 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 5 Sept 26 54
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/@chirpie/mcp@1.0.21
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 →
chirpie_analytics ~66
Get analytics (likes, reposts, replies, etc.) for a published post on X, Bluesky, LinkedIn, Threads, Mastodon, Instagram or Facebook. Note: Telegram does not expose analytics.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | Post ID to get analytics for |
No output schema declared.
No examples provided.
chirpie_connect_bluesky ~65
Connect a Bluesky account using an app password (create one at https://bsky.app/settings/app-passwords).
| Name | Type | Req | Description |
|---|---|---|---|
| app_password | string | yes | Bluesky app password |
| identifier | string | yes | Bluesky handle (e.g. user.bsky.social) |
No output schema declared.
No examples provided.
chirpie_connect_facebook ~37
Start the OAuth flow for a Facebook Pages account. Returns an authorization_url the user must open in a browser to complete the connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_connect_instagram ~36
Start the OAuth flow for a Instagram account. Returns an authorization_url the user must open in a browser to complete the connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_connect_linkedin ~37
Start the OAuth flow for a LinkedIn account. Returns an authorization_url the user must open in a browser to complete the connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_connect_mastodon ~47
Start the OAuth flow for a Mastodon account on a specific instance.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_url | string | yes | Mastodon instance URL (e.g. https://mastodon.social) |
No output schema declared.
No examples provided.
chirpie_connect_telegram ~75
Connect a Telegram bot. Create a bot with @BotFather on Telegram, then pass the bot token and the chat ID (user, group, or channel).
| Name | Type | Req | Description |
|---|---|---|---|
| bot_token | string | yes | Bot token from @BotFather |
| chat_id | string | yes | Target chat ID (user, group, or channel) |
No output schema declared.
No examples provided.
chirpie_connect_threads ~35
Start the OAuth flow for a Threads account. Returns an authorization_url the user must open in a browser to complete the connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_connect_x ~37
Start the OAuth flow for a X/Twitter account. Returns an authorization_url the user must open in a browser to complete the connection.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_create_key ~64
Create a new Chirpie API key. Returns the full key once — store it securely. Keys are prefixed `chirpie_sk_` and never re-shown by the API.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Friendly name for the key (default: 'Default') |
No output schema declared.
No examples provided.
chirpie_delete_post ~37
Delete a post. Also deletes it from the platform if it was already published.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Post ID to delete |
No output schema declared.
No examples provided.
chirpie_get_post ~26
Get a single post by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Post ID |
No output schema declared.
No examples provided.
chirpie_get_x_keys_status ~43
Check whether the user has registered their own X developer app. Returns configuration status and the callback URI to register on the X app — never the client secret.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_list_accounts ~36
List connected social accounts (X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook and Telegram).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_list_keys ~31
List the user's Chirpie API keys (prefix + metadata; the full key is only shown on creation).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_list_posts ~61
List recent posts. Filter by status or account.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Filter by account ID |
| limit | number | – | Max results (default 20) |
| status | string | – | Filter: draft, scheduled, published, failed |
No output schema declared.
No examples provided.
chirpie_post ~381
Create a post on X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, or Telegram with optional media. Posts immediately or at a scheduled time. Note: Instagram REQUIRES media. X posts whose text contains a link are billed at $0.25 each on paid plans and are rejected on the Free plan (x_link_posts_require_paid_plan); X accounts connected with your own X API keys are exempt.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | Account ID to post from (X, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, or Telegram) |
| media_urls | array | – | Public image URLs. X supports images + video (max 4); Bluesky supports images only (~1MB each, max 4); LinkedIn supports images (JPEG, PNG, GIF up to 8MB each, max 4). Threads supports one image per… |
| schedule_at | string | – | ISO 8601 datetime to schedule the post. Must carry a timezone — '2026-04-01T14:00:00Z' or '2026-04-01T16:00:00+02:00' — and is normalized to UTC. Scheduled posts publish within ~5 minutes of this tim… |
| text | string | yes | Post text (max 280 chars for standard X, 25,000 for X Premium, 300 for Bluesky, 3,000 for LinkedIn, 500 for Threads, 500 for Mastodon, 2,200 for Instagram, 63,206 for Facebook, 4,096 for Telegram) |
No output schema declared.
No examples provided.
chirpie_remove_x_keys ~44
Remove the user's own X developer app. X accounts connected through it stop refreshing until the keys are re-added or the accounts are reconnected through Chirpie's app.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
chirpie_revoke_key ~41
Revoke a Chirpie API key by its ID. Revocation is permanent and immediate.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | API key ID to revoke |
No output schema declared.
No examples provided.
chirpie_set_x_keys ~153
Register the user's OWN X developer app (from developer.x.com) so their X accounts connect through it and post against their X API credits instead of Chirpie's. Link posts from accounts connected this way are not surcharged. After setting keys, the user must add the returned redirect_uri as a callback URI on their X app and then reconnect each X account (chirpie_connect_x) to move it onto their app.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | OAuth 2.0 Client ID from developer.x.com |
| client_secret | string | yes | OAuth 2.0 Client Secret from developer.x.com. Stored encrypted and never returned. |
| label | string | – | Optional human-readable name for the app |
No output schema declared.
No examples provided.
chirpie_thread ~242
Create a thread (multiple posts) on X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, or Telegram. X, Bluesky, Threads, Mastodon, and Telegram support native reply threading. Others degrade gracefully to standalone posts. On X, each post in the thread whose text contains a link is billed at $0.25 on paid plans; on the Free plan such threads are rejected (x_link_posts_require_paid_plan). X accounts connected with your own X API keys are exempt.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | yes | Account ID to post from (X, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, or Telegram). Some platforms degrade to standalone posts. |
| posts | array | yes | Array of posts in the thread |
| schedule_at | string | – | ISO 8601 datetime to schedule the thread. Must carry a timezone — '2026-04-01T14:00:00Z' or '2026-04-01T16:00:00+02:00' — and is normalized to UTC. Scheduled threads publish within ~5 minutes of this… |
No output schema declared.
No examples provided.
What is the Chirpie MCP server?
Chirpie is an MCP server listed in the public MCP registry as io.github.Firefloco/chirpie. Post, schedule, and track social posts on X, Bluesky, LinkedIn, Instagram and more from AI agents. This page covers its npm package (@chirpie/mcp).
Is the Chirpie MCP server safe to use?
Chirpie 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 Chirpie MCP server expose?
Chirpie exposes 21 tools: chirpie_post, chirpie_thread, chirpie_list_posts, chirpie_get_post, chirpie_delete_post, and 16 more. Their descriptions and schemas cost roughly 1,594 tokens of context every time the server is loaded.
Is the Chirpie MCP server still maintained?
Chirpie 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 Chirpie MCP server under?
Chirpie declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.