Nursing Home Database — MCP

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

MCP endpoint


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.

Tools

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` highlights

search_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 77354
radius_miles: optional positive number; defaults to 25 when address is provided
sort=distance: sorts nearest results first when using address-based search

If the supplied address cannot be resolved to a valid location, the API returns an address-specific validation error rather than a generic internal failure.

MCP Registry

This server is listed in the official MCP Registry as com.nursinghomedatabase/mcp.

Registry metadata for clients and automation: server.json in this repository.
Search API: https://registry.modelcontextprotocol.io/v0.1/servers?search=com.nursinghomedatabase

REST API (same backend)

JSON discovery APIs are also available under the main site, for example:

GET https://www.nursinghomedatabase.com/api/v1/nh/capabilities
GET 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+77354
GET https://www.nursinghomedatabase.com/api/v1/nh/facilities?address=150+Corporate+Woods+Drive,+Magnolia,+TX+77354&radius_miles=10
GET https://www.nursinghomedatabase.com/api/v1/nh/facilities?address=150+Corporate+Woods+Drive,+Magnolia,+TX+77354&radius_miles=10&sort=distance

Example: Cursor / IDE config

Add a Streamable HTTP MCP server pointing at the URL above, for example:

{
  "mcpServers": {
    "nursing-home-database": {
      "type": "streamableHttp",
      "url": "https://mcp.nursinghomedatabase.com/mcp"
    }
  }
}

Adjust field names to match your client’s MCP configuration format.

Repository contents

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.

License and data

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.

Nursing Home Database