Remote MCP · Endpoint

Mash Prime MCP server

No. Mash Prime answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
179 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 15 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
2 hours agoHandshake completed179 ms
2 days agoHandshake completed254 ms
4 days agoHandshake completed300 ms
6 days agoHandshake completed729 ms
8 days agoHandshake completed166 ms
10 days agoHandshake completed147 ms
12 days agoHandshake completed182 ms
13 days agoHandshake completed983 ms
15 days agoHandshake completed194 ms
16 days agoHandshake completed722 ms
18 days agoHandshake completed273 ms
20 days agoHandshake completed252 ms
21 days agoHandshake completed419 ms
23 days agoHandshake completed184 ms
24 days agoHandshake completed226 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 Mash Prime and makes no claim about it beyond what these checks measured.