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.

instapi: Instagram

REMOTE · INSTAPI.CO

Instagram search and posts for AI agents, with images and videos AI-parsed to text.

Available components

0 this week 80 Trust /100

Last scanned (19 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 302 tokens (~75/item across 4 items; 4 tools + 0 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • 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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 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.

  • 27 Oct 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.

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 21 Nov 2026 · Probed https://instapi.co/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=instapi.co CN=YE1,O=Let's Encrypt,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA384 5b8bc9012d28e57136d6fc2664f4f6a2a6d
SANs: *.instapi.co, instapi.co
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of instapi.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
instapi.co. 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://instapi.co/mcp Verified 200
http (plaintext) http://instapi.co/mcp HTTPS enforced 301 https://instapi.co/mcp
MCP tools · 4 exposed · ~274 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
get_started ~34

Free, no auth. Service overview, pricing, current account status, and how to get an API key for the data tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

instagram_search ~59

Search Instagram users, hashtags, and places by keyword. Costs 1 credit. Requires Authorization: Bearer sk_instapi_... on the MCP connection.

NameTypeReqDescription
querystringyesSearch keyword, e.g. a name, brand, or topic

No output schema declared.

No examples provided.

instagram_user_posts ~100

Fetch recent posts for an Instagram username, with images and videos AI-parsed into text descriptions. Costs 1 credit. Requires Authorization: Bearer sk_instapi_.... First fetch for a user can take up to ~60s while media is analyzed; cached users return fast.

NameTypeReqDescription
countinteger–Number of most recent posts, newest first (default 12, max 30)
usernamestringyesInstagram username, without @

No output schema declared.

No examples provided.

instagram_user_profile ~81

Public profile for an Instagram username: bio, links, follower/following/post counts, verified/private/business flags, category. Works for private accounts too. Costs 1 credit (refunded if the user doesn't exist). Requires Authorization: Bearer sk_instapi_....

NameTypeReqDescription
usernamestringyesInstagram username (bare, @handle, or profile URL)

No output schema declared.

No examples provided.

Install

How do I install the instapi: Instagram MCP server?

instapi: Instagram is a hosted endpoint at https://instapi.co/mcp, 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 · instapi.co

# add to Claude Code
claude mcp add --transport http co-instapi-instagram 'https://instapi.co/mcp'
Common questions

What is the instapi: Instagram MCP server?

instapi: Instagram is an MCP server listed in the public MCP registry as co.instapi/instagram. Instagram search and posts for AI agents, with images and videos AI-parsed to text. This page covers its hosted endpoint (https://instapi.co/mcp).

Is the instapi: Instagram MCP server safe to use?

instapi: Instagram scores 80 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 instapi: Instagram MCP server expose?

instapi: Instagram exposes 4 tools: get_started, instagram_search, instagram_user_profile, instagram_user_posts. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.

Does the instapi: Instagram MCP server require authentication?

No. We connected to instapi: Instagram without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the instapi: Instagram MCP server still maintained?

instapi: 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 instapi: Instagram MCP server?

VerifyMCP ran 12 checks on instapi: Instagram, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about instapi: Instagram: Authorization. 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.