Signalcrest
REMOTE · WWW.SIGNALCREST.APP · SCANNED SEP 27
Cross-source trend signals from 10 developer communities, scored every 30 minutes.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 544 tokens (~136/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Signalcrest MCP server?
Signalcrest is a hosted endpoint at https://www.signalcrest.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.signalcrest.app
claude mcp add --transport http apolloprojectsllc-svg-signalcrest 'https://www.signalcrest.app/api/mcp'
{
"mcpServers": {
"apolloprojectsllc-svg-signalcrest": {
"url": "https://www.signalcrest.app/api/mcp"
}
}
} {
"servers": {
"apolloprojectsllc-svg-signalcrest": {
"type": "http",
"url": "https://www.signalcrest.app/api/mcp"
}
}
} [mcp_servers.apolloprojectsllc-svg-signalcrest] url = "https://www.signalcrest.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"apolloprojectsllc-svg-signalcrest": {
"type": "remote",
"url": "https://www.signalcrest.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add apolloprojectsllc-svg-signalcrest --url 'https://www.signalcrest.app/api/mcp' --transport streamable-http
mcp_servers:
apolloprojectsllc-svg-signalcrest:
url: "https://www.signalcrest.app/api/mcp" {
"McpServers": {
"apolloprojectsllc-svg-signalcrest": {
"Transport": "http",
"Url": "https://www.signalcrest.app/api/mcp"
}
}
} assistant mcp add apolloprojectsllc-svg-signalcrest -t streamable-http -u 'https://www.signalcrest.app/api/mcp'
{
"mcpServers": {
"apolloprojectsllc-svg-signalcrest": {
"type": "http",
"url": "https://www.signalcrest.app/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
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 27 Sept 2026 · Probed https://www.signalcrest.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.signalcrest.app | CN=YR2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 53af5018d34483985a42f6851ee2e7b5f97 |
| SANs: www.signalcrest.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.signalcrest.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| signalcrest.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.signalcrest.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.signalcrest.app/api/mcp | HTTPS enforced | 308 | https://www.signalcrest.app/api/mcp |
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 →
get_entity Get entity detail ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Entity name as returned by list_entities, e.g. "kubernetes". |
No output schema declared.
No examples provided.
get_topic Get topic detail ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Topic id as returned by list_signals, e.g. "hn:48910545". |
No output schema declared.
No examples provided.
list_entities List trending entities ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to one category. Omit for all categories. |
| limit | integer | – | How many entities to return (default 50, max 200). |
No output schema declared.
No examples provided.
list_signals List live signals ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict to one category. Omit for all categories. |
| limit | integer | – | How many signals to return (default 50, max 200). |
No output schema declared.
No examples provided.
What is the Signalcrest MCP server?
Signalcrest is an MCP server listed in the public MCP registry as io.github.apolloprojectsllc-svg/signalcrest. Cross-source trend signals from 10 developer communities, scored every 30 minutes. This page covers its hosted endpoint (https://www.signalcrest.app/api/mcp).
Is the Signalcrest MCP server safe to use?
Signalcrest scores 73 out of 100 on VerifyMCP. 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 Signalcrest MCP server expose?
Signalcrest exposes 4 tools: list_signals, get_topic, list_entities, get_entity. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the Signalcrest MCP server require authentication?
No. We connected to Signalcrest without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Signalcrest MCP server still maintained?
Signalcrest is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.