Remote MCP · Endpoint

ResumeMD MCP server

No. ResumeMD answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://resumemd.pro/api/mcp

The last check completed an MCP handshake.

Registry name
pro.resumemd/resumemd
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
170 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Turn a Markdown resume draft into an interview-ready PDF. 32 templates, no account, nothing stored.
Listing
From the official MCP registry (active).
Recent checks of ResumeMD
CheckedResultHandshake
3 hours agoHandshake completed170 ms
2 days agoHandshake completed86 ms
4 days agoHandshake completed135 ms
5 days agoHandshake completed96 ms
7 days agoHandshake completed111 ms
8 days agoHandshake completed101 ms
9 days agoHandshake completed141 ms
12 days agoHandshake completed92 ms
13 days agoHandshake completed99 ms
15 days agoHandshake completed85 ms
16 days agoHandshake completed178 ms
17 days agoHandshake completed95 ms
18 days agoHandshake completed81 ms
19 days agoHandshake completed162 ms
20 days agoHandshake completed81 ms
21 days agoHandshake completed92 ms
22 days agoHandshake completed83 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 ResumeMD and makes no claim about it beyond what these checks measured.