Remote MCP · Endpoint

study.vela/corpus MCP server

No. study.vela/corpus answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vela.study/mcp

The last check completed an MCP handshake.

Registry name
study.vela/corpus
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Read-only MCP access to Vela's corpus of human experience: cited passages, coordinates, reading path
Website
https://vela.study/
Repository
https://github.com/people-analyst/vela
Listing
From the official MCP registry (active).
Recent checks of study.vela/corpus
CheckedResultHandshake
1 hour agoHandshake completed119 ms
1 day agoHandshake completed168 ms
2 days agoHandshake completed114 ms
3 days agoHandshake completed116 ms
4 days agoHandshake completed110 ms
5 days agoHandshake completed172 ms
6 days agoHandshake completed213 ms
8 days agoHandshake completed191 ms
11 days agoHandshake completed154 ms
13 days agoHandshake completed198 ms
15 days agoHandshake completed110 ms
18 days agoHandshake completed140 ms
20 days agoHandshake completed164 ms
22 days agoHandshake completed102 ms
24 days agoHandshake completed74 ms
26 days agoHandshake completed186 ms
27 days agoHandshake completed76 ms
29 days agoHandshake completed68 ms
29 days agoHandshake completed82 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 study.vela/corpus and makes no claim about it beyond what these checks measured.