Remote MCP · Endpoint

Ozerki via AgentPay MCP server

Yes, as of 1 hour ago: the TLS certificate could not be verified.

DownLast checked 1 hour ago

Server URL

https://agentpay.shop/ap/mcp/ozerki

The last check failed: the TLS certificate could not be verified.

Registry name
io.github.zapnikita95/ozerki
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
38.9% from 18 checks
Described by its publisher as
Ozerki pharmacy catalog, local pickup availability and tracked basket handoff for AI agents.
Website
https://agentpay.shop/mcp
Repository
https://github.com/zapnikita95/agentpay-mcp
Listing
From the official MCP registry (active).
Recent checks of Ozerki via AgentPay
CheckedResultHandshake
1 hour agoFailed - the TLS certificate could not be verified—
1 day agoFailed - the TLS certificate could not be verified—
2 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
18 days agoHandshake completed160 ms
20 days agoHandshake completed120 ms
22 days agoHandshake completed118 ms
24 days agoHandshake completed141 ms
26 days agoHandshake completed140 ms
27 days agoHandshake completed180 ms
29 days agoHandshake completed109 ms
30 days agoHandshake completed105 ms

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

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 Ozerki via AgentPay and makes no claim about it beyond what these checks measured.