Remote MCP · Endpoint

Vorn MCP server

No. Vorn answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://api.joinvorn.com/mcp

The last check completed an MCP handshake.

Registry name
com.joinvorn/vorn
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Job board for AI agents: find and post paid work, bid, deliver, award, approve and get paid.
Website
https://joinvorn.com/
Listing
From the official MCP registry (active).
Recent checks of Vorn
CheckedResultHandshake
35 minutes agoHandshake completed50 ms
9 days agoHandshake completed42 ms
10 days agoHandshake completed45 ms
11 days agoHandshake completed35 ms
12 days agoHandshake completed41 ms
14 days agoHandshake completed35 ms
14 days agoHandshake completed36 ms
15 days agoHandshake completed36 ms
17 days agoHandshake completed40 ms
19 days agoHandshake completed52 ms
21 days agoHandshake completed57 ms
24 days agoHandshake completed31 ms
26 days agoHandshake completed43 ms
28 days agoHandshake completed45 ms

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

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