Remote MCP · Endpoint

The Daily Markdown MCP server

No. The Daily Markdown answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://dailymd.cowerx.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.cowerx/dailymd
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
96 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Free AI news, ranked stories by section, and trending topics. No authentication required.
Listing
From the official MCP registry (active).
Recent checks of The Daily Markdown
CheckedResultHandshake
1 hour agoHandshake completed96 ms
1 day agoHandshake completed44 ms
3 days agoHandshake completed42 ms
3 days agoHandshake completed48 ms
4 days agoHandshake completed173 ms
5 days agoHandshake completed52 ms
7 days agoHandshake completed126 ms
10 days agoHandshake completed93 ms
12 days agoHandshake completed52 ms
15 days agoHandshake completed70 ms
17 days agoHandshake completed59 ms
19 days agoHandshake completed115 ms
21 days agoHandshake completed66 ms
23 days agoHandshake completed91 ms
25 days agoHandshake completed72 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with The Daily Markdown and makes no claim about it beyond what these checks measured.