Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.mikusnuz/meta

NPM · @MIKUSNUZ/META-MCP · SCANNED SEP 20

MCP server for Instagram Graph API, Threads API & Meta platform management

Available components

0 this week 84 Trust /100
Trust breakdown (7 categories)

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
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 3581 tokens (~60/item across 59 items; 57 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 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 58 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
Install

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

# add to Claude Code
claude mcp add mikusnuz-meta -- npx -y @mikusnuz/meta-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "mikusnuz-meta": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/meta-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mikusnuz-meta": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/meta-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mikusnuz-meta -- npx -y @mikusnuz/meta-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mikusnuz-meta": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mikusnuz/meta-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mikusnuz-meta --command npx --arg -y --arg @mikusnuz/meta-mcp
# ~/.hermes/config.yaml
mcp_servers:
  mikusnuz-meta:
    command: "npx"
    args: ["-y", "@mikusnuz/meta-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mikusnuz-meta": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@mikusnuz/meta-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mikusnuz-meta -t stdio -c npx -a -y @mikusnuz/meta-mcp
// mcp.json
{
  "mcpServers": {
    "mikusnuz-meta": {
      "command": "npx",
      "args": [
        "-y",
        "@mikusnuz/meta-mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 10 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
Diagnostics

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/@mikusnuz/meta-mcp@2.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 →

MCP tools · 57 exposed · ~3,558 tokens

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 →

Tool Tokens
threads_publish_carousel ~83

Publish a carousel post on Threads with 2-20 images/videos.

NameTypeReqDescription
itemsarrayyesArray of media items
quote_post_idstringID of a post to quote
reply_controlstringWho can reply
textstringCaption text
topic_tagstringTopic tag for the post

No output schema declared.

No examples provided.

threads_publish_image ~133

Publish an image post on Threads. Supports topic tag, quote post, alt text, and spoiler flag.

NameTypeReqDescription
alt_textstringAlt text for accessibility (max 1000 chars)
image_urlstringyesPublic HTTPS URL of the image (JPEG/PNG, max 8MB)
is_spoilerbooleanMark content as spoiler
quote_post_idstringID of a post to quote
reply_controlstringWho can reply
textstringCaption text
topic_tagstringTopic tag for the post

No output schema declared.

No examples provided.

threads_publish_text ~218

Publish a text-only post on Threads. Supports optional link attachment, poll, GIF, topic tag, and quote post.

NameTypeReqDescription
alt_textstringAlt text for accessibility (max 1000 chars)
gif_idstringGIF ID from GIPHY or Tenor
gif_providerstringGIF provider (GIPHY or TENOR). Tenor sunsets March 31, 2026.
is_spoilerbooleanMark content as spoiler
link_attachmentstringURL to attach as a link preview card (max 5 links per post)
poll_optionsarrayPoll options (2-4 choices). Creates a poll attachment.
quote_post_idstringID of a post to quote
reply_controlstringWho can reply
textstringyesPost text (max 500 chars)
topic_tagstringTopic tag for the post (1-50 chars, no periods or ampersands)

No output schema declared.

No examples provided.

threads_publish_video ~146

Publish a video post on Threads. Waits for video processing. Supports topic tag, quote post, alt text, and spoiler flag.

NameTypeReqDescription
alt_textstringAlt text for accessibility (max 1000 chars)
is_spoilerbooleanMark content as spoiler
quote_post_idstringID of a post to quote
reply_controlstringWho can reply
textstringCaption text
topic_tagstringTopic tag for the post
video_urlstringyesPublic 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.

NameTypeReqDescription
image_urlstringOptional image URL to attach
reply_to_idstringyesPost ID to reply to
textstringyesReply text
video_urlstringOptional video URL to attach

No output schema declared.

No examples provided.

threads_search_posts ~128

Search for public Threads posts by keyword or topic tag. Results can be filtered by media type and author.

NameTypeReqDescription
afterstringPagination cursor
author_usernamestringFilter results by author username
limitnumberNumber of results
media_typestringFilter results by media type
qstringyesSearch keyword or query
search_typestringSearch by keyword or topic tag (default: keyword)
sincestringStart date (Unix timestamp)
untilstringEnd date (Unix timestamp)

No output schema declared.

No examples provided.

threads_unhide_reply ~34

Unhide a previously hidden reply on your Threads post.

NameTypeReqDescription
reply_idstringyesReply ID to unhide

No output schema declared.

No examples provided.

Common questions

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 84 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.mikusnuz/meta MCP server expose?

io.github.mikusnuz/meta exposes 57 tools: meta_exchange_token, meta_refresh_token, meta_debug_token, meta_get_app_info, meta_subscribe_webhook, and 52 more. Their descriptions and schemas cost roughly 3,558 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 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.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.