io.github.rezmeplxrf/insightsentry_mcp
NPM · @INSIGHTSENTRY/MCP · SCANNED SEP 25
MCP server for InsightSentry financial data API - market data, options, screeners, and more
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
- 50 of 135 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- 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 10 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 19882 tokens (~375/item across 53 items; 42 tools + 11 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 Management83
- Stability observed for 25 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
- Structured output schemas are declared (5% 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 42 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 44 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
How do I install the io.github.rezmeplxrf/insightsentry_mcp MCP server?
io.github.rezmeplxrf/insightsentry_mcp runs locally as an npm package, launched with npx -y @insightsentry/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 · @insightsentry/mcp
claude mcp add rezmeplxrf-insightsentry-mcp -- npx -y @insightsentry/mcp
{
"mcpServers": {
"rezmeplxrf-insightsentry-mcp": {
"command": "npx",
"args": [
"-y",
"@insightsentry/mcp"
]
}
}
} {
"servers": {
"rezmeplxrf-insightsentry-mcp": {
"command": "npx",
"args": [
"-y",
"@insightsentry/mcp"
]
}
}
} codex mcp add rezmeplxrf-insightsentry-mcp -- npx -y @insightsentry/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rezmeplxrf-insightsentry-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@insightsentry/mcp"
],
"enabled": true
}
}
} openclaw mcp add rezmeplxrf-insightsentry-mcp --command npx --arg -y --arg @insightsentry/mcp
mcp_servers:
rezmeplxrf-insightsentry-mcp:
command: "npx"
args: ["-y", "@insightsentry/mcp"] {
"McpServers": {
"rezmeplxrf-insightsentry-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@insightsentry/mcp"
]
}
}
} assistant mcp add rezmeplxrf-insightsentry-mcp -t stdio -c npx -a -y @insightsentry/mcp
{
"mcpServers": {
"rezmeplxrf-insightsentry-mcp": {
"command": "npx",
"args": [
"-y",
"@insightsentry/mcp"
]
}
}
} 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.
- 25 Sept 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Stability: fail → 0.77 functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 69 to 73.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 59 to 63.
- 17 Sept 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 73 to 56.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 69 to 73.
- 15 Sept 26 0
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 1.4.44 → 1.4.45 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 25 Sept 2026 · Analysed npm/@insightsentry/mcp@1.4.45
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 135 packages
| Packages resolved | 135 |
|---|---|
| Deprecated | 1 |
| Stale | 49 |
| 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 →
search_symbols ~325
Search for symbols. Search for symbols by text, type, country, or exchange. → Returns {current_page: number, has_more: boolean, symbols: [{name: string, code: string, type: string, exchange: string, currency_code: string, country: string, description: string}]}. ALWAYS start here to find the correct standard symbol code unless you already know it. InsightSentry uses EXCHANGE:SYMBOL format (e.g., NASDAQ:AAPL) which differs from other platforms. Do NOT guess codes — search first. Use exchange to limit results to one exchange; call list_exchanges to discover exchange prefixes. For SIP: codes, use list_sip_symbols. Use the returned code with get_quotes, get_symbol_series, get_symbol_info, or any other standard market-data tool.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Filter by country. 2-letter ISO code |
| exchange | string | – | Filter by exchange |
| filter | string | – | (Optional) JSONata expression to return only the fields or rows you need. See https://jsonata.org for syntax. |
| output_dir | string | – | Directory for stored response when output_file is not set. |
| output_file | string | – | File path for stored response. |
| page | integer | – | Each page returns up to 50 results. |
| query | string | – | Search query string |
| store | string | – | Store the response locally instead of returning it. Default is none. csv is only supported for get_symbol_series. |
| type | string | – | Filter by instrument type |
No output schema declared.
No examples provided.
version_status ~34
Check the installed InsightSentry CLI/MCP package version against the latest npm version and show the upgrade command when one is available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
whoami ~23
Print the logged-in InsightSentry user's email, falling back to uuid.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.rezmeplxrf/insightsentry_mcp MCP server?
io.github.rezmeplxrf/insightsentry_mcp is an MCP server listed in the public MCP registry as io.github.rezmeplxrf/insightsentry_mcp. MCP server for InsightSentry financial data API - market data, options, screeners, and more. This page covers its npm package (@insightsentry/mcp).
Is the io.github.rezmeplxrf/insightsentry_mcp MCP server safe to use?
io.github.rezmeplxrf/insightsentry_mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 io.github.rezmeplxrf/insightsentry_mcp MCP server expose?
io.github.rezmeplxrf/insightsentry_mcp exposes 42 tools: whoami, version_status, collect_live, collect_newsfeed, list_sip_symbols, and 37 more. Their descriptions and schemas cost roughly 15,277 tokens of context every time the server is loaded.
Is the io.github.rezmeplxrf/insightsentry_mcp MCP server still maintained?
io.github.rezmeplxrf/insightsentry_mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 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 io.github.rezmeplxrf/insightsentry_mcp MCP server under?
io.github.rezmeplxrf/insightsentry_mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.