io.github.joepangallo/mcp-server-research-signals
NPM · MCP-SERVER-RESEARCH-SIGNALS · SCANNED SEP 20
Scored trend intelligence from HN, Reddit, ArXiv, and GitHub.
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 96 dependencies flagged as unhealthy. 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 178 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 425 tokens (~60/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.joepangallo/mcp-server-research-signals server?
io.github.joepangallo/mcp-server-research-signals runs locally as an npm package, launched with npx -y mcp-server-research-signals. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-server-research-signals
claude mcp add joepangallo-mcp-server-research-signals -- npx -y mcp-server-research-signals
{
"mcpServers": {
"joepangallo-mcp-server-research-signals": {
"command": "npx",
"args": [
"-y",
"mcp-server-research-signals"
]
}
}
} {
"servers": {
"joepangallo-mcp-server-research-signals": {
"command": "npx",
"args": [
"-y",
"mcp-server-research-signals"
]
}
}
} codex mcp add joepangallo-mcp-server-research-signals -- npx -y mcp-server-research-signals
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joepangallo-mcp-server-research-signals": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-server-research-signals"
],
"enabled": true
}
}
} openclaw mcp add joepangallo-mcp-server-research-signals --command npx --arg -y --arg mcp-server-research-signals
mcp_servers:
joepangallo-mcp-server-research-signals:
command: "npx"
args: ["-y", "mcp-server-research-signals"] {
"McpServers": {
"joepangallo-mcp-server-research-signals": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-server-research-signals"
]
}
}
} assistant mcp add joepangallo-mcp-server-research-signals -t stdio -c npx -a -y mcp-server-research-signals
{
"mcpServers": {
"joepangallo-mcp-server-research-signals": {
"command": "npx",
"args": [
"-y",
"mcp-server-research-signals"
]
}
}
} 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.
- 20 Sept 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.
- 18 Sept 26 +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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 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.
- 13 Sept 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.
- 11 Sept 26 +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.
- 10 Sept 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 20 Sept 2026 · Analysed npm/mcp-server-research-signals@1.2.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 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
list_signals ~130
List scored research signals from swarm intelligence. Each signal has a composite score based on urgency, buyer intent, durability, and source count. Signals come from HN, Reddit, ArXiv, GitHub, and other sources.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category: ai, infrastructure, security, devtools, data, business, career, market |
| limit | number | – | Max signals to return (default: 25) |
| min_score | number | – | Minimum score filter |
| sort | string | – | Sort by: score (default), urgency, buyer_intent, durability |
No output schema declared.
No examples provided.
recalculate_scores ~36
Force a recalculation of all signal scores. Applies time decay to urgency and detects new breakout trends. Use after ingesting new data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
signal_detail ~63
Get deep detail on a specific research signal including full evidence, score breakdown (urgency, buyer intent, durability), actionable-for audience, and trend history.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | The signal topic to look up (partial match supported, use hyphens for spaces) |
No output schema declared.
No examples provided.
signal_stats ~36
Get aggregate statistics: total signals, category breakdown (count + avg score + top topic per category), and the top 10 signals overall.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
signals_by_category ~45
Get all signals in a specific category. Categories: ai, infrastructure, security, devtools, data, business, career, market.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category name |
No output schema declared.
No examples provided.
trending_signals ~45
Get breakout signals (trending at 1.8x+ their rolling average) and hot signals (score 6+). Use this to find what's surging right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
triage_signals ~70
Group research signals into build_now, monitor, and ignore buckets with product mapping for cloud-agent, mcp-audit, web-recon, and lead-gen plus a one-sentence recommended action.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max signals to include in the triage summary (default: 25) |
No output schema declared.
No examples provided.
What is the io.github.joepangallo/mcp-server-research-signals server?
io.github.joepangallo/mcp-server-research-signals is listed in the public MCP registry as io.github.joepangallo/mcp-server-research-signals. Scored trend intelligence from HN, Reddit, ArXiv, and GitHub. This page covers its npm package (mcp-server-research-signals).
Is the io.github.joepangallo/mcp-server-research-signals server safe to use?
io.github.joepangallo/mcp-server-research-signals scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.joepangallo/mcp-server-research-signals server expose?
io.github.joepangallo/mcp-server-research-signals exposes 7 tools: list_signals, trending_signals, triage_signals, signal_detail, signals_by_category, and 2 more. Their descriptions and schemas cost roughly 425 tokens of context every time the server is loaded.
Is the io.github.joepangallo/mcp-server-research-signals server still maintained?
io.github.joepangallo/mcp-server-research-signals is still listed as active in the MCP registry. We last reached this channel on 20 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.joepangallo/mcp-server-research-signals server under?
io.github.joepangallo/mcp-server-research-signals declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.