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.

Instoryview

REMOTE · INSTORYVIEW.COM

Instagram profiles, follower/following snapshots and changes, with budgeted public lookups.

Available components

0 this week 90 Trust /100

Last scanned (19 hours ago)

Scores higher than 97% 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 Security94
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 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 Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 41% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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 (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 26 +1

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

  • 7 Nov 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.

  • 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
  • 5 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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://instoryview.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=instoryview.com CN=YE1,O=Let's Encrypt,C=US 16 Nov 2026 14 Feb 2027 ECDSA 256 ECDSA-SHA384 6fd144974c2e6f01280ea1e84a901a35bd2
SANs: *.instoryview.com, instoryview.com
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 instoryview.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
instoryview.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://instoryview.com/.well-known/oauth-protected-resource", error="invalid_token", scope="data:read", error_description="Connect PenguinRadar and grant the required data scopes"

Bearer resource_metadata="https://instoryview.com/.well-known/oauth-protected-resource", error="invalid_token", scope="data:read", error_description="Connect PenguinRadar and grant the required data scopes"
Header Value
strict-transport-security max-age=31536000
content-security-policy frame-ancestors 'self' https://superboard.kaitox.ai
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Document https://instoryview.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://instoryview.com/mcp
Authorisation server https://instoryview.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://instoryview.com/mcp Verified 200
http (plaintext) http://instoryview.com/mcp HTTPS enforced 308 https://instoryview.com/mcp
MCP tools · 6 exposed · ~544 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_account ~48

Read stored profile information and follower/following counts. Counts may have a different observation time than lists. No online collection.

NameTypeReqDescription
usernamestringyesInstagram username, optionally prefixed with @.
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

get_account_changes ~126

Read detected changes in your accessible tracking history, default last seven calendar days UTC. detectedAt is detection time, not exact Instagram action time. For the next page send username and cursor; the cursor keeps the list, dates and timezone.

NameTypeReqDescription
cursorstring–meta.nextCursor from the previous page of this same tool and account.
fromstring––
limitinteger––
liststring––
timezonestring––
tostring––
usernamestringyesInstagram username, optionally prefixed with @.
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

list_followers ~80

Read a page of the most recent accessible follower snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.

NameTypeReqDescription
cursorstring–meta.nextCursor from the previous page of this same tool and account.
limitinteger––
usernamestringyesInstagram username, optionally prefixed with @.
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

list_following ~80

Read a page of the most recent accessible following snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.

NameTypeReqDescription
cursorstring–meta.nextCursor from the previous page of this same tool and account.
limitinteger––
usernamestringyesInstagram username, optionally prefixed with @.
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

list_tracking ~61

List your tracked accounts with profile counts and snapshot times. Reads stored data without collection charges.

NameTypeReqDescription
cursorstring–meta.nextCursor from the previous page of this same tool and account.
includeArchivedboolean––
limitinteger––
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

query_public_account ~149

Explicit online query of a public profile or ONE page of followers/following (one source page, usually 25 people). May consume credits: a first list page needs maxCredits of at least 2 (profile + page), a next page 1. Require user authorization for this target, type and maxCredits. Generate and keep idempotencyKey before the first attempt; reuse it with identical arguments when restoring. Never automatically fetch all pages or increase budget.

NameTypeReqDescription
cursorstring––
idempotencyKeystringyes–
maxCreditsintegeryes–
typestringyes–
usernamestringyesInstagram username, optionally prefixed with @.
NameTypeReqDescription
dataobjectyes–
metaobjectyes–

No examples provided.

Install

How do I install the Instoryview MCP server?

Instoryview is a hosted endpoint at https://instoryview.com/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 · instoryview.com

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

What is the Instoryview MCP server?

Instoryview is an MCP server listed in the public MCP registry as io.github.instoryview/instoryview. Instagram profiles, follower/following snapshots and changes, with budgeted public lookups. This page covers its hosted endpoint (https://instoryview.com/mcp).

Is the Instoryview MCP server safe to use?

Instoryview scores 90 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 Instoryview MCP server expose?

Instoryview exposes 6 tools: list_tracking, get_account, list_followers, list_following, get_account_changes, query_public_account. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.

Does the Instoryview MCP server require authentication?

Yes. Instoryview asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Instoryview MCP server still maintained?

Instoryview 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 Instoryview MCP server?

VerifyMCP ran 13 checks on Instoryview, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.