io.github.mattlsmith/navmds
REMOTE · WWW.NAVMDS.COM
Research 7,400+ US doctors: search, semantic search, profiles, reviews & procedure pricing.
Available components
Last scanned (11 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1381 tokens (~115/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Oct 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 28 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 17 Oct 26 +6
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- 16 Oct 26 −6
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://www.navmds.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=navmds.com | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d885e596999e10a2138402d4ffcbc970 |
| SANs: navmds.com, *.navmds.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.navmds.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| navmds.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.navmds.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.navmds.com/api/mcp | HTTPS enforced | 302 | https://www.navmds.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch Fetch document (connector-compatible) ~54
Retrieve a full doctor profile by id (the slug returned from `search`). Returns {id, title, text, url, metadata}. (OpenAI connector-compatible.)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Doctor slug returned by the search tool. |
No output schema declared.
No examples provided.
find_local_specialists Curated 'best {procedure} doctors in {city}' guide ~224
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, and the canonical navmds.com page URL to cite. This is the best tool for 'who are the best <procedure> doctors in <city>' questions — it mirrors NavMDs' editorial city pages. If no curated guide exists for that city+procedure, it says so; fall back to search_doctors with a nearby larger city.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City name, e.g. 'Beverly Hills', 'Miami'. This is the area the user asked about, not the user's own location. |
| procedure | string | yes | Procedure/specialty, e.g. 'rhinoplasty', 'breast augmentation', 'botox'. |
| state | string | yes | US state name, e.g. 'California', 'Florida'. This is the area the user asked about, not the user's own location. |
No output schema declared.
No examples provided.
get_community_thread Get a full community discussion ~116
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 need the actual answers rather than an excerpt. Community posts are patient discussion, not medical advice.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Community topic id, e.g. 117. |
| limit | integer | – | Max posts to return (default 30). |
No output schema declared.
No examples provided.
get_doctor Get full doctor profile ~87
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 and verification status.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Doctor slug, e.g. 'dr-jane-smith-md'. |
No output schema declared.
No examples provided.
get_doctor_reviews Get patient reviews for a doctor ~47
Return published (moderation-approved) patient reviews for a doctor by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max reviews (default 20). |
| slug | string | yes | Doctor slug. |
No output schema declared.
No examples provided.
get_procedure_costs Get pricing for a procedure ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City filter. This is the area the user asked about, not the user's own location. |
| procedure | string | yes | Procedure name, e.g. 'rhinoplasty'. |
| state | string | – | US state filter. This is the area the user asked about, not the user's own location. |
No output schema declared.
No examples provided.
list_locations List covered locations ~61
List states/cities where NavMDs has doctors, with doctor counts. Useful for grounding a location filter.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max locations (default 150, ordered by doctor count). |
| state | string | – | Filter to a single state name. |
No output schema declared.
No examples provided.
list_procedures List available procedures ~54
List the procedures/specialties covered by NavMDs, with the number of doctors for each. Useful for grounding a search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max procedures (default 100, ordered by doctor count). |
No output schema declared.
No examples provided.
search Search (connector-compatible) ~62
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.)
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text search query. |
No output schema declared.
No examples provided.
search_community Search NavMDs community discussions ~163
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 is rhinoplasty recovery like', 'how much did people actually pay for a tummy tuck', 'how do I pick a surgeon') where the doctor-directory tools can't help. Returns thread titles, categories, excerpts and canonical URLs; pass an id to get_community_thread for the full discussion. Community posts are patient discussion, not medical advice.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max threads (default 10). |
| query | string | yes | Free-text search, e.g. 'rhinoplasty recovery swelling' or 'tummy tuck cost'. |
No output schema declared.
No examples provided.
search_doctors Search doctors by procedure & location ~190
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 tuck'). For open-ended natural-language queries, use semantic_search_doctors instead.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, e.g. 'Miami'. This is the area the user asked about, not the user's own location. |
| limit | integer | – | Max results (default 20). |
| procedure | string | yes | Procedure or specialty, e.g. 'rhinoplasty', 'breast augmentation', 'botox'. |
| state | string | – | US state name, e.g. 'California' or 'Florida'. This is the area the user asked about, not the user's own location. |
No output schema declared.
No examples provided.
semantic_search_doctors Natural-language doctor search ~99
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. Best tool for open-ended or multi-attribute questions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 15). |
| query | string | yes | Natural-language description of the doctor you're looking for. |
No output schema declared.
No examples provided.
How do I install the io.github.mattlsmith/navmds MCP server?
io.github.mattlsmith/navmds is a hosted endpoint at https://www.navmds.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.navmds.com
claude mcp add --transport http mattlsmith-navmds 'https://www.navmds.com/api/mcp'
What is the io.github.mattlsmith/navmds MCP server?
io.github.mattlsmith/navmds is an MCP server listed in the public MCP registry as io.github.mattlsmith/navmds. Research 7,400+ US doctors: search, semantic search, profiles, reviews & procedure pricing. This page covers its hosted endpoint (https://www.navmds.com/api/mcp).
Is the io.github.mattlsmith/navmds MCP server safe to use?
io.github.mattlsmith/navmds scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.mattlsmith/navmds MCP server expose?
io.github.mattlsmith/navmds exposes 12 tools: search_doctors, find_local_specialists, semantic_search_doctors, get_doctor, get_doctor_reviews, and 7 more. Their descriptions and schemas cost roughly 1,277 tokens of context every time the server is loaded.
Does the io.github.mattlsmith/navmds MCP server require authentication?
No. We connected to io.github.mattlsmith/navmds without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.mattlsmith/navmds MCP server still maintained?
io.github.mattlsmith/navmds is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.mattlsmith/navmds MCP server?
VerifyMCP ran 13 checks on io.github.mattlsmith/navmds, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.