Remote MCP · Endpoint

Ärikratt MCP server

No. Ärikratt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://arikratt.ee/mcp

The last check completed an MCP handshake.

Registry name
ee.arikratt/arikratt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
221 ms
Tools exposed
19 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Estonian companies, EMTAK, grants and tenders from public registers.
Listing
From the official MCP registry (active).
Recent checks of Ärikratt
CheckedResultHandshake
1 hour agoHandshake completed221 ms
2 days agoHandshake completed150 ms
4 days agoHandshake completed321 ms
6 days agoHandshake completed181 ms
8 days agoHandshake completed208 ms
9 days agoHandshake completed144 ms
11 days agoHandshake completed176 ms
12 days agoHandshake completed303 ms
13 days agoHandshake completed207 ms
16 days agoHandshake completed150 ms
17 days agoHandshake completed554 ms
19 days agoHandshake completed497 ms
21 days agoHandshake completed495 ms
22 days agoHandshake completed479 ms
23 days agoHandshake completed502 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 Ärikratt and makes no claim about it beyond what these checks measured.