io.github.ravi-p-k-1/insightiq
NPM · INSIGHTIQ-MCP
Look up real FRED (Federal Reserve Economic Data) series and historical observations.
Available components
Last scanned (21 hours ago)
Scores higher than 51% of npm servers
Category Data and Analytics
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (CC0-1.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 64 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 819 tokens (~204/item across 4 items; 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 16 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 11 Nov 26 +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.
- 10 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 9 Nov 26 +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.
- 8 Nov 26 0
- Security disclosure: unverified → fail ▼ 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 21 Nov 2026 · Analysed npm/insightiq-mcp@1.0.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
get_economic_data Get economic data for a question ~283
Convenience tool that chains search_economic_series and get_series_observations in one call: searches FRED for series relevant to a question, then fetches their observations. Returns raw retrieved data only (series, units, observations) — you (the calling agent) should analyze this data yourself and write the explanation, this tool does not generate one. For better recall on vague questions, optionally pass searchQueries with 1-3 concise FRED-style keyword phrases; otherwise the question itself is used as the search text.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeTags | array | – | Optional FRED tag names that returned series must NOT have (e.g. ["nsa"] to exclude seasonally-unadjusted series). |
| limit | integer | – | Maximum number of series to search for and fetch data on. Defaults to 4. |
| question | string | yes | The natural-language economic question being asked. |
| searchQueries | array | – | Optional: 1-3 concise search phrases to use instead of the raw question, e.g. ["inflation", "consumer price index"]. |
| tags | array | – | Optional FRED tag names that returned series must ALL have (e.g. ["usa", "state"] to force state-level series). Use list_series_tags first to find valid tag names for your topic — an unrecognized tag… |
No output schema declared.
No examples provided.
get_series_observations Get series observations ~85
Fetch historical annual observations and units for specific real FRED series IDs. Returns raw retrieved data only — it does not generate any explanation or analysis. Use search_economic_series first to find real series IDs, then interpret the returned observations yourself to answer the user's question.
| Name | Type | Req | Description |
|---|---|---|---|
| series | array | yes | FRED series to fetch, typically the output of search_economic_series. |
No output schema declared.
No examples provided.
list_series_tags List series tags ~189
Discover the FRED tags that actually exist among series matching a topic, and how many series each tag covers. Use this before narrowing search_economic_series or get_economic_data with tags/excludeTags — FRED tag names are a controlled vocabulary (geography codes, "sa"/"nsa" for seasonal adjustment, frequency like "monthly") that usually cannot be guessed reliably, so guessing a wrong tag name silently returns zero results instead of erroring. Common tag groups include geography (e.g. "usa", "state", state postal codes like "tx"), seasonal adjustment ("sa", "nsa"), and frequency ("monthly", "quarterly", "annual").
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of tags to return, ordered by how many series they cover. Defaults to 20. |
| query | string | yes | A concise topic phrase, e.g. "unemployment rate". |
No output schema declared.
No examples provided.
search_economic_series Search economic series ~262
Search FRED (Federal Reserve Economic Data) for real economic data series matching a topic. Returns real FRED series IDs and titles only — never invents series IDs. Provide 1-3 concise, FRED-style keyword phrases (e.g. "consumer price index", "Texas unemployment rate"), not a full conversational question — FRED search matches every word in a phrase, so short, specific phrases work far better than full sentences. Include likely synonyms or named entities (a state, a specific indicator name) as separate phrases to improve recall.
| Name | Type | Req | Description |
|---|---|---|---|
| excludeTags | array | – | Optional FRED tag names that returned series must NOT have (e.g. ["nsa"] to exclude seasonally-unadjusted series). |
| limit | integer | – | Maximum number of series to return. Defaults to 4. |
| queries | array | yes | 1 to 3 concise economic search phrases, e.g. ["inflation", "consumer price index"]. |
| tags | array | – | Optional FRED tag names that returned series must ALL have (e.g. ["usa", "state"] to force state-level series). Use list_series_tags first to find valid tag names for your topic — an unrecognized tag… |
No output schema declared.
No examples provided.
How do I install the io.github.ravi-p-k-1/insightiq MCP server?
io.github.ravi-p-k-1/insightiq runs locally as an npm package, launched with npx -y insightiq-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 · insightiq-mcp
claude mcp add ravi-p-k-1-insightiq -- npx -y insightiq-mcp
What is the io.github.ravi-p-k-1/insightiq MCP server?
io.github.ravi-p-k-1/insightiq is an MCP server listed in the public MCP registry as io.github.ravi-p-k-1/insightiq. Look up real FRED (Federal Reserve Economic Data) series and historical observations. This page covers its npm package (insightiq-mcp).
Is the io.github.ravi-p-k-1/insightiq MCP server safe to use?
io.github.ravi-p-k-1/insightiq scores 75 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 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 io.github.ravi-p-k-1/insightiq MCP server expose?
io.github.ravi-p-k-1/insightiq exposes 4 tools: search_economic_series, get_series_observations, get_economic_data, list_series_tags. Their descriptions and schemas cost roughly 819 tokens of context every time the server is loaded.
Is the io.github.ravi-p-k-1/insightiq MCP server still maintained?
io.github.ravi-p-k-1/insightiq 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 licence is the io.github.ravi-p-k-1/insightiq MCP server under?
io.github.ravi-p-k-1/insightiq declares the CC0-1.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the io.github.ravi-p-k-1/insightiq MCP server?
VerifyMCP ran 16 checks on io.github.ravi-p-k-1/insightiq, 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.