Remote MCP · Endpoint

Pyxmark MCP server

No. Pyxmark answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.pyxmark.com/mcp

The last check completed an MCP handshake.

Registry name
com.pyxmark/pyxmark
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
746 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Vendor checks: sanctions lists, SEC filings, domain age and a due-diligence report with sources.
Listing
From the official MCP registry (active).
Recent checks of Pyxmark
CheckedResultHandshake
34 minutes agoHandshake completed746 ms
9 days agoHandshake completed1.02 s
10 days agoHandshake completed840 ms
11 days agoHandshake completed790 ms
12 days agoHandshake completed758 ms
14 days agoHandshake completed773 ms
14 days agoHandshake completed782 ms
15 days agoHandshake completed737 ms
17 days agoHandshake completed1.84 s
19 days agoHandshake completed794 ms
21 days agoHandshake completed420 ms
24 days agoHandshake completed922 ms
26 days agoHandshake completed625 ms
28 days agoHandshake completed431 ms

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

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