Signalcrest
by apolloprojectsllc-svg · remote · no sign-in to list tools · v1.0.0 · published by GitHub user apolloprojectsllc-svg
Cross-source trend signals from 10 developer communities, scored every 30 minutes.
4 tools: 4 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things0Claude Code: ask
- Only reads4Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http signalcrest https://www.signalcrest.app/api/mcp --header 'Authorization: <your-authorization>'Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
4 tools
Only reads 4Claude Code: allow
get_entityFull detail for one entity by name (e.g.No findings
Why it is in this group
- The name "get_entity" says "get": a word for reading.
Description, as the server wrote it Full detail for one entity by name (e.g. "kubernetes"): current composite score, complete score history, which communities are talking about it, and the live member items (evidence) behind the score. Names come from list_entities.
get_topicFull detail and complete score history for one topic, by id (e.g.No findings
Why it is in this group
- The name "get_topic" says "get": a word for reading.
Description, as the server wrote it Full detail and complete score history for one topic, by id (e.g. "hn:48910545", "gh:1287845516"). Call this after list_signals to see how a specific signal has moved over time, its cross-source corroboration, and its lifecycle stage. Ids come from list_signals.
list_entitiesTrending entities (products, companies, libraries, technologies) ranked by cross-source momentum.No findings
Why it is in this group
- The name "list_entities" says "list": a word for reading.
Description, as the server wrote it Trending entities (products, companies, libraries, technologies) ranked by cross-source momentum. An entity aggregates every post, repo and release mentioning it across ten developer and builder communities — one row per trend rather than per post. Prefer this over list_signals when the user asks about trends or technologies; use list_signals for individual posts.
list_signalsTop technology signals ranked by momentum right now, scored every 30 minutes across ten developer and builder communities (Hacker News, GitHub, Stack Overflow, npm, Hugging Face, D…No findings
Why it is in this group
- The name "list_signals" says "list": a word for reading.
Description, as the server wrote it Top technology signals ranked by momentum right now, scored every 30 minutes across ten developer and builder communities (Hacker News, GitHub, Stack Overflow, npm, Hugging Face, Dev.to, Lobsters, Product Hunt, arXiv, crypto governance forums). Call this to find what is gaining traction before it reaches search-trend tools — e.g. when the user asks what is emerging, trending, or worth paying attention to in a technology area. Returns live unredacted data with no delay.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http signalcrest https://www.signalcrest.app/api/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__signalcrest__list_signals",
"mcp__signalcrest__get_topic",
"mcp__signalcrest__list_entities",
"mcp__signalcrest__get_entity"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as signalcrest. Review it before you use it.
