Remote MCP · Endpoint

FiveM Docs MCP server

No. FiveM Docs answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://fivemdocs.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Livvux/fivemdocs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
216 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Search and read independent FiveM development guides with citations. Free, read-only, no API key.
Listing
From the official MCP registry (active).
Recent checks of FiveM Docs
CheckedResultHandshake
7 hours agoHandshake completed216 ms
4 days agoHandshake completed474 ms
14 days agoHandshake completed412 ms
15 days agoHandshake completed435 ms
15 days agoHandshake completed437 ms
17 days agoHandshake completed422 ms
18 days agoHandshake completed441 ms
19 days agoHandshake completed419 ms
20 days agoHandshake completed433 ms
21 days agoHandshake completed494 ms
23 days agoHandshake completed417 ms
26 days agoHandshake completed192 ms
28 days agoHandshake completed421 ms

The last 13 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 FiveM Docs and makes no claim about it beyond what these checks measured.