Remote MCP · Endpoint

Mash Prime MCP server

No. Mash Prime answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mashprime.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.mashprime/mashprime
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
490 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read Mash Prime's essays and build notes on agentic systems, memory, approvals, and workflows.
Listing
From the official MCP registry (active).
Recent checks of Mash Prime
CheckedResultHandshake
1 hour agoHandshake completed490 ms
9 days agoHandshake completed289 ms
10 days agoHandshake completed117 ms
11 days agoHandshake completed311 ms
12 days agoHandshake completed101 ms
14 days agoHandshake completed385 ms
14 days agoHandshake completed340 ms
15 days agoHandshake completed119 ms
17 days agoHandshake completed219 ms
19 days agoHandshake completed134 ms
21 days agoHandshake completed186 ms
24 days agoHandshake completed179 ms
26 days agoHandshake completed254 ms
28 days agoHandshake completed300 ms

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

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