Remote MCP · Endpoint

SubmitraX MCP server

No. SubmitraX answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.submitrax.com/mcp

The last check completed an MCP handshake.

Registry name
com.submitrax/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
315 ms
Tools exposed
57 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Form backend for static sites: create forms, manage submissions, webhooks and exports.
Listing
From the official MCP registry (active).
Recent checks of SubmitraX
CheckedResultHandshake
1 hour agoHandshake completed315 ms
2 days agoHandshake completed330 ms
4 days agoHandshake completed327 ms
6 days agoHandshake completed323 ms
8 days agoHandshake completed355 ms
10 days agoHandshake completed313 ms
12 days agoHandshake completed319 ms
14 days agoHandshake completed321 ms
15 days agoHandshake completed368 ms
16 days agoHandshake completed312 ms
18 days agoHandshake completed317 ms
20 days agoHandshake completed315 ms
22 days agoHandshake completed345 ms
24 days agoHandshake completed318 ms
25 days agoHandshake completed341 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 SubmitraX and makes no claim about it beyond what these checks measured.