Remote MCP · Endpoint

org.web2md/web2md MCP server

No. org.web2md/web2md answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://web2md.org/api/mcp

The last check completed an MCP handshake.

Registry name
org.web2md/web2md
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
205 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 5 checks
Described by its publisher as
MCP Server for Web2MD — convert URLs to Markdown from Claude Desktop, Cursor, etc.
Listing
From the official MCP registry (active).
Recent checks of org.web2md/web2md
CheckedResultHandshake
52 minutes agoHandshake completed205 ms
3 days agoCredentials required—
12 days agoCredentials required—
13 days agoCredentials required—
14 days agoCredentials required—

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

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