INSSIST
NPM · @INSSIST/MCP
Drive your own logged-in Instagram session via the INSSIST extension: read, publish, DMs, analytics.
Available components
Last scanned (14 hours ago)
Scores higher than 72% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 43 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7683 tokens (~128/item across 60 items; 60 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- All 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 61 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.93 functional
- 18 Oct 26 +1
- Stability: 0.97 → pass security
- 16 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.
- 14 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.
- 13 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 12 Oct 26 −3
- Stability: pass → 0.80 functional
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 5 Nov 2026 · Analysed npm/@inssist/mcp@2.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
note_set Note set ~133
Set the logged-in account's Note. ≤60-chars. Atop the DM inbox avatar, gone in 24h. Pushes you to the top of the DM list. Empty text clears it. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| instant | boolean | – | Optional. Skip INSSIST's action pacing and run now — use only when the user asked for an unspaced or burst action. |
| text | string | – | Note text (≤60 chars). Empty or omitted clears the current note. |
No output schema declared.
No examples provided.
notifications_list Notifications list ~125
Recent notifications: comments, likes, follows, mentions. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| instant | boolean | – | Optional. Skip INSSIST's action pacing and run now — use only when the user asked for an unspaced or burst action. |
| limit | number | – | Max notifications to return, 1-200, default 50. Newest first. |
| type | string | – | Filter: all (default), comments, likes, follows or mentions. |
No output schema declared.
No examples provided.
peers_export Peers export ~98
Export a full followers/following list to a CSV file; returns the file path. Run peers_scan first for other accounts. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| type | string | – | List: followers (default) or following. |
| username | string | – | Account to export, without @. Omit for the logged-in account. |
No output schema declared.
No examples provided.
peers_report Peers report ~168
Read a page of a collected followers/following list (from/limit). Own account uses stored data, richer (adds `mutual`, `followedOn`; `mutual` is null when not checked yet); other accounts need peers_scan first. Whole list: peers_export. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| from | number | – | Zero-based offset into the list, default 0. |
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| limit | number | – | Page size, 1-1000, default 100. |
| type | string | – | List: followers (default) or following. |
| username | string | – | Account whose list to read, without @. Omit for the logged-in account. |
No output schema declared.
No examples provided.
peers_scan Peers scan ~114
Start collecting an account's followers or following. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| instant | boolean | – | Optional. Skip INSSIST's action pacing and run now — use only when the user asked for an unspaced or burst action. |
| type | string | – | Collect followers (default) or following. |
| username | string | – | Account to scan, without @. Omit for the logged-in account. |
No output schema declared.
No examples provided.
profile_update Profile update ~127
Edit the logged-in account's bio (the text under the name on the profile). Own account only; changing bio links is not supported (app-only). Other profile fields are left untouched. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| bio | string | yes | The new bio text. Pass an empty string to clear it. |
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| instant | boolean | – | Optional. Skip INSSIST's action pacing and run now — use only when the user asked for an unspaced or burst action. |
No output schema declared.
No examples provided.
story_viewers Story viewers ~129
See who viewed one of your active stories. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Resume token from a previous call's nextCursor. Omit for the first page. |
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| instant | boolean | – | Optional. Skip INSSIST's action pacing and run now — use only when the user asked for an unspaced or burst action. |
| storyId | string | yes | Story media id, from ig_fetch_stories. Must be one of your own active stories. |
No output schema declared.
No examples provided.
unfollowers_export Unfollowers export ~58
Export the full list of accounts that unfollowed you to a CSV file; returns the path. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
No output schema declared.
No examples provided.
unfollowers_report Unfollowers report ~79
List accounts that unfollowed you in the last 7 days, from stored scan data. Run unfollowers_scan to refresh; poll `scanning` and `lastScanOn` for freshness. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
No output schema declared.
No examples provided.
unfollowers_scan Unfollowers scan ~106
Start an unfollower scan for the logged-in account. Runs in the background through INSSIST's paced follower crawl; poll unfollowers_report for progress and results. (Requires INSSIST PRO.)
| Name | Type | Req | Description |
|---|---|---|---|
| instance | string | – | Optional. Browser instance id from account_info; defaults to the active one. |
| instant | boolean | – | Optional. Skip INSSIST's action pacing and run now — use only when the user asked for an unspaced or burst action. |
No output schema declared.
No examples provided.
How do I install the INSSIST MCP server?
INSSIST runs locally as an npm package, launched with npx -y @inssist/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @inssist/mcp
claude mcp add inssist-inssist-mcp -- npx -y @inssist/mcp
What is the INSSIST MCP server?
INSSIST is an MCP server listed in the public MCP registry as io.github.inssist/inssist-mcp. Drive your own logged-in Instagram session via the INSSIST extension: read, publish, DMs, analytics. This page covers its npm package (@inssist/mcp).
Is the INSSIST MCP server safe to use?
INSSIST scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 INSSIST MCP server expose?
INSSIST exposes 60 tools: account_info, account_switch, antibot_export, antibot_report, antibot_scan, and 55 more. Their descriptions and schemas cost roughly 7,651 tokens of context every time the server is loaded.
Is the INSSIST MCP server still maintained?
INSSIST is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the INSSIST MCP server under?
INSSIST declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the INSSIST MCP server?
VerifyMCP ran 16 checks on INSSIST, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.