Remote MCP · Endpoint
inktomd MCP Server MCP server
No. inktomd MCP Server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.inktomd.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.hadirizvi093/inktomd-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 650 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Convert files, URLs, and documents to clean, AI-ready Markdown via MCP.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 650 ms |
| 1 day ago | Handshake completed | 1.34 s |
| 2 days ago | Handshake completed | 646 ms |
| 3 days ago | Handshake completed | 406 ms |
| 4 days ago | Handshake completed | 404 ms |
| 5 days ago | Handshake completed | 645 ms |
| 6 days ago | Handshake completed | 420 ms |
| 9 days ago | Handshake completed | 701 ms |
| 11 days ago | Handshake completed | 402 ms |
| 14 days ago | Handshake completed | 622 ms |
| 16 days ago | Handshake completed | 823 ms |
| 18 days ago | Handshake completed | 478 ms |
| 20 days ago | Handshake completed | 9.21 s |
| 22 days ago | Handshake completed | 434 ms |
| 24 days ago | Handshake completed | 469 ms |
| 26 days ago | Handshake completed | 669 ms |
| 27 days ago | Handshake completed | 393 ms |
| 29 days ago | Handshake completed | 709 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 inktomd MCP Server and makes no claim about it beyond what these checks measured.