Remote MCP · Endpoint

com.tiraisoft/resumejson MCP server

No. com.tiraisoft/resumejson answered an MCP handshake 37 minutes ago.

UpLast checked 37 minutes ago

Server URL

https://resumejson.tiraisoft.com/mcp

The last check completed an MCP handshake.

Registry name
com.tiraisoft/resumejson
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
132 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Parse a resume or CV (PDF, DOCX, text, scan or photo) into typed JSON.
Listing
From the official MCP registry (active).
Recent checks of com.tiraisoft/resumejson
CheckedResultHandshake
37 minutes agoHandshake completed132 ms
4 days agoHandshake completed198 ms
7 days agoHandshake completed121 ms
16 days agoHandshake completed232 ms
16 days agoHandshake completed220 ms
18 days agoHandshake completed136 ms
19 days agoHandshake completed166 ms
20 days agoHandshake completed167 ms
21 days agoHandshake completed144 ms
22 days agoHandshake completed145 ms
23 days agoHandshake completed149 ms
26 days agoHandshake completed136 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 com.tiraisoft/resumejson and makes no claim about it beyond what these checks measured.