Remote MCP · Endpoint

RPScripts FiveM Developer MCP server

No. RPScripts FiveM Developer answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://rpscripts.net/mcp

The last check completed an MCP handshake.

Registry name
net.rpscripts/fivem
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
331 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
FiveM dev tools: find resources, check compatibility, validate Lua and server.cfg, generate jobs
Listing
From the official MCP registry (active).
Recent checks of RPScripts FiveM Developer
CheckedResultHandshake
18 minutes agoHandshake completed331 ms
10 days agoHandshake completed367 ms
10 days agoHandshake completed356 ms
11 days agoHandshake completed420 ms
13 days agoHandshake completed326 ms
14 days agoHandshake completed360 ms
14 days agoHandshake completed155 ms
15 days agoHandshake completed321 ms
17 days agoHandshake completed344 ms
19 days agoHandshake completed232 ms
21 days agoHandshake completed246 ms
24 days agoHandshake completed140 ms
26 days agoHandshake completed173 ms
28 days agoHandshake completed464 ms

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