REMOTE · API.MCP.AI
Instagram for AI agents: publish, read comments and DMs, insights, and engage from your account.
Available components
Last scanned (18 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3835 tokens (~116/item across 33 items; 33 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 34 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.460 → 0.9.467 functional
- 20 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.459 → 0.9.460 functional
- 19 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.454 → 0.9.459 functional
- 18 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.452 → 0.9.454 functional
- 17 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.450 → 0.9.452 functional
- 16 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.449 → 0.9.450 functional
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.442 → 0.9.449 functional
- 14 Nov 26 0
- Stability: 0.97 → pass security
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.9.427 → 0.9.442 functional
- “instagram_post_ig_user_media” added an optional parameter “trial_params” cosmetic
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 21 Nov 2026 · Probed https://api.mcp.ai/p_instagram
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ai | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1bf4d405299e078a0e62ff16cded599b |
| SANs: mcp.ai, *.mcp.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcp.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| mcp.ai. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcp.ai/p_instagram | Verified | 200 | |
| http (plaintext) | http://api.mcp.ai/p_instagram | Inconclusive | 406 |
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 →
authenticate ~99
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | – |
No output schema declared.
No examples provided.
connect ~42
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
instagram_actions_follow ~38
Follow one or more Instagram users by @username. Returns a job_id.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| targets | array | yes | – |
No output schema declared.
No examples provided.
instagram_actions_get_job_status ~61
Get the status/progress/result of a previously started action by its job_id. Bulk support: accepts job_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| job_id | string | yes | – |
| job_ids | array | – | – |
No output schema declared.
No examples provided.
instagram_actions_like ~59
Like one or more Instagram posts, addressed by post URL or shortcode (NOT the numeric media id the official API returns). Returns a job_id; poll instagram_actions_get_job_status.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| posts | array | yes | – |
No output schema declared.
No examples provided.
instagram_actions_like_comment ~75
Like one or more comments. Each comment_id MUST come from instagram_actions_list_comments. The id returned by the official instagram_get_ig_media_comments belongs to a different namespace and is rejected. Returns a job_id; poll instagram_actions_get_job_status.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| comment_ids | array | yes | – |
No output schema declared.
No examples provided.
instagram_actions_list_accounts ~32
List the Instagram accounts connected to this install — id, username, label.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
No output schema declared.
No examples provided.
instagram_actions_list_comments ~77
List the comments on a post, addressed by URL or shortcode. Returns each comment_id in the form that instagram_actions_like_comment accepts. The official API returns a DIFFERENT id that is not accepted there. Returns a job_id; poll instagram_actions_get_job_status.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| posts | array | yes | – |
No output schema declared.
No examples provided.
instagram_actions_list_jobs ~38
List recent action jobs for the connected account, optionally filtered by status.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
instagram_actions_list_stories ~62
List a specific user's currently available stories (read-only, does not mark as seen). Returns a job_id (or the result inline when wait=true).
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| target | string | yes | – |
| wait | boolean | – | – |
No output schema declared.
No examples provided.
instagram_actions_send_message ~75
Send the FIRST direct message to someone who has never messaged this account (the official API cannot do this). One recipient per call, low daily cap. Returns a job_id.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| dry_run | boolean | – | – |
| target | string | yes | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
instagram_actions_unfollow ~40
Unfollow one or more Instagram users by @username. Returns a job_id.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| targets | array | yes | – |
No output schema declared.
No examples provided.
instagram_actions_view_story ~54
Watch (mark as seen) the stories of one or more profiles. Omit `targets` to watch the home tray. Returns a job_id.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| targets | array | – | – |
No output schema declared.
No examples provided.
instagram_create_carousel_container ~179
Create a draft carousel post with multiple images/videos before publishing. Instagram requires carousels to have between 2 and 10 media items. Container creation_ids expire in under 24 hours, so publish promptly after creation. Bulk support: accepts ig_user_ids, location_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| caption | string | – | – |
| child_image_files | array | – | – |
| child_image_urls | array | – | – |
| child_video_files | array | – | – |
| child_video_urls | array | – | – |
| children | array | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| location_id | string | – | – |
| location_ids | array | – | – |
| share_to_feed | boolean | – | – |
No output schema declared.
No examples provided.
instagram_get_conversation ~99
Get details about a specific Instagram DM conversation (participants, etc). Requires a Business or Creator account with Instagram messaging permissions; personal accounts will return permission errors. Newly sent/received messages may take a few seconds to appear in results. Bulk support: accepts conversation_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| conversation_id | string | yes | – |
| conversation_ids | array | – | – |
| graph_api_version | string | – | – |
No output schema declared.
No examples provided.
instagram_get_ig_media ~126
Get a published Instagram Media object (photo, video, story, reel, or carousel). Use when you need to retrieve detailed information about a specific Instagram post including engagement metrics, caption, media URLs, and metadata. NOTE: This action is for published media only. For unpublished container IDs (from INSTAGR… Bulk support: accepts ig_media_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| fields | string | – | – |
| graph_api_version | string | – | – |
| ig_media_id | string | yes | – |
| ig_media_ids | array | – | – |
No output schema declared.
No examples provided.
instagram_get_ig_media_comments ~145
Tool to retrieve comments on an Instagram media object. Use when you need to fetch comments from a specific Instagram post, photo, video, or carousel owned by the connected Business/Creator account. Supports cursor-based pagination for navigating through large comment lists. An empty data array in the response indicat… Bulk support: accepts ig_media_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| after | string | – | – |
| before | string | – | – |
| fields | string | – | – |
| graph_api_version | string | – | – |
| ig_media_id | string | yes | – |
| ig_media_ids | array | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
instagram_get_ig_media_insights ~121
Read media insights. REST response: read result.result.data. Request metric=[views,reach,saved,shares] for views, reach, saves and shares; availability depends on the media type and metric. Bulk support: accepts ig_media_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| breakdown | string | – | – |
| graph_api_version | string | – | – |
| ig_media_id | string | yes | – |
| ig_media_ids | array | – | – |
| metric | array | yes | – |
| period | string | – | – |
No output schema declared.
No examples provided.
instagram_get_ig_user_media ~171
List account media. REST response: read result.result.data and result.result.paging (not result.data). Null engagement fields mean unavailable, not zero; use media insights for saved, shares and views. Bulk support: accepts ig_user_ids, auto_resolve_fb_page_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| after | string | – | – |
| auto_resolve_fb_page_id | boolean | – | – |
| auto_resolve_fb_page_ids | array | – | – |
| before | string | – | – |
| fields | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| limit | number | – | – |
| since | number | – | – |
| until | number | – | – |
No output schema declared.
No examples provided.
instagram_get_user_info ~118
Get Instagram Business Account info including profile details and statistics. Use "me" to query your own authenticated account, or provide the numeric Business Account ID of an account you manage. NOTE: followers_count and follows_count are returned for your own profile (ig_user_id="me"). For other accounts, follower/… Bulk support: accepts ig_user_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
No output schema declared.
No examples provided.
instagram_get_user_insights ~140
Read account insights at result.result.data in REST. An empty data array means insights are unavailable, not zero. It does not by itself establish a follower-count restriction. Bulk support: accepts ig_user_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| breakdown | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| metric | array | – | – |
| metric_type | string | – | – |
| period | string | – | – |
| since | number | – | – |
| timeframe | string | – | – |
| until | number | – | – |
No output schema declared.
No examples provided.
instagram_list_all_conversations ~157
List all Instagram DM conversations for the authenticated user. Requires a Business/Creator account with messaging permissions; personal accounts return empty results. Response conversations are nested under `data.data` — accessing top-level `data` as the final list returns zero items. An empty `data` list is a valid … Bulk support: accepts user_ids, ig_user_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| after | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| limit | number | – | – |
| platform | string | – | – |
| user_id | string | – | – |
| user_ids | array | – | – |
No output schema declared.
No examples provided.
instagram_list_all_messages ~114
List all messages from a specific Instagram DM conversation. Requires a Business or Creator account with messaging permissions; personal accounts return empty results. Response data is nested under data.data (double-wrapped); attachment-only messages may have empty text fields. Bulk support: accepts conversation_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| after | string | – | – |
| conversation_id | string | yes | – |
| conversation_ids | array | – | – |
| graph_api_version | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
instagram_mark_seen ~137
Mark Instagram DM messages as read/seen for a specific user. Sends a 'mark_seen' sender action to indicate messages from the specified recipient have been read. Marking as seen is visible to the other party and changes inbox read state — use with explicit user approval in automated or bulk flows. IMPORTANT LIMITATIONS… Bulk support: accepts ig_user_ids, recipient_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| recipient_id | string | yes | – |
| recipient_ids | array | – | – |
No output schema declared.
No examples provided.
instagram_post_ig_comment_replies ~127
Tool to create a reply to an Instagram comment. Use when you need to reply to a specific comment on an Instagram post owned by a Business or Creator account. The reply must be 300 characters or less, contain at most 4 hashtags and 1 URL, and cannot consist entirely of capital letters. Bulk support: accepts ig_comment_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| graph_api_version | string | – | – |
| ig_comment_id | string | yes | – |
| ig_comment_ids | array | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
instagram_post_ig_user_media ~254
Tool to create a media container for Instagram posts. Use this to create a container for images, videos, Reels, or carousels. This is the first step in Instagram's two-step publishing process - after creating the container, use the media_publish endpoint to publish it. Bulk support: accepts ig_user_ids, location_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| alt_text | string | – | – |
| audio_name | string | – | – |
| caption | string | – | – |
| children | array | – | – |
| cover_url | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| image_file | object | – | – |
| image_url | string | – | – |
| is_carousel_item | boolean | – | – |
| location_id | string | – | – |
| location_ids | array | – | – |
| media_type | string | – | – |
| share_to_feed | boolean | – | – |
| thumb_offset | number | – | – |
| trial_params | object | – | – |
| user_tags | array | – | – |
| video_file | object | – | – |
| video_url | string | – | – |
No output schema declared.
No examples provided.
instagram_post_ig_user_media_publish ~154
Tool to publish a media container to an Instagram Business account. This action automatically waits for the container to finish processing before publishing. Instagram enforces an account-specific content-publishing rate limit over a 24-hour moving window; the exact cap varies by account and should be read live via IN… Bulk support: accepts ig_user_ids, creation_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| creation_id | string | yes | – |
| creation_ids | array | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| max_wait_seconds | number | – | – |
| poll_interval_seconds | number | – | – |
No output schema declared.
No examples provided.
instagram_send_image ~109
Send an image via Instagram DM to a specific user. Each send modifies inbox state; avoid bulk or automated sends without explicit user approval. Bulk support: accepts ig_user_ids, recipient_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| image_url | string | yes | – |
| recipient_id | string | yes | – |
| recipient_ids | array | – | – |
No output schema declared.
No examples provided.
instagram_send_text_message ~167
Send a text message to an Instagram user via DM in an existing conversation. Cannot initiate new DM threads — a prior conversation must exist. Requires an Instagram Business or Creator account with messaging permissions. Fails with error_subcode 2534022 if outside the messaging window; do not retry these failures. Bulk support: accepts ig_user_ids, recipient_ids, reply_to_message_ids for batched execution.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | – |
| graph_api_version | string | – | – |
| ig_user_id | string | – | – |
| ig_user_ids | array | – | – |
| recipient_id | string | yes | – |
| recipient_ids | array | – | – |
| reply_to_message_id | string | – | – |
| reply_to_message_ids | array | – | – |
| text | string | yes | – |
No output schema declared.
No examples provided.
marketplace ~532
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| arguments | string | – | – |
| cancel_comment | string | – | – |
| cancel_reason | string | – | – |
| conversation | string | – | – |
| immediate | boolean | – | – |
| limit | number | – | – |
| mcp_id | string | – | – |
| message | string | – | – |
| prompt_body | string | – | – |
| prompt_category | string | – | – |
| prompt_description | string | – | – |
| prompt_slug | string | – | – |
| prompt_targets | array | – | – |
| prompt_title | string | – | – |
| prompt_tool | string | – | – |
| prompt_vars | string | – | – |
| query | string | – | – |
| report_context | string | – | – |
| request_details | string | – | – |
| request_name | string | – | – |
| tier_slug | string | – | – |
| tool_id | string | – | – |
No output schema declared.
No examples provided.
report_bug ~50
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | – |
| conversation | string | – | – |
| message | string | yes | – |
No output schema declared.
No examples provided.
show_version ~17
Show the current MCP platform and adapter versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
toolkit_info ~37
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Instagram MCP server?
Instagram is a hosted endpoint at https://api.mcp.ai/p_instagram, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mcp.ai
claude mcp add --transport http mcp-dir-instagram-mcp 'https://api.mcp.ai/p_instagram'
What is the Instagram MCP server?
Instagram is an MCP server listed in the public MCP registry as io.github.mcp-dir/instagram-mcp. Instagram for AI agents: publish, read comments and DMs, insights, and engage from your account. This page covers its hosted endpoint (https://api.mcp.ai/p_instagram).
Is the Instagram MCP server safe to use?
Instagram scores 76 out of 100 on VerifyMCP. 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 Instagram MCP server expose?
Instagram exposes 33 tools: instagram_actions_list_accounts, instagram_actions_like, instagram_actions_list_comments, instagram_actions_like_comment, instagram_actions_follow, and 28 more. Their descriptions and schemas cost roughly 3,706 tokens of context every time the server is loaded.
Does the Instagram MCP server require authentication?
No. We connected to Instagram without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Instagram MCP server still maintained?
Instagram is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Instagram MCP server?
VerifyMCP ran 12 checks on Instagram, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Instagram: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.