MCP servers observed by Lowdown
org.web2md/web2md MCP server: daily status and tool changes
Answered initialize and tools/list on the latest check (2026-11-17) (Lowdown checks this server every 3 days); 7 tools listed. 1 of 3 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:org.web2md/web2md
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:org.web2md/web2md?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 1
- Required authentication: 2
- No response: 0
- Remotes differed: 0
Does it require authentication?
It returned HTTP 401/403 on 2 of 3 observed days. Lowdown checks without credentials, so the tools behind authentication were not listed.
Did its tools change recently?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
7 tools on 2026-11-17:
convert_urlget_conversionget_library_itemsget_skilllist_skillssearch_librarysemantic_search
MCP Registry declaration
- Registry name:
org.web2md/web2md - Declared version: 0.14.3
- Status: active
- Declared hosts:
web2md.org
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:org.web2md/web2md", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:org.web2md/web2md?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:org.web2md/web2md -- npx -y web2md-mcp-server
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).