cms.nursing_home.search
Search 14 600+ Medicare/Medicaid-certified nursing homes and long-term care facilities in the US with CMS 5-star quality ratings. Filter by state, city, ZIP code, name, minimum overall rating, and ownership type (for-profit, non-profit, government). Returns CMS Certification Number (CCN), provide...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/cms.nursing-home.search.md
What cms.nursing_home.search does on Apibase
AI agents call cms.nursing_home.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | — | City or town name to filter nursing homes (partial match). Example: "Miami", "Chicago". |
name | string | — | Partial nursing home name to search (case-insensitive substring match). Example: "Sunrise", "Brookdale", "Manor". |
limit | integer | — | Maximum number of nursing homes to return (1–100, default 20). |
state | string | — | Two-letter US state abbreviation to filter nursing homes (e.g. FL, CA, TX). |
offset | integer | — | Number of results to skip for pagination (default 0). |
zip_code | string | — | 5-digit US ZIP code to filter nursing homes by location. |
min_rating | integer | — | Minimum CMS Overall Star Rating (1–5 stars). Higher ratings indicate better quality of care based on health inspections, staffing levels, and quality measures. |
ownership_type | string | — | Filter by ownership type. Common values: "For profit - Corporation", "Non profit - Corporation", "Government - State", "Government - County", "For profit - Indi |
Parameters from the server's own tool schema.
Why cms.nursing_home.search is rated Low
Queries publicly available CMS nursing home data with no side effects or modifications.
From the tool's definition Search nursing homes, filter by state/city/ZIP, returns ratings and provider information.
Attacks that exploit this kind of access
The rule that runs cms.nursing_home.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cms.nursing_home.search, this is the rule to start with:
cms.nursing_home.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every cms.nursing_home.search call is checked against it from then on.
Questions about cms.nursing_home.search
Search 14 600+ Medicare/Medicaid-certified nursing homes and long-term care facilities in the US with CMS 5-star quality ratings. Filter by state, city, ZIP code, name, minimum overall rating, and ownership type (for-profit, non-profit, government). Returns CMS Certification Number (CCN), provider name, address, phone, ownership, certified bed count, and four separate quality ratings: overall (1–5 stars), health inspection, staffing, and quality measures. Star ratings help families compare nursing homes objectively for long-term care placement. No auth — US Centers for Medicare & Medicaid Services public domain, unlimited free. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
cms.nursing_home.search accepts 8 parameters: city, name, limit, state, offset, zip_code, min_rating, ownership_type. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for cms.nursing_home.search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
cms.nursing_home.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cms.nursing_home.search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for cms.nursing_home.search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
cms.nursing_home.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue