Remote MCP · Endpoint

dev.podaci/tvrtke MCP server

No. dev.podaci/tvrtke answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://tvrtke.podaci.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.podaci/tvrtke
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
443 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
An MCP server that provides Croatian corporate, financial, and beneficial ownership intelligence.
Listing
From the official MCP registry (active).
Recent checks of dev.podaci/tvrtke
CheckedResultHandshake
19 minutes agoHandshake completed443 ms
9 days agoHandshake completed327 ms
9 days agoHandshake completed315 ms
11 days agoHandshake completed372 ms
12 days agoHandshake completed1.19 s
13 days agoHandshake completed325 ms
14 days agoHandshake completed299 ms
15 days agoHandshake completed314 ms
16 days agoHandshake completed300 ms
19 days agoHandshake completed302 ms
21 days agoHandshake completed306 ms
24 days agoHandshake completed1.47 s

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.

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