Signalcrest
Cross-source trend signals from 10 developer communities, scored every 30 minutes.
사용해야 할까요
품질 및 안전성
발견 사항 (2)
- HIGHTool poisoning patterns detected
- INFOTool description contains placeholder or incomplete textlist_signals에서
도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.
컨텍스트 비용
이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.
설치
원클릭 설치
`claude_desktop_config.json` 파일에 다음을 추가하세요:
{
"mcpServers": {
"signalcrest": {
"url": "https://www.signalcrest.app/api/mcp"
}
}
}원격 엔드포인트
https://www.signalcrest.app/api/mcpstreamable-http할 수 있는 일
도구 목록
도구 (4)
🟢list_signals(category, limit)
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.
입력 스키마
{
"type": "object",
"properties": {
"category": {
"type": "string",
"enum": [
"ai",
"devtools",
"security",
"web",
"data",
"crypto",
"hardware",
"business",
"science",
"other"
],
"description": "Restrict to one category. Omit for all categories."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 200,
"description": "How many signals to return (default 50, max 200)."
}
},
"required": [],
"additionalProperties": false
}🟢get_topic(id)
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.
입력 스키마
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Topic id as returned by list_signals, e.g. \"hn:48910545\"."
}
},
"required": [
"id"
],
"additionalProperties": false
}🟢list_entities(category, limit)
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.
입력 스키마
{
"type": "object",
"properties": {
"category": {
"type": "string",
"enum": [
"ai",
"devtools",
"security",
"web",
"data",
"crypto",
"hardware",
"business",
"science",
"other"
],
"description": "Restrict to one category. Omit for all categories."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 200,
"description": "How many entities to return (default 50, max 200)."
}
},
"required": [],
"additionalProperties": false
}🟢get_entity(name)
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.
입력 스키마
{
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Entity name as returned by list_entities, e.g. \"kubernetes\"."
}
},
"required": [
"name"
],
"additionalProperties": false
}커뮤니티
증거