Remote MCP · Endpoint

Palmyr MCP server

No. Palmyr answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://palmyr.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.palmyr/palmyr
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
3.26 s
Tools exposed
33 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agent infra: email, phone, social, domains, VPS, wallets. Paid per-action via x402, no API key.
Listing
From the official MCP registry (active).
Recent checks of Palmyr
CheckedResultHandshake
8 hours agoHandshake completed3.26 s
2 days agoHandshake completed420 ms
4 days agoHandshake completed410 ms
5 days agoHandshake completed394 ms
7 days agoHandshake completed486 ms
8 days agoHandshake completed1.10 s
9 days agoHandshake completed336 ms
12 days agoHandshake completed369 ms
13 days agoHandshake completed444 ms
15 days agoHandshake completed419 ms
16 days agoHandshake completed471 ms
17 days agoHandshake completed552 ms
18 days agoHandshake completed403 ms
19 days agoHandshake completed390 ms
20 days agoHandshake completed435 ms
21 days agoHandshake completed486 ms
23 days agoHandshake completed611 ms

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

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