MCP server for US nursing facility search and ownership lookup (NursingHomeDatabase).
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Public documentation for the Nursing Home Database Model Context Protocol server. It exposes US nursing facility search, detail, ownership, and owner portfolio data to AI assistants and other MCP clients.
Website: nursinghomedatabase.com
Contact: Contact page
| Transport | Streamable HTTP (JSON-RPC 2.0 over HTTPS) |
| URL | https://mcp.nursinghomedatabase.com/mcp |
| Auth | None required for discovery and tools (public access) |
Send a standard MCP session: initialize β notifications/initialized (optional; may receive HTTP 204) β tools/list β tools/call as needed.
After tools/list, you will see tools such as:
| Tool | Purpose |
|---|---|
search_facilities | Search facilities by name, geography, filters, or distance from a free-form address |
get_facility | Get one facility by CMS provider number or site slug |
get_facility_ownership | Ownership records for a facility |
search_owners | Search owners by name |
get_owner | Owner portfolio by web_owner slug |
get_data_freshness | Dataset freshness metadata |
Exact parameters and schemas are returned in the tools/list response (inputSchema per tool).
search_facilities highlightssearch_facilities supports the usual location and rating filters plus address-based distance search.
address: free-form origin address, for example 150 Corporate Woods Drive, Magnolia, TX 77354radius_miles: optional positive number; defaults to 25 when address is providedsort=distance: sorts nearest results first when using address-based searchIf the supplied address cannot be resolved to a valid location, the API returns an address-specific validation error rather than a generic internal failure.
This server is listed in the official MCP Registry as com.nursinghomedatabase/mcp.
server.json in this repository.https://registry.modelcontextprotocol.io/v0.1/servers?search=com.nursinghomedatabaseJSON discovery APIs are also available under the main site, for example:
GET https://www.nursinghomedatabase.com/api/v1/nh/capabilitiesGET https://www.nursinghomedatabase.com/api/v1/nh/... (see site documentation)MCP and REST share the same underlying data layer.
For REST callers, the facilities endpoint now supports:
GET https://www.nursinghomedatabase.com/api/v1/nh/facilities?address=150+Corporate+Woods+Drive,+Magnolia,+TX+77354GET https://www.nursinghomedatabase.com/api/v1/nh/facilities?address=150+Corporate+Woods+Drive,+Magnolia,+TX+77354&radius_miles=10GET https://www.nursinghomedatabase.com/api/v1/nh/facilities?address=150+Corporate+Woods+Drive,+Magnolia,+TX+77354&radius_miles=10&sort=distanceAdd a Streamable HTTP MCP server pointing at the URL above, for example:
Adjust field names to match your clientβs MCP configuration format.
| File | Description |
|---|---|
server.json | Published MCP Registry manifest (name, version, remote URL) |
README.md | This file |
There is no application source code in this repository; the MCP is implemented in the Nursing Home Database production environment.
Data is derived from public CMS and related sources; use is subject to the terms published on nursinghomedatabase.com. For licensing or bulk use, use the site contact form.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/nursing-home-database-2)<a href="https://allmcps.com/mcp/nursing-home-database-2"><img src="https://allmcps.com/api/badge/nursing-home-database-2?style=directory" alt="Nursing Home Database on AllMCPs" /></a>