Remote MCP · Endpoint

Kódvéna MCP server

No. Kódvéna answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://kodvena.hu/mcp

The last check completed an MCP handshake.

Registry name
hu.kodvena/kodvena
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.00 s
Tools exposed
42 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Kódvéna (kodvena.hu) magyar webfejlesztő: szolgáltatások, szakmai oldalak, GYIK, igényleadás.
Website
https://kodvena.hu/
Listing
From the official MCP registry (active).
Recent checks of Kódvéna
CheckedResultHandshake
18 minutes agoHandshake completed1.00 s
9 days agoHandshake completed430 ms
9 days agoHandshake completed226 ms
11 days agoHandshake completed206 ms
12 days agoHandshake completed380 ms
13 days agoHandshake completed268 ms
14 days agoHandshake completed254 ms
14 days agoHandshake completed189 ms
16 days agoHandshake completed431 ms
19 days agoHandshake completed199 ms
21 days agoHandshake completed528 ms
24 days agoHandshake completed259 ms
26 days agoHandshake completed558 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Kódvéna and makes no claim about it beyond what these checks measured.