io.github.almaestilo/newswake
REMOTE · NEWSWAKE-AJQ8T.ONDIGITALOCEAN.APP · SCANNED SEP 24
News momentum + what-changed outcome tools for agents. Signals + links, ~296 sources.
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 Security57
- 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 2 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 262 tokens (~131/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.almaestilo/newswake MCP server?
io.github.almaestilo/newswake is a hosted endpoint at https://newswake-ajq8t.ondigitalocean.app/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 · newswake-ajq8t.ondigitalocean.app
claude mcp add --transport http almaestilo-newswake 'https://newswake-ajq8t.ondigitalocean.app/mcp'
{
"mcpServers": {
"almaestilo-newswake": {
"url": "https://newswake-ajq8t.ondigitalocean.app/mcp"
}
}
} {
"servers": {
"almaestilo-newswake": {
"type": "http",
"url": "https://newswake-ajq8t.ondigitalocean.app/mcp"
}
}
} [mcp_servers.almaestilo-newswake] url = "https://newswake-ajq8t.ondigitalocean.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"almaestilo-newswake": {
"type": "remote",
"url": "https://newswake-ajq8t.ondigitalocean.app/mcp",
"enabled": true
}
}
} openclaw mcp add almaestilo-newswake --url 'https://newswake-ajq8t.ondigitalocean.app/mcp' --transport streamable-http
mcp_servers:
almaestilo-newswake:
url: "https://newswake-ajq8t.ondigitalocean.app/mcp" {
"McpServers": {
"almaestilo-newswake": {
"Transport": "http",
"Url": "https://newswake-ajq8t.ondigitalocean.app/mcp"
}
}
} assistant mcp add almaestilo-newswake -t streamable-http -u 'https://newswake-ajq8t.ondigitalocean.app/mcp'
{
"mcpServers": {
"almaestilo-newswake": {
"type": "http",
"url": "https://newswake-ajq8t.ondigitalocean.app/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.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 24 Sept 2026 · Probed https://newswake-ajq8t.ondigitalocean.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ondigitalocean.app | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 91fc2e6624162c2f0ea28c20d707275b |
| SANs: ondigitalocean.app, *.ondigitalocean.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of newswake-ajq8t.ondigitalocean.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ondigitalocean.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://newswake-ajq8t.ondigitalocean.app/mcp | Verified | 200 | |
| http (plaintext) | http://newswake-ajq8t.ondigitalocean.app/mcp | HTTPS enforced | 301 | https://newswake-ajq8t.ondigitalocean.app/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 →
find_trending ~135
What news is ACCELERATING right now — a ranked list of story-events climbing in attention, optionally scoped to a beat/topic. Each returns trend, momentum, acceleration, outlet count, a runway hint (act now vs window closing), why-now, and a link. Use to decide what to ride/publish/watch. ~2h behind live, ~296 mainstream sources, signals + links only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 8). |
| topic | string | – | Beat or keyword to scope to, e.g. "technology", "crypto", "nvidia". Omit for all beats. |
No output schema declared.
No examples provided.
whats_changed ~127
The DELTA on an entity — what is new or has shifted in news coverage of a company/person/topic since a given time. Returns new vs updated story-events, trend, importance, and links. This is the stateful "what changed since my last check" that stateless search tools cannot answer. ~296 mainstream sources, signals + links only.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Company, person, or topic, e.g. "Nvidia", "OpenAI", "Donald Trump". |
| since | string | – | ISO timestamp of your last check. Default: 7 days ago. |
No output schema declared.
No examples provided.
What is the io.github.almaestilo/newswake MCP server?
io.github.almaestilo/newswake is an MCP server listed in the public MCP registry as io.github.almaestilo/newswake. News momentum + what-changed outcome tools for agents. Signals + links, ~296 sources. This page covers its hosted endpoint (https://newswake-ajq8t.ondigitalocean.app/mcp).
Is the io.github.almaestilo/newswake MCP server safe to use?
io.github.almaestilo/newswake scores 78 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 io.github.almaestilo/newswake MCP server expose?
io.github.almaestilo/newswake exposes 2 tools: find_trending, whats_changed. Their descriptions and schemas cost roughly 262 tokens of context every time the server is loaded.
Does the io.github.almaestilo/newswake MCP server require authentication?
No. We connected to io.github.almaestilo/newswake without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.almaestilo/newswake MCP server still maintained?
io.github.almaestilo/newswake is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.