Remote MCP · Endpoint

RawMark MCP server

No. RawMark answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rawmark.tech/mcp

The last check completed an MCP handshake.

Registry name
io.github.Sani96/rawmark
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
213 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Documents to Markdown: PDF, DOCX, PPTX, XLSX, HTML. Scanned PDF pages read by AI.
Listing
From the official MCP registry (active).
Recent checks of RawMark
CheckedResultHandshake
1 hour agoHandshake completed213 ms
11 hours agoHandshake completed212 ms
1 day agoHandshake completed206 ms
2 days agoHandshake completed204 ms
4 days agoHandshake completed205 ms
4 days agoHandshake completed203 ms
5 days agoHandshake completed448 ms
6 days agoHandshake completed207 ms
8 days agoHandshake completed209 ms
11 days agoHandshake completed206 ms
13 days agoHandshake completed208 ms
16 days agoHandshake completed269 ms
18 days agoHandshake completed237 ms
20 days agoHandshake completed207 ms
22 days agoHandshake completed211 ms
24 days agoHandshake completed211 ms

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

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