Remote MCP · Endpoint

Velrim MCP server

No. Velrim answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.velrim.com/mcp

The last check completed an MCP handshake.

Registry name
com.velrim/extract
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.38 s
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Document extraction against a JSON Schema with a calibrated confidence per field; async job status.
Listing
From the official MCP registry (active).
Recent checks of Velrim
CheckedResultHandshake
1 hour agoHandshake completed1.38 s
2 days agoHandshake completed611 ms
4 days agoHandshake completed497 ms
5 days agoHandshake completed735 ms
7 days agoHandshake completed533 ms
8 days agoHandshake completed1.23 s
9 days agoHandshake completed875 ms
12 days agoHandshake completed677 ms
13 days agoHandshake completed611 ms
15 days agoHandshake completed570 ms
16 days agoHandshake completed648 ms
18 days agoHandshake completed632 ms
19 days agoHandshake completed638 ms
20 days agoHandshake completed493 ms
20 days agoHandshake completed474 ms
21 days agoHandshake completed424 ms
22 days agoHandshake completed736 ms

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

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