io.github.mikusnuz/meta
NPM · @MIKUSNUZ/META-MCP
MCP server for Instagram Graph API, Threads API & Meta platform management
Available components
Last scanned (6 hours ago)
Scores higher than 61% of npm servers
Category Marketing and SEO
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 16 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 5255 tokens (~77/item across 68 items; 66 tools + 2 resources), lean.Pass
- 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 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 13 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ig_publish_photo" 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 67 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
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.
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 19 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- Package version: 2.2.0 → 2.2.2 functional
- 18 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 5 Nov 2026 · Analysed npm/@mikusnuz/meta-mcp@2.2.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
threads_get_profile_posts ~118
Get a public profile's posts by username (Profile Discovery). Requires threads_profile_discovery permission; with standard access, only @meta, @threads, @instagram, and @facebook are queryable.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Pagination cursor |
| limit | number | – | Number of results |
| since | string | – | Start date (ISO 8601 or Unix timestamp) |
| until | string | – | End date (ISO 8601 or Unix timestamp) |
| username | string | yes | Threads username to look up (without @) |
No output schema declared.
No examples provided.
threads_get_publishing_limit ~33
Check how many posts you can still publish within the current 24-hour window (max 250 posts/day).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
threads_get_replies ~65
Get replies (conversation) for a specific Threads post.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Pagination cursor |
| limit | number | – | Number of replies |
| post_id | string | yes | Threads post ID to get replies for |
| reverse | boolean | – | Reverse chronological order |
No output schema declared.
No examples provided.
threads_get_user_insights ~100
Get account-level Threads insights (views, likes, replies, reposts, quotes, clicks, followers, follower demographics).
| Name | Type | Req | Description |
|---|---|---|---|
| breakdown | string | – | Required when requesting follower_demographics |
| metric | string | yes | Comma-separated metrics: views,likes,replies,reposts,quotes,followers_count,follower_demographics |
| since | string | – | Start date (Unix timestamp) |
| until | string | – | End date (Unix timestamp) |
No output schema declared.
No examples provided.
threads_get_user_threads ~80
Get all threads published by the user (alias for threads_get_posts with user context).
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Pagination cursor |
| limit | number | – | Number of results |
| since | string | – | Start date (ISO 8601 or Unix timestamp) |
| until | string | – | End date (ISO 8601 or Unix timestamp) |
No output schema declared.
No examples provided.
threads_hide_reply ~38
Hide a reply on your Threads post. Hidden replies are still visible if directly accessed.
| Name | Type | Req | Description |
|---|---|---|---|
| reply_id | string | yes | Reply ID to hide |
No output schema declared.
No examples provided.
threads_lookup_profile ~75
Look up a public Threads user's profile by username (Profile Discovery). Requires threads_profile_discovery permission and target must have >=100 followers; with standard access, only @meta, @threads, @instagram, and @facebook are queryable.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | Threads username to look up (exact match, without @) |
No output schema declared.
No examples provided.
threads_manage_pending_reply ~64
Approve or ignore a pending reply on a post with reply approvals enabled. Ignored replies can still be approved later.
| Name | Type | Req | Description |
|---|---|---|---|
| approve | boolean | yes | true to approve and publish the reply, false to ignore it |
| reply_id | string | yes | Pending reply ID |
No output schema declared.
No examples provided.
threads_publish_carousel ~166
Publish a carousel post on Threads with 2-20 images/videos.
| Name | Type | Req | Description |
|---|---|---|---|
| crossreshare_to_ig | boolean | – | Also share this post to the user's linked Instagram account as a Story |
| crossreshare_to_ig_dark_mode | boolean | – | Cross-share to Instagram Stories in dark mode |
| enable_reply_approvals | boolean | – | Require replies to be approved before they're published |
| items | array | yes | Array of media items |
| location_id | string | – | Location ID to tag (from threads_search_locations) |
| quote_post_id | string | – | ID of a post to quote |
| reply_control | string | – | Who can reply |
| text | string | – | Caption text |
| topic_tag | string | – | Topic tag for the post |
No output schema declared.
No examples provided.
threads_publish_image ~216
Publish an image post on Threads. Supports topic tag, quote post, alt text, and spoiler flag.
| Name | Type | Req | Description |
|---|---|---|---|
| alt_text | string | – | Alt text for accessibility (max 1000 chars) |
| crossreshare_to_ig | boolean | – | Also share this post to the user's linked Instagram account as a Story |
| crossreshare_to_ig_dark_mode | boolean | – | Cross-share to Instagram Stories in dark mode |
| enable_reply_approvals | boolean | – | Require replies to be approved before they're published |
| image_url | string | yes | Public HTTPS URL of the image (JPEG/PNG, max 8MB) |
| is_spoiler | boolean | – | Mark content as spoiler |
| location_id | string | – | Location ID to tag (from threads_search_locations) |
| quote_post_id | string | – | ID of a post to quote |
| reply_control | string | – | Who can reply |
| text | string | – | Caption text |
| topic_tag | string | – | Topic tag for the post |
No output schema declared.
No examples provided.
threads_publish_text ~430
Publish a text-only post on Threads. Supports optional link attachment, poll, GIF, topic tag, and quote post.
| Name | Type | Req | Description |
|---|---|---|---|
| alt_text | string | – | Alt text for accessibility (max 1000 chars) |
| crossreshare_to_ig | boolean | – | Also share this post to the user's linked Instagram account as a Story |
| crossreshare_to_ig_dark_mode | boolean | – | Cross-share to Instagram Stories in dark mode |
| enable_reply_approvals | boolean | – | Require replies to be approved before they're published. Not compatible with ghost posts. |
| gif_id | string | – | GIF ID from GIPHY (id field from GIPHY's API response). GIPHY is currently the only supported GIF provider (Tenor was sunset March 31, 2026). |
| is_ghost_post | boolean | – | Create a ghost post (auto-archived after 24h). Text-only, and per Meta's docs the only other feature supported alongside it is is_spoiler — do not combine with polls, GIFs, links, topic tags, locatio… |
| is_spoiler | boolean | – | Mark content as spoiler |
| link_attachment | string | – | URL to attach as a link preview card (max 5 links per post) |
| location_id | string | – | Location ID to tag (from threads_search_locations) |
| poll_options | array | – | Poll options (2-4 choices, each 1-25 characters). Creates a poll attachment. |
| quote_post_id | string | – | ID of a post to quote |
| reply_control | string | – | Who can reply |
| spoiler_ranges | array | – | Up to 10 exact spoiler ranges within text. If omitted and is_spoiler=true, the entire text is marked as a spoiler. |
| text | string | yes | Post text (max 500 chars) |
| topic_tag | string | – | Topic tag for the post (1-50 chars, no periods or ampersands) |
No output schema declared.
No examples provided.
threads_publish_video ~229
Publish a video post on Threads. Waits for video processing. Supports topic tag, quote post, alt text, and spoiler flag.
| Name | Type | Req | Description |
|---|---|---|---|
| alt_text | string | – | Alt text for accessibility (max 1000 chars) |
| crossreshare_to_ig | boolean | – | Also share this post to the user's linked Instagram account as a Story |
| crossreshare_to_ig_dark_mode | boolean | – | Cross-share to Instagram Stories in dark mode |
| enable_reply_approvals | boolean | – | Require replies to be approved before they're published |
| is_spoiler | boolean | – | Mark content as spoiler |
| location_id | string | – | Location ID to tag (from threads_search_locations) |
| quote_post_id | string | – | ID of a post to quote |
| reply_control | string | – | Who can reply |
| text | string | – | Caption text |
| topic_tag | string | – | Topic tag for the post |
| video_url | string | yes | Public HTTPS URL of the video (MP4/MOV, max 1GB, up to 5 min) |
No output schema declared.
No examples provided.
threads_reply ~66
Reply to a Threads post or another reply.
| Name | Type | Req | Description |
|---|---|---|---|
| image_url | string | – | Optional image URL to attach |
| reply_to_id | string | yes | Post ID to reply to |
| text | string | yes | Reply text |
| video_url | string | – | Optional video URL to attach |
No output schema declared.
No examples provided.
threads_search_locations ~85
Search for locations to tag in a Threads post, by query text or by coordinates. Provide q, or latitude+longitude, or both.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | – | Latitude of a location (must be used with longitude) |
| longitude | number | – | Longitude of a location (must be used with latitude) |
| q | string | – | Query text to search for locations by |
No output schema declared.
No examples provided.
threads_search_posts ~173
Search for public Threads posts by keyword or topic tag via the /keyword_search endpoint. Results can be filtered by media type and author.
| Name | Type | Req | Description |
|---|---|---|---|
| author_username | string | – | Filter results to an exact author username (no @) |
| limit | number | – | Number of results (default 25, max 100) |
| media_type | string | – | Filter results by media type |
| q | string | yes | Search keyword or topic tag to query |
| search_mode | string | – | Treat q as a keyword or a topic tag (default: KEYWORD) |
| search_type | string | – | Return most popular or most recent results (default: TOP) |
| since | string | – | Start date (Unix timestamp, must be >= 1688540400) |
| until | string | – | End date (Unix timestamp) |
No output schema declared.
No examples provided.
threads_unhide_reply ~34
Unhide a previously hidden reply on your Threads post.
| Name | Type | Req | Description |
|---|---|---|---|
| reply_id | string | yes | Reply ID to unhide |
No output schema declared.
No examples provided.
How do I install the io.github.mikusnuz/meta MCP server?
io.github.mikusnuz/meta runs locally as an npm package, launched with npx -y @mikusnuz/meta-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 · @mikusnuz/meta-mcp
claude mcp add mikusnuz-meta -- npx -y @mikusnuz/meta-mcp
What is the io.github.mikusnuz/meta MCP server?
io.github.mikusnuz/meta is an MCP server listed in the public MCP registry as io.github.mikusnuz/meta. MCP server for Instagram Graph API, Threads API & Meta platform management. This page covers its npm package (@mikusnuz/meta-mcp).
Is the io.github.mikusnuz/meta MCP server safe to use?
io.github.mikusnuz/meta scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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.mikusnuz/meta MCP server expose?
io.github.mikusnuz/meta exposes 66 tools: meta_exchange_token, meta_refresh_token, meta_debug_token, meta_get_app_info, meta_subscribe_webhook, and 61 more. Their descriptions and schemas cost roughly 5,232 tokens of context every time the server is loaded.
Is the io.github.mikusnuz/meta MCP server still maintained?
io.github.mikusnuz/meta is still listed as active in the MCP registry. We last reached this channel on 5 November 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.mikusnuz/meta MCP server under?
io.github.mikusnuz/meta declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.