io.github.joepangallo/mcp-server-research-signals
NPM · MCP-SERVER-RESEARCH-SIGNALS · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 130 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 (excellent).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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · mcp-server-research-signals
claude mcp add joepangallo-mcp-server-research-signals -- npx -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": {
"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.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +29
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Schema quality: unverified → excellent ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: MIT functional
- 31 Jul 26 +9
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 40
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.