# Instoryview (remote · instoryview.com)

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

- Trust score: 90/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `instoryview.com`: 90/100 (this document), [markdown](https://verifymcp.io/servers/instoryview-instoryview/instoryview.md), [page](https://verifymcp.io/servers/instoryview-instoryview/instoryview)

## Channel facts

- Endpoint: `https://instoryview.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 576 tokens (~96/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 41% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "instoryview-instoryview": {
      "url": "https://instoryview.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "instoryview-instoryview": {
      "type": "http",
      "url": "https://instoryview.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.instoryview-instoryview]
url = "https://instoryview.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "instoryview-instoryview": {
      "type": "remote",
      "url": "https://instoryview.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add instoryview-instoryview --url 'https://instoryview.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  instoryview-instoryview:
    url: "https://instoryview.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "instoryview-instoryview": {
      "Transport": "http",
      "Url": "https://instoryview.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add instoryview-instoryview -t streamable-http -u 'https://instoryview.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "instoryview-instoryview": {
      "type": "http",
      "url": "https://instoryview.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-12 (score 90, 0)

- [security] Stability: 0.97 → pass

### 2026-11-11 (score 90, +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.

### 2026-11-09 (score 89, +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.

### 2026-11-07 (score 88, +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.

### 2026-11-06 (score 87, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 87, +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.

### 2026-11-02 (score 86, +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.

### 2026-10-31 (score 85, +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.

## MCP tools (6)

### `list_tracking` (~61 tokens)

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

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `includeArchived` (boolean)
- `limit` (integer)

Output parameters:

- `data` (object)
- `meta` (object)

### `get_account` (~48 tokens)

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

Input parameters:

- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `list_followers` (~80 tokens)

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

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `limit` (integer)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `list_following` (~80 tokens)

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

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `limit` (integer)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `get_account_changes` (~126 tokens)

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.

Input parameters:

- `cursor` (string): meta.nextCursor from the previous page of this same tool and account.
- `from` (string)
- `limit` (integer)
- `list` (string)
- `timezone` (string)
- `to` (string)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

### `query_public_account` (~149 tokens)

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.

Input parameters:

- `cursor` (string)
- `idempotencyKey` (string, required)
- `maxCredits` (integer, required)
- `type` (string, required)
- `username` (string, required): Instagram username, optionally prefixed with @.

Output parameters:

- `data` (object)
- `meta` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/instoryview-instoryview/instoryview#diagnostics

## Score history

- 2026-11-21: 90
- 2026-11-20: 90
- 2026-11-19: 90
- 2026-11-18: 90
- 2026-11-17: 90
- 2026-11-16: 90
- 2026-11-15: 90
- 2026-11-14: 90
- 2026-11-13: 90
- 2026-11-12: 90
- 2026-11-11: 90
- 2026-11-10: 89
- 2026-11-09: 89
- 2026-11-08: 88
- 2026-11-07: 88
- 2026-11-06: 87
- 2026-11-05: 87
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 86
- 2026-11-01: 85
- 2026-10-31: 85
- 2026-10-30: 84
- 2026-10-29: 84
- 2026-10-28: 83
- 2026-10-27: 83
- 2026-10-26: 82
- 2026-10-25: 82
- 2026-10-24: 81
- 2026-10-23: 81

## 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.

## Links

- Remote endpoint: https://instoryview.com/mcp
- Website: https://instoryview.com/docs/plugins
- Changelog RSS feed: https://verifymcp.io/servers/instoryview-instoryview/instoryview.xml
- Changelog JSON feed: https://verifymcp.io/servers/instoryview-instoryview/instoryview/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/instoryview-instoryview/instoryview.json
- HTML version of this page: https://verifymcp.io/servers/instoryview-instoryview/instoryview
