Remote MCP · Endpoint

Ordkort MCP server

No. Ordkort answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://ordkort.com/mcp

The last check completed an MCP handshake.

Registry name
com.ordkort/ordkort
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
309 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Flashcard decks with pictures and card designs for a free vocabulary site in 60 languages.
Listing
From the official MCP registry (active).
Recent checks of Ordkort
CheckedResultHandshake
13 minutes agoHandshake completed309 ms
10 days agoHandshake completed278 ms
10 days agoHandshake completed391 ms
11 days agoHandshake completed383 ms
13 days agoHandshake completed261 ms
14 days agoHandshake completed455 ms
14 days agoHandshake completed48 ms
15 days agoHandshake completed499 ms
17 days agoHandshake completed267 ms
19 days agoHandshake completed1.11 s
21 days agoHandshake completed256 ms
24 days agoHandshake completed319 ms
26 days agoHandshake completed326 ms
28 days agoHandshake completed358 ms

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