Clarity Today
REMOTE · THECLARITY.TODAY
Clarity Today's briefing, latest stories by desk, search and full source-linked stories.
Available components
Last scanned (22 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 4 Nov 2026.
Category News and Social
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 yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 405. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 17 Oct 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Oct 26 0
- Tool “get_todays_briefing” rewrote its description, which is the text the model reads security
- 15 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 13 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 534 → 688 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- New resource “Clarity Today evidence card” functional
- New tool “get_story” functional
- 12 Oct 26 75
First indexed and scored.
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 4 Nov 2026 · Probed https://theclarity.today/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=theclarity.today | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b96ebbe2105d2acb0ed7281dc9a7f5d9 |
| SANs: theclarity.today | ||||||
| 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 theclarity.today. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| today. | present | 8164 | 8 | Verified |
| theclarity.today. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 405 |
| Header | Value |
|---|---|
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://theclarity.today/mcp | HTTP error | 405 | |
| http (plaintext) | http://theclarity.today/mcp | HTTPS enforced | 301 | https://theclarity.today/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 →
fetch Read a Clarity Today story ~81
Read one Clarity Today story in full, as Markdown: what happened, why it matters, what to watch, the claim ledger tying each claim to its source, and every publisher the story draws on.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A story id from search, the briefing or the latest stories, or a https://theclarity.today/story/<slug> URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | The story as Markdown, ending with the URL to cite. |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_story Show a Clarity Today story’s evidence ~108
Show one Clarity Today story as its evidence card: what changed and why it matters, the story’s own figure, each claim with the verifier’s verdict and its source, and the publishers behind it. Use it when the reader wants to see a story or check it; use fetch to read a story’s text for an answer.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A story id from search, the briefing or the latest stories, or a https://theclarity.today/story/<slug> URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| claim_count | integer | yes | Claims in the story’s full ledger. |
| claims | array | yes | The ledger in the story page’s order, up to 60 claims. |
| confirmation | string | yes | What the story’s record is worth, in the story page’s own words (“Widely confirmed”, “Not yet confirmed elsewhere”). Lead with it; publishers is the proof. |
| confirmation_kind | string | yes | – |
| correction | – | yes | – |
| corroboration | string | yes | single-source below two independent publishers: present it as a report, not a confirmed fact. |
| desk | string | yes | – |
| desk_name | string | yes | – |
| id | string | yes | The story id (its slug). Pass it to fetch for the full story. |
| published_at | string | yes | ISO 8601. |
| publishers | integer | yes | Independent publishers whose reporting the story is built from. |
| source_count | integer | yes | – |
| sources | array | yes | Up to 30 of the publishers the story draws on. |
| summary | string | yes | – |
| title | string | yes | – |
| updated_at | string | yes | ISO 8601. |
| url | string | yes | The story page. Link it whenever you use the story. |
| visual | – | yes | The story’s stored evidence visual (the publication’s story-visual catalog), exactly as published; null when it has none. |
| watch_next | array | yes | Open questions the story says to watch. |
| what_happened | array | yes | – |
| why_it_matters | array | yes | – |
No examples provided.
get_todays_briefing Today’s Briefing ~39
Today’s Briefing: the handful of stories Clarity’s desks ranked most important right now, each with its key sourced points.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| built_at | string | yes | When the briefing was assembled, ISO 8601. |
| stories | array | yes | – |
| url | string | yes | – |
No examples provided.
list_latest_stories Latest Clarity Today stories ~166
The newest Clarity Today stories, newest first: across every desk, or from one desk.
| Name | Type | Req | Description |
|---|---|---|---|
| desk | string | – | One desk; omit for every desk. security — Security desk (security): Reads the advisories so you don't have to. build — Build desk (engineering): What changed in the platforms and tools you ship on. i… |
| limit | integer | – | How many stories, 1–25. Default 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| desk | – | yes | – |
| stories | array | yes | – |
| url | string | yes | The page listing these stories. |
No examples provided.
search Search Clarity Today ~82
Find Clarity Today stories about a subject. Returns up to 12 matching stories, newest first, each with its URL and how many independent publishers back it. Pass a result’s id to fetch to read the whole story.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 1–4 distinctive keywords: a company, product, person, vulnerability or technology. Matches story headlines and summaries. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
How do I install the Clarity Today MCP server?
Clarity Today is a hosted endpoint at https://theclarity.today/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 · theclarity.today
claude mcp add --transport http today-theclarity-clarity-today 'https://theclarity.today/mcp'
What is the Clarity Today MCP server?
Clarity Today is an MCP server listed in the public MCP registry as today.theclarity/clarity-today. Clarity Today's briefing, latest stories by desk, search and full source-linked stories. This page covers its hosted endpoint (https://theclarity.today/mcp).
Is the Clarity Today MCP server safe to use?
Clarity Today scores 23 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 Clarity Today MCP server expose?
Clarity Today exposes 5 tools: search, fetch, get_story, get_todays_briefing, list_latest_stories. Their descriptions and schemas cost roughly 476 tokens of context every time the server is loaded.
Does the Clarity Today MCP server require authentication?
Its publisher declares no required credentials for Clarity Today. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Clarity Today MCP server still maintained?
Clarity Today is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.