Is the Jshelley Briefings MCP server down?

mcp-registry/io.github.jshelley/briefings · v0.2.0

Also listed as github/jshelley/briefing-mcp

As of 2026-10-22 18:03 UTC, the Jshelley Briefings MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

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

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

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

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (78/100)

What to fix (3)

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jshelley%2Fbriefings/fixes

{
  "name": "get_briefing",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "key"
    ],
    "properties": {
      "key": {
        "type": "string",
        "description": "briefing key from list_briefings, e.g. 'ai'"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_page",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "key"
    ],
    "properties": {
      "key": {
        "type": "string"
      },
      "page": {
        "type": "integer",
        "default": 0,
        "maximum": 32,
        "minimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "list_briefings",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.jshelley/briefings"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jshelley/briefings"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~315 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• get_briefing ~111 tokens
• get_page ~107 tokens
• list_briefings ~97 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jshelley%2Fbriefings.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jshelley%2Fbriefings?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.jshelley%2Fbriefings?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jshelley%2Fbriefings.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jshelley%2Fbriefings.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jshelley%2Fbriefings?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:694708767e087683…, first seen 2026-10-17, included at leaf 7270 of 47,366. Version history · verify what your client received.

Tools (3)

• get_briefing
• get_page
• list_briefings

Compare: most reliable knowledge servers · most reliable media servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Jshelley Briefings MCP server down right now?

As of 2026-10-22 18:03 UTC, the Jshelley Briefings MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Jshelley Briefings MCP server provide?

Jshelley Briefings MCP server advertises 3 tools, including get_briefing, get_page, list_briefings.

How do I install Jshelley Briefings MCP server?

Point your MCP client at this streamable-http endpoint: https://briefing-service.wholemind.workers.dev/mcp

Is the Jshelley Briefings MCP server safe to connect to an AI agent?

Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Jshelley Briefings MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.