Remote MCP · Endpoint

TOVREK Current-State Resolver MCP server

No. TOVREK Current-State Resolver answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://tovrek.com/mcp

The last check completed an MCP handshake.

Registry name
com.tovrek/current-state-resolver
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Verify DOI metadata before autonomous action; preserve conflicts, provenance, and UNKNOWN.
Listing
From the official MCP registry (active).
Recent checks of TOVREK Current-State Resolver
CheckedResultHandshake
38 minutes agoHandshake completed173 ms
3 days agoHandshake completed261 ms
13 days agoHandshake completed167 ms
13 days agoHandshake completed192 ms
15 days agoHandshake completed199 ms
16 days agoHandshake completed238 ms
17 days agoHandshake completed171 ms
18 days agoHandshake completed180 ms
18 days agoHandshake completed271 ms
20 days agoHandshake completed165 ms
22 days agoHandshake completed162 ms
25 days agoHandshake completed179 ms
27 days agoHandshake completed428 ms

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

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