Remote MCP · Endpoint

TOVREK Current-State Resolver MCP server

No. TOVREK Current-State Resolver answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
165 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
1 hour agoHandshake completed165 ms
2 days agoHandshake completed162 ms
4 days agoHandshake completed179 ms
7 days agoHandshake completed428 ms
9 days agoHandshake completed179 ms
11 days agoHandshake completed159 ms
13 days agoHandshake completed152 ms
15 days agoHandshake completed157 ms
17 days agoHandshake completed159 ms
19 days agoHandshake completed170 ms
20 days agoHandshake completed154 ms
22 days agoHandshake completed171 ms
23 days agoHandshake completed148 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.

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.