Skip to content

Instoryview MCP server

io.github.instoryview/instoryviewinstoryviewstreamable-httpv0.1.0Scanned

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

6 tools: 1 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 1 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Instoryview MCP server can do

The Instoryview MCP server is published by the GitHub account instoryview. It has 6 tools. It can create or change data (1 tool: query_public_account), but cannot delete data. 5 tools only read.

1 tool reads private data (get_account_changes); 1 tool brings in text other people can write (query_public_account).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 1Claude Code: ask
  • query_public_accountExplicit online query of a public profile or ONE page of followers/following (one source page, usually 25 people).Reads text others write1 finding

    Why it is in this group

    • The name "query_public_account" says "query": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "query_public_account" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "query_public_account" says "query": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • get_accountRead stored profile information and follower/following counts.No findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.
    Description, as the server wrote it
    Read stored profile information and follower/following counts. Counts may have a different observation time than lists. No online collection.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_account_changesRead detected changes in your accessible tracking history, default last seven calendar days UTC.Reads private dataNo findings

    Why it is in this group

    • The name "get_account_changes" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "calendar": it reads calendars.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_followersRead a page of the most recent accessible follower snapshot, or permitted public query cache.No findings

    Why it is in this group

    • The name "list_followers" says "list": a word for reading.
    Description, as the server wrote it
    Read a page of the most recent accessible follower snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_followingRead a page of the most recent accessible following snapshot, or permitted public query cache.No findings

    Why it is in this group

    • The name "list_following" says "list": a word for reading.
    Description, as the server wrote it
    Read a page of the most recent accessible following snapshot, or permitted public query cache. State its asOf and partial coverage. Never collects automatically.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_trackingList your tracked accounts with profile counts and snapshot times.No findings

    Why it is in this group

    • The name "list_tracking" says "list": a word for reading.
    Description, as the server wrote it
    List your tracked accounts with profile counts and snapshot times. Reads stored data without collection charges.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:06 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://instoryview.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://instoryview.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://instoryview.com/mcp: tools/list returned 6 tools to an anonymous client, including query_public_account (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "query_public_account" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "query_public_account" says "query": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http instoryview https://instoryview.com/mcp
claude mcp add --transport http instoryview https://instoryview.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__instoryview__list_tracking",
      "mcp__instoryview__get_account",
      "mcp__instoryview__list_followers",
      "mcp__instoryview__list_following",
      "mcp__instoryview__get_account_changes"
    ],
    "ask": [
      "mcp__instoryview__query_public_account"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as instoryview. Review it before you use it.

Capability tags behind 2 rules
  • mcp__instoryview__get_account_changes private-data
  • mcp__instoryview__query_public_account untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.instoryview/instoryview/verify?hash=2ccd882d9856124b552996c5fdbe7970cb6a26db0cba70250d530d49fdd772fe" | jq -e '.changed == false'

Pinned hash 2ccd882d9856, from Nov 20, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.instoryview/instoryview/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.instoryview/instoryview
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.instoryview/instoryview.svg)](https://radar.anlyon.com/servers/io.github.instoryview/instoryview)

Source: MCP Registry. Synced Oct 21, 2026, 18:36 UTC.

Instoryview MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Instoryview MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Instoryview MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Instoryview MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Instoryview MCP server have?

6 tools: 1 write, 5 read. query_public_account, list_tracking, get_account, list_followers, list_following and get_account_changes.

Does the Instoryview MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Instoryview MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Instoryview MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.