Remote MCP · Endpoint

Verateca MCP server

No. Verateca answered an MCP handshake 27 minutes ago.

UpLast checked 27 minutes ago

Server URL

https://verateca.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.a1476/verateca
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.31 s
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Dietary supplement register: compositions, country upper limits, US prices, stack check vs limits.
Listing
From the official MCP registry (active).
Recent checks of Verateca
CheckedResultHandshake
27 minutes agoHandshake completed1.31 s
10 days agoHandshake completed76 ms
11 days agoHandshake completed94 ms
12 days agoHandshake completed65 ms
13 days agoHandshake completed46 ms
14 days agoHandshake completed64 ms
15 days agoHandshake completed72 ms
16 days agoHandshake completed113 ms
17 days agoHandshake completed90 ms
19 days agoHandshake completed378 ms
22 days agoHandshake completed116 ms
24 days agoHandshake completed297 ms
26 days agoHandshake completed118 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 Verateca and makes no claim about it beyond what these checks measured.