Remote MCP · Endpoint

Pressmark MCP server

No. Pressmark answered an MCP handshake 36 minutes ago.

UpLast checked 36 minutes ago

Server URL

https://pressmark.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.mooshee/pressmark
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Create PDF invoices, estimates, contracts, and real estate documents. (mooshworks.com)
Listing
From the official MCP registry (active).
Recent checks of Pressmark
CheckedResultHandshake
36 minutes agoHandshake completed160 ms
3 days agoHandshake completed83 ms
13 days agoHandshake completed98 ms
14 days agoHandshake completed147 ms
15 days agoHandshake completed66 ms
16 days agoHandshake completed65 ms
17 days agoHandshake completed70 ms
18 days agoHandshake completed67 ms
19 days agoHandshake completed65 ms
20 days agoHandshake completed151 ms
22 days agoHandshake completed871 ms
25 days agoHandshake completed73 ms

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

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