MCP server for US nursing facility search and ownership lookup (NursingHomeDatabase).
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) | Auth | None required for discovery and tools (public access) | Send a standard MCP…
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
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) | Auth | None required for discovery and tools (public access) | Send a standard MCP session: → (optional; may receive HTTP 204) → → as needed. After , you will see tools such as: |…
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.