Remote MCP · Endpoint

com.mart402/docs MCP server

No. com.mart402/docs answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mart402.com/mcp/docs

The last check completed an MCP handshake.

Registry name
com.mart402/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
81 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Documents and web for AI agents: PDF parse, OCR, web extract, invoice checks. x402, no API key.
Website
https://mart402.com/
Listing
From the official MCP registry (active).
Recent checks of com.mart402/docs
CheckedResultHandshake
5 hours agoHandshake completed81 ms
9 days agoHandshake completed77 ms
10 days agoHandshake completed75 ms
11 days agoHandshake completed60 ms
12 days agoHandshake completed40 ms
14 days agoHandshake completed61 ms
14 days agoHandshake completed66 ms
15 days agoHandshake completed155 ms
17 days agoHandshake completed106 ms
19 days agoHandshake completed67 ms
21 days agoHandshake completed180 ms
24 days agoHandshake completed59 ms
26 days agoHandshake completed58 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.mart402/docs and makes no claim about it beyond what these checks measured.