Remote MCP · Endpoint

Substack MCP Server and API by Cotlet MCP server

No. Substack MCP Server and API by Cotlet answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://cotlet.dev/mcp/v1/substack

The last check completed an MCP handshake.

Registry name
dev.cotlet/substack
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
153 ms
Tools exposed
83 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Substack writer newsletter publishing MCP server: create post, schedule post, publish Note.
Listing
From the official MCP registry (active).
Recent checks of Substack MCP Server and API by Cotlet
CheckedResultHandshake
42 minutes agoHandshake completed153 ms
3 days agoHandshake completed159 ms
12 days agoHandshake completed168 ms
12 days agoHandshake completed164 ms
14 days agoHandshake completed182 ms
15 days agoHandshake completed549 ms
16 days agoHandshake completed193 ms
17 days agoHandshake completed600 ms
18 days agoHandshake completed167 ms
20 days agoHandshake completed181 ms
22 days agoHandshake completed162 ms
25 days agoHandshake completed149 ms

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

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 Substack MCP Server and API by Cotlet and makes no claim about it beyond what these checks measured.