# io.github.jshelley/briefings (remote · briefing-service.wholemind.workers.dev)

Hourly ranked news (AI, markets, sports, world): JSON, e-ink pages, Morning Paper PDF; 25 free/day

- Trust score: 59/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `briefing-service.wholemind.workers.dev`: 59/100 (this document), [markdown](https://verifymcp.io/servers/jshelley-briefings/briefing-service.md), [page](https://verifymcp.io/servers/jshelley-briefings/briefing-service)
- mcpb · `briefing-mcp-0.1.0.mcpb`: 50/100, [markdown](https://verifymcp.io/servers/jshelley-briefings/https-github-com-jshelley-briefing-mcp-releases-download-v0-1-0-briefing-mcp-0-1.md), [page](https://verifymcp.io/servers/jshelley-briefings/https-github-com-jshelley-briefing-mcp-releases-download-v0-1-0-briefing-mcp-0-1)

## Channel facts

- Endpoint: `https://briefing-service.wholemind.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 354 tokens (~118/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 18/100
  - Stability check failed: schema churn in the 13 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 33% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.jshelley/briefings MCP server?

io.github.jshelley/briefings is a hosted endpoint at https://briefing-service.wholemind.workers.dev/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.

### Claude

```bash
claude mcp add --transport http jshelley-briefings 'https://briefing-service.wholemind.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jshelley-briefings": {
      "url": "https://briefing-service.wholemind.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jshelley-briefings": {
      "type": "http",
      "url": "https://briefing-service.wholemind.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jshelley-briefings]
url = "https://briefing-service.wholemind.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jshelley-briefings": {
      "type": "remote",
      "url": "https://briefing-service.wholemind.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jshelley-briefings --url 'https://briefing-service.wholemind.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jshelley-briefings:
    url: "https://briefing-service.wholemind.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jshelley-briefings": {
      "Transport": "http",
      "Url": "https://briefing-service.wholemind.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jshelley-briefings -t streamable-http -u 'https://briefing-service.wholemind.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jshelley-briefings": {
      "type": "http",
      "url": "https://briefing-service.wholemind.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.

### 2026-09-18 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.

### 2026-09-17 (score 57, −3)

- [security regression] Stability: 0.27 → fail
- [security regression] A breaking change shipped without a version bump: still 0.2.0
- [security regression] Tool “render_briefing” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 445 → 354

### 2026-09-16 (score 60, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “list_briefings” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 99 → 111

### 2026-09-15 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 59, +1)

- [functional improvement] Tool coverage: 20% → 33%
- [cosmetic] “render_briefing” added an optional parameter “timezone”

### 2026-09-12 (score 58, +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.

### 2026-09-11 (score 57, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 53 → 92
- [functional] Server version: 0.1.0 → 0.2.0

## MCP tools (3)

### `list_briefings` (~57 tokens)

List the briefings available (AI, Frontier Labs, Markets, US Sports, European Football, US News, World News, Crypto & Onchain hourly; Grants & Funding and Noticias Lentas (simple Spanish, B1) daily).

### `get_briefing` (~62 tokens)

One briefing as structured JSON: lead story, ranked stories and research items with summaries, why-it-matters and key points, plus when it was ranked.

Input parameters:

- `key` (string, required): briefing key from list_briefings, e.g. 'ai'

### `get_page` (~60 tokens)

One rendered page of a briefing as a 480x800 1-bit PNG (page 0 is the front page; story pages follow). Made for e-ink and small displays.

Input parameters:

- `key` (string, required)
- `page` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jshelley-briefings/briefing-service#diagnostics

## Score history

- 2026-09-21: 59
- 2026-09-20: 59
- 2026-09-19: 58
- 2026-09-18: 58
- 2026-09-17: 57
- 2026-09-16: 60
- 2026-09-15: 60
- 2026-09-14: 59
- 2026-09-13: 59
- 2026-09-12: 58
- 2026-09-11: 57
- 2026-09-10: 57
- 2026-09-09: 56
- 2026-09-08: 56

## Common questions

### What is the io.github.jshelley/briefings MCP server?

io.github.jshelley/briefings is an MCP server listed in the public MCP registry as io.github.jshelley/briefings. Hourly ranked news (AI, markets, sports, world): JSON, e-ink pages, Morning Paper PDF; 25 free/day. This page covers its hosted endpoint (https://briefing-service.wholemind.workers.dev/mcp).

### Is the io.github.jshelley/briefings MCP server safe to use?

io.github.jshelley/briefings scores 59 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.jshelley/briefings MCP server expose?

io.github.jshelley/briefings exposes 3 tools: list_briefings, get_briefing, get_page. Their descriptions and schemas cost roughly 179 tokens of context every time the server is loaded.

### Does the io.github.jshelley/briefings MCP server require authentication?

No. We connected to io.github.jshelley/briefings without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.jshelley/briefings MCP server still maintained?

io.github.jshelley/briefings is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://briefing-service.wholemind.workers.dev/mcp
- Repository: https://github.com/jshelley/briefing-mcp
- Website: https://briefing-service.wholemind.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/jshelley-briefings/briefing-service.xml
- Changelog JSON feed: https://verifymcp.io/servers/jshelley-briefings/briefing-service.json
- HTML version of this page: https://verifymcp.io/servers/jshelley-briefings/briefing-service