Remote MCP · Endpoint

Kourier MCP server

No. Kourier answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://kourier.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.kourier/info
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
149 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Discover flat-rate DeepSeek plans, model limits, API-key instructions, and coding-client setup.
Listing
From the official MCP registry (active).
Recent checks of Kourier
CheckedResultHandshake
1 hour agoHandshake completed149 ms
18 hours agoHandshake completed217 ms
2 days agoHandshake completed272 ms
3 days agoHandshake completed203 ms
4 days agoHandshake completed132 ms
5 days agoHandshake completed472 ms
6 days agoHandshake completed242 ms
7 days agoHandshake completed139 ms
10 days agoHandshake completed209 ms
13 days agoHandshake completed248 ms
15 days agoHandshake completed218 ms
17 days agoHandshake completed214 ms
19 days agoHandshake completed225 ms
21 days agoHandshake completed207 ms
23 days agoHandshake completed469 ms
25 days agoHandshake completed230 ms

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

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 Kourier and makes no claim about it beyond what these checks measured.