# Signalcrest

> Cross-source trend signals from 10 developer communities, scored every 30 minutes.

- name: io.github.apolloprojectsllc-svg/signalcrest
- version: 1.0.0
- connection class: R1 (autonomous)
- trust: 74/100 flags: no-repository
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.apolloprojectsllc-svg%2Fsignalcrest
- tools: https://api.protogrid.dev/v1/servers/io.github.apolloprojectsllc-svg%2Fsignalcrest/tools

**An agent can connect on its own if it already holds `SIGNALCREST_TOKEN`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "signalcrest": {
      "type": "http",
      "url": "https://www.signalcrest.app/api/mcp",
      "headers": {
        "Authorization": "Bearer ${SIGNALCREST_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${SIGNALCREST_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 35
- drivers: +reachable +uptime-100% ~updated-40d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: list_entities (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_signals (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_topic (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 633 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 633 tokens to load them all
- tool set hash: b90719f1ffce11f396f0e0e0fd31829c
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.apolloprojectsllc-svg/signalcrest.svg)](https://protogrid.dev/servers/io.github.apolloprojectsllc-svg/signalcrest)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://www.signalcrest.app/api/mcp (streamable-http, auth api_key ${SIGNALCREST_TOKEN}, reachable true, uptime30d 1)

## Packages

_none_

## Tools (4)

- `get_entity`: 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_topic`: 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_entities`: 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_signals`: 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.