InsightSocial
NPM · INSIGHTSOCIAL · SCANNED OCT 5
Live public data from Instagram, TikTok, LinkedIn, YouTube, X and 20 more networks, via one key.
Available components
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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to insightsocial/cli). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
- Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the InsightSocial MCP server?
InsightSocial runs locally as an npm package, launched with npx -y insightsocial. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · insightsocial
claude mcp add app-insightsocial-insightsocial -- npx -y insightsocial
{
"mcpServers": {
"app-insightsocial-insightsocial": {
"command": "npx",
"args": [
"-y",
"insightsocial"
]
}
}
} {
"servers": {
"app-insightsocial-insightsocial": {
"command": "npx",
"args": [
"-y",
"insightsocial"
]
}
}
} codex mcp add app-insightsocial-insightsocial -- npx -y insightsocial
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-insightsocial-insightsocial": {
"type": "local",
"command": [
"npx",
"-y",
"insightsocial"
],
"enabled": true
}
}
} openclaw mcp add app-insightsocial-insightsocial --command npx --arg -y --arg insightsocial
mcp_servers:
app-insightsocial-insightsocial:
command: "npx"
args: ["-y", "insightsocial"] {
"McpServers": {
"app-insightsocial-insightsocial": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"insightsocial"
]
}
}
} assistant mcp add app-insightsocial-insightsocial -t stdio -c npx -a -y insightsocial
{
"mcpServers": {
"app-insightsocial-insightsocial": {
"command": "npx",
"args": [
"-y",
"insightsocial"
]
}
}
} 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 Oct 26 −31
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.3.0 → 0.3.1 functional
- 4 Oct 26 +25
- Known CVEs: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Provenance: fail → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- The attested source repository moved: insightsocial/cli security
- Schema quality: 156 → 192 ▼ functional
- Dependency health: 0.86 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.0 → 0.3.0 functional
- Package version: 0.1.0 → 0.2.2 functional
- Package version: 0.1.0 → 0.2.1 functional
- Package version: 0.1.0 → 0.2.0 functional
- 3 Oct 26 55
First indexed and scored.
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 8 Oct 2026 · Analysed npm/insightsocial@0.3.6
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | insightsocial/cli |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/insightsocial/cli/.github/workflows/publish.yml@refs/tags/v0.3.6 |
| Rekor log index | 3137745087 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f5706d3173c332524167671cfd0e4479d64a1ff172f2cf181f4b3bfb13a49edd7c37e9a40014e374463f583773fb9f30292b487fbda8a6a2592b50561 |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
call_endpoint Call an endpoint ~223
Fetch live data from one endpoint. Costs the credits listed in the catalogue (empty results and failures are free). The full response is saved and a result_id is returned with a trimmed view; use read_result to see more of it for free.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Keep only these keys on each item, e.g. ["username","followers","ext.public_email"]. Dotted paths descend. |
| fresh | boolean | – | Bypass caches and fetch fresh. Always charged. |
| idempotency_key | string | – | Send the same key to retry safely: a replay returns the original response and is charged 0. |
| jq | string | – | A jq expression over the saved response envelope, e.g. ".data.items[] | {id, text}". |
| max_items | integer | – | Items shown in the view (default 10). The saved result is always complete. |
| params | object | – | Query inputs, e.g. {"handle":"natgeo"} |
| path | string | yes | Endpoint path, e.g. /v1/instagram/profile |
No output schema declared.
No examples provided.
describe_endpoint Describe an endpoint ~53
The full contract of one endpoint: what it returns, every input with its type, allowed values and an example, and its price. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | e.g. /v1/instagram/profile |
No output schema declared.
No examples provided.
get_credits Credit balance ~25
Remaining credits, plan and this period’s usage for the configured key. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_result Read a saved result ~152
Re-slice a result saved by call_endpoint: jq, fields, max_items, or summary for an outline with byte sizes. Local and free. Never call the endpoint again just to see a different part.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Keep only these keys on each item, e.g. ["username","followers","ext.public_email"]. Dotted paths descend. |
| jq | string | – | A jq expression over the saved response envelope, e.g. ".data.items[] | {id, text}". |
| max_items | integer | – | – |
| result_id | string | yes | The result_id returned by call_endpoint. |
| summary | boolean | – | An outline of the structure with byte sizes, instead of values. |
No output schema declared.
No examples provided.
search_endpoints Search endpoints ~86
Find InsightSocial API endpoints by keywords and/or platform. Returns path, price in credits, required inputs and whether it paginates. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many results (default 10). |
| platform | string | – | Limit to one platform. |
| query | string | – | Words such as "instagram followers", "tiktok comments", "linkedin company jobs". |
No output schema declared.
No examples provided.
What is the InsightSocial MCP server?
InsightSocial is an MCP server listed in the public MCP registry as app.insightsocial/insightsocial. Live public data from Instagram, TikTok, LinkedIn, YouTube, X and 20 more networks, via one key. This page covers its npm package (insightsocial).
Is the InsightSocial MCP server safe to use?
InsightSocial scores 49 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 InsightSocial MCP server expose?
InsightSocial exposes 5 tools: search_endpoints, describe_endpoint, call_endpoint, read_result, get_credits. Their descriptions and schemas cost roughly 539 tokens of context every time the server is loaded.
Is the InsightSocial MCP server still maintained?
InsightSocial is still listed as active in the MCP registry. We last reached this channel on 5 October 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 InsightSocial MCP server under?
InsightSocial declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.