Navmds is a remote MCP server that gives an AI agent 12 tools, among them fetch, find_local_specialists, get_community_thread. It answers at https://www.navmds.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.
Research 7,400+ US doctors: search, semantic search, profiles, reviews & procedure pricing.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
fetch | Retrieve a full doctor profile by id (the slug returned from `search`). Returns {id, title, text, url, metadata}. (OpenAI connector-compatible.) Inputs: id |
find_local_specialists | Return NavMDs' curated city guide for a procedure: the ranked specialists (the city's OWN doctors first, then the nearest within an adaptive radius), the typical local price range, the average rating, the share offering free consultations, Inputs: procedure, state, city |
get_community_thread | Fetch a complete NavMDs community thread by id (the id returned by search_community, or the trailing number of a community.navmds.com/t/<slug>/<id> URL) — the original question plus every reply, in order. Use after search_community when you Inputs: id, limit |
get_doctor | Fetch a doctor's complete NavMDs profile by slug (the id returned by the search tools, or the last path segment of a navmds.com/doctor/<slug> URL). Returns specialty, locations, ratings, overview, procedures, pricing, consultation fee, FAQ Inputs: slug |
get_doctor_reviews | Return published (moderation-approved) patient reviews for a doctor by slug. Inputs: slug, limit |
get_procedure_costs | Aggregate what a procedure costs across NavMDs doctors — combining patient-reported costs and practice-website pricing. Optionally narrow to a state/city. Returns min/median/max/average plus sample practice quotes. Inputs: procedure, state, city |
list_locations | List states/cities where NavMDs has doctors, with doctor counts. Useful for grounding a location filter. Inputs: state, limit |
list_procedures | List the procedures/specialties covered by NavMDs, with the number of doctors for each. Useful for grounding a search. Inputs: limit |
search | Search NavMDs doctors by free-text query. Returns a list of {id, title, url} results. Pass an id to the `fetch` tool to retrieve the full profile. (OpenAI connector-compatible.) Inputs: query |
search_community | Search patient discussion threads on community.navmds.com — the NavMDs forum where people discuss recovery timelines, what procedures actually cost them, choosing a surgeon, and what to expect. Use this for lived-experience questions ('what Inputs: query, limit |
search_doctors | Find doctors by procedure/specialty, optionally filtered by US state and city. Uses NavMDs' pre-computed search index (fast, ranked by rating + review volume). Use this when you have a concrete procedure (e.g. 'rhinoplasty', 'botox', 'tummy Inputs: procedure, state, city, limit |
semantic_search_doctors | Search NavMDs' 7,400+ doctor directory with a natural-language query, e.g. 'board-certified facelift surgeon in Los Angeles with great reviews and free consults'. Powered by Gemini embeddings + cosine similarity over full doctor profiles. B Inputs: query, limit |
Every block below points at https://www.navmds.com/api/mcp. Pick your client and copy.
claude mcp add --transport http navmds https://www.navmds.com/api/mcp
{
"mcpServers": {
"navmds": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://www.navmds.com/api/mcp"]
}
}
}{
"mcpServers": {
"navmds": {
"url": "https://www.navmds.com/api/mcp"
}
}
}{
"servers": {
"navmds": {
"type": "http",
"url": "https://www.navmds.com/api/mcp"
}
}
}{
"context_servers": {
"navmds": {
"url": "https://www.navmds.com/api/mcp"
}
}
}{
"mcpServers": {
"navmds": {
"serverUrl": "https://www.navmds.com/api/mcp"
}
}
}{
"mcpServers": {
"navmds": {
"url": "https://www.navmds.com/api/mcp"
}
}
}name: Navmds
version: 0.0.1
schema: v1
mcpServers:
- name: Navmds
type: streamable-http
url: https://www.navmds.com/api/mcp{
"mcpServers": {
"navmds": {
"httpUrl": "https://www.navmds.com/api/mcp"
}
}
}{
"mcpServers": {
"navmds": {
"type": "http",
"url": "https://www.navmds.com/api/mcp"
}
}
}{
"mcpServers": {
"navmds": {
"url": "https://www.navmds.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fwww.navmds.com%2Fapi%2Fmcp&type=streamable_http&id=navmds&name=Navmds
It answered our last check on 22 October 2026 in 628 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
12, as returned by the server's own tools/list on 15 September 2026: fetch, find_local_specialists, get_community_thread, get_doctor, get_doctor_reviews, get_procedure_costs, list_locations, list_procedures, and 4 more.
It answered our last check on 22 October 2026 in 628 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.navmds.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.mattlsmith. Endpoint host: www.navmds.com. ARD identifier: urn:air:io.github.mattlsmith:mcp:navmds.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.