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.

com.jojapi/instagram

REMOTE · MCP.JOJAPI.COM

Instagram: Instagram public data scraper API for search, users, posts, hashtags, locations and more.

Available components

0 this week 71 Trust /100

Last scanned (16 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Web Scraping

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 Usability56
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1061 tokens (~48/item across 22 items; 22 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 Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 26% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 22 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 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • 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
  • 28 Sept 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
  • 25 Sept 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
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
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://mcp.jojapi.com/instagram

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.jojapi.com CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 4fdef8b174aa7f510e6f8de60526c223
SANs: mcp.jojapi.com
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 mcp.jojapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
jojapi.com. 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://mcp.jojapi.com/instagram Verified 200
http (plaintext) http://mcp.jojapi.com/instagram HTTPS enforced 301 https://mcp.jojapi.com/instagram
MCP tools · 22 exposed · ~973 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_user_details_by_username ~36

User Details (by username) Group: User. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_user_posts_by_username ~44

User Posts (by username) Group: User. Billing per call: 1 Credits.

NameTypeReqDescription
pagination_tokenstring––
usernamestring––

No output schema declared.

No examples provided.

get_user_stories_by_username ~37

User Stories (by username) Group: User. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_v2_location_posts ~58

v2 / Location Posts Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
location_idstring–You can find Location IDs from the v2 / Search endpoint
max_idstring––

No output schema declared.

No examples provided.

get_v2_post_details_by_shortcode ~42

v2 / Post Details by Shortcode Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
shortcodestring––

No output schema declared.

No examples provided.

get_v2_search ~49

v2 / Search Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
contextstring–blended,user,place,hashtag
querystring––

No output schema declared.

No examples provided.

get_v2_tag_posts ~52

v2 / Tag Posts Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
max_idstring––
tag_namestring–Tag name without number sign (#)

No output schema declared.

No examples provided.

get_v2_user_details_by_id ~42

v2 / User Details by ID Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
user_idstring––

No output schema declared.

No examples provided.

get_v2_user_details_by_username ~41

v2 / User Details by Username Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_v2_user_following_hashtags ~43

v2 / User Following Hashtags Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
user_idstring––

No output schema declared.

No examples provided.

get_v2_user_posts ~58

v2 / User Posts Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
countstring–Max number of results
cursorstring–Cursor token
user_idstring––

No output schema declared.

No examples provided.

get_v2_user_tagged_posts ~61

v2 / User Tagged Posts Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
countstring–Max number of results
cursorstring–Cursor token
user_idstring––

No output schema declared.

No examples provided.

get_v3_1_user_details_by_username ~44

User Details by Username (more detailed) Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_v3_user_details_by_id ~38

User Details by ID Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
idstring––

No output schema declared.

No examples provided.

get_v3_user_details_by_username ~38

User Details By Username Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_v3_user_stories ~35

User Stories Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
idstring––

No output schema declared.

No examples provided.

get_v4_1_user_posts ~50

v4.1 / user-posts Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
maxIdstring––
usernamestring––

No output schema declared.

No examples provided.

get_v4_highlight_stories ~46

v4 / highlight-stories Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
highlight_idstring–Get from User Highlights endpoint

No output schema declared.

No examples provided.

get_v4_user_details_by_username ~42

v4 / user-details-by-username Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_v4_user_highlights ~40

v4 / user-highlights Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
user_idstring––

No output schema declared.

No examples provided.

get_v4_user_posts ~38

v4 / user-posts Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

get_v4_user_stories ~39

v4 / user-stories Group: Deprecated Endpoints. Billing per call: 1 Credits.

NameTypeReqDescription
usernamestring––

No output schema declared.

No examples provided.

Install

How do I install the com.jojapi/instagram MCP server?

com.jojapi/instagram is a hosted endpoint at https://mcp.jojapi.com/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 · mcp.jojapi.com

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

What is the com.jojapi/instagram MCP server?

com.jojapi/instagram is an MCP server listed in the public MCP registry as com.jojapi/instagram. Instagram: Instagram public data scraper API for search, users, posts, hashtags, locations and more. This page covers its hosted endpoint (https://mcp.jojapi.com/instagram).

Is the com.jojapi/instagram MCP server safe to use?

com.jojapi/instagram scores 71 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 com.jojapi/instagram MCP server expose?

com.jojapi/instagram exposes 22 tools: get_user_details_by_username, get_user_posts_by_username, get_user_stories_by_username, get_v3_user_details_by_username, get_v3_user_stories, and 17 more. Their descriptions and schemas cost roughly 973 tokens of context every time the server is loaded.

Does the com.jojapi/instagram MCP server require authentication?

No. We connected to com.jojapi/instagram without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.jojapi/instagram MCP server still maintained?

com.jojapi/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 com.jojapi/instagram MCP server?

VerifyMCP ran 12 checks on com.jojapi/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 com.jojapi/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.