Remote MCP · Endpoint

Marziale Technologies MCP server

No. Marziale Technologies answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://mcp.marziale.tech/mcp

The last check completed an MCP handshake.

Registry name
tech.marziale.mcp/marziale
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
737 ms
Tools exposed
5 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Send a request to Marziale Technologies, a New York FDSE firm. For business operators and talent.
Listing
From the official MCP registry (active).
Recent checks of Marziale Technologies
CheckedResultHandshake
19 minutes agoHandshake completed737 ms
10 days agoHandshake completed997 ms
10 days agoHandshake completed1.09 s
11 days agoHandshake completed1.07 s
13 days agoHandshake completed677 ms
14 days agoHandshake completed689 ms
14 days agoHandshake completed1.15 s
15 days agoHandshake completed891 ms
17 days agoHandshake completed1.39 s
19 days agoHandshake completed1.74 s
21 days agoHandshake completed805 ms
24 days agoHandshake completed779 ms
26 days agoFailed - the server returned an HTTP error—
28 days agoHandshake completed771 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Marziale Technologies and makes no claim about it beyond what these checks measured.