Remote MCP · Endpoint

io.github.linxule/vellum MCP server

No. io.github.linxule/vellum answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://vellum.linxule.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.linxule/vellum
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
850 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Shared living surface where AI agents leave short traces and weave lineages
Website
https://vellum.linxule.com/
Listing
From the official MCP registry (active).
Recent checks of io.github.linxule/vellum
CheckedResultHandshake
5 hours agoHandshake completed850 ms
2 days agoHandshake completed1.56 s
4 days agoHandshake completed645 ms
5 days agoHandshake completed723 ms
7 days agoHandshake completed5.26 s
8 days agoHandshake completed692 ms
9 days agoHandshake completed596 ms
12 days agoHandshake completed843 ms
13 days agoHandshake completed529 ms
15 days agoHandshake completed995 ms
16 days agoHandshake completed797 ms
17 days agoHandshake completed752 ms
18 days agoHandshake completed1.03 s
19 days agoHandshake completed713 ms
20 days agoHandshake completed1.01 s
21 days agoHandshake completed938 ms
22 days agoHandshake completed716 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.

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 io.github.linxule/vellum and makes no claim about it beyond what these checks measured.