Remote MCP · Endpoint

Laravilt MCP server

No. Laravilt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.laravilt.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.laravilt/laravilt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
500 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Laravilt docs, packages and plugins for agents: a Laravel admin panel on Inertia with Vue or React.
Listing
From the official MCP registry (active).
Recent checks of Laravilt
CheckedResultHandshake
1 hour agoHandshake completed500 ms
1 day agoHandshake completed516 ms
2 days agoHandshake completed675 ms
3 days agoHandshake completed507 ms
4 days agoHandshake completed522 ms
5 days agoHandshake completed500 ms
6 days agoHandshake completed514 ms
9 days agoHandshake completed545 ms
12 days agoHandshake completed490 ms
14 days agoHandshake completed1.58 s
16 days agoHandshake completed697 ms
18 days agoHandshake completed513 ms
20 days agoHandshake completed538 ms
22 days agoHandshake completed539 ms
24 days agoHandshake completed506 ms

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

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