Bankruptcy Observer vs Loppee
A side-by-side look at the Bankruptcy Observer and Loppee MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bankruptcy Observer for legal work over a hosted endpoint; choose Loppee for legal over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bankruptcy Observer when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
search_facilities, search_facilities_by_ownership, summarize_facilities.
Choose Loppee when
- You need dedicated capabilities in the Legal domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
lookup_business, get_trust_card, get_business_reviews.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 57/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 5 |
| Full listing | View Bankruptcy Observer | View Loppee |
Tools & capabilities
Bankruptcy Observer tools 12
search_facilitiesFind certified US skilled nursing facilities near an address or in a city. Filter by CMS ownership type (call list_distinct_values field=ownership first), star rating, abuse flag, high-performing icon, or Special Focus status. Returns ownership, ratings, nurse hours (HPRD), nurse/RN turnover, weighted inspection score, beds, fines, straight-line distance_miles, and maps deep-links. distance_miles is crow-flies, not drive time — use maps.google_dir / a mapping service for minutes.search_facilities_by_ownershipFind certified US SNFs by CMS ownership type (ProviderInfo.ownership). Call list_distinct_values with field=ownership first. Same result schema as search_facilities; combine with state, city, ZIP, or address.summarize_facilitiesAggregate numeric CMS ProviderInfo fields (n, mean, min, max; optional median) across certified SNFs. Prefer this over paging search_facilities for national or grouped stats. Call list_distinct_values for ownership catalogs; call list_file_dates for filedate. Facility-equal means — not bed-weighted. Missing values excluded per metric. Not causal. Not a substitute for get_facility on a named home. Rate limit 60 requests/minute.compare_facilitiesCompare up to 25 certified skilled nursing facilities by CMS CCN or web slug. Returns the same decision fields as search_facilities (ratings, nurse hours, turnover, inspection score, beds, fines, maps) as a table. Prefer this over looping get_facility against the 60 requests/minute limit.get_facility_changesMonitor one skilled nursing facility across two CMS monthly files. Defaults to latest vs the prior snapshot. Returns field-level diffs for stars, nurse hours, turnover, inspection score, abuse icon, high-performing icon, fines, and occupancy. Care Compare shows this month only — rerun after the next file.get_facilityGet one certified skilled nursing facility by CMS CCN (provnum) or web slug. Returns the same decision fields as search_facilities: ratings, nurse hours (HPRD), nurse/RN turnover, weighted inspection score, beds, fines, abuse/SFF flags, and maps deep-links. Use data_as_of as the CMS vintage; do not invent ratings or hours that are missing. Defaults to the latest monthly snapshot; pass filedate from list_file_dates for a prior month.get_facility_ownershipGet CMS ownership records for one facility — who owns or manages the building. Defaults to the latest CMS monthly snapshot; pass filedate from list_file_dates to query a prior month.search_ownersSearch nursing-home owners by name. Defaults to the latest CMS monthly snapshot; pass filedate from list_file_dates to query a prior month.get_ownerGet an owner portfolio by web_owner slug, including facility names, locations, and overall stars. Defaults to the latest CMS monthly snapshot; pass filedate from list_file_dates to query a prior month.list_file_datesList CMS monthly snapshot dates available in the database (newest first), plus the current filedate and known unpublished months. Use a returned date as filedate on other tools to retrieve a prior month instead of the latest data.list_distinct_valuesList distinct CMS ProviderInfo values and counts for a field. Omit field to see the catalog. Use field=ownership before search_facilities to get the 13 ownership types. city requires state.get_data_freshnessGet latest source dataset dates and row counts. For prior months, call list_file_dates and pass filedate to other tools.
Loppee tools 5
lookup_businessUse this when the user names a business and wants its Loppee Registry match. Returns exact and genuine-prefix name matches with stable ids, coarse public city/state, and truthful Verified, Listed, or Registry disclosure. It does not perform category discovery, accept or return caller location, or return a street address or ZIP.get_trust_cardUse this when a business is already identified and the user wants its public Loppee Trust Card. Returns the exact business status, disclosure, coarse public city/state, public facts, review context, and citation without account authority, street address, ZIP, or signed media links.get_business_reviewsUse this when the user wants the public customer reviews for one Loppee business id. Supports pagination and star-rating filters, preserves reviewer and interaction labels, masks reviewer identity, and changes nothing.explain_recommendationUse this when the user asks why a known published business is or is not recommendable on Loppee. Returns the published class, disclosure, recommendation basis, commercial-neutrality statement, and citation without exposing private weighting.compare_businessesUse this when the user wants a side-by-side comparison of two to twenty known published Loppee business ids. Returns each business's exact class, disclosure, review context, and citation; unknown or unavailable ids are listed as unresolved rather than fabricated.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Bankruptcy Observer
{
"mcpServers": {
"bankruptcy-observer-2": {
"url": "https://mcp.nursinghomedatabase.com/mcp"
}
}
}
Loppee
{
"mcpServers": {
"loppee-3": {
"url": "https://loppee.com/mcp/discovery"
}
}
}
Frequently asked questions
Bankruptcy Observer is categorized under Legal and uses a remote HTTP/SSE transport. Loppee belongs to Legal and uses a remote HTTP/SSE transport. Pick Bankruptcy Observer for legal work and Loppee for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Bankruptcy Observer has no declared pricing — check the project's own site. Loppee has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bankruptcy-observer-2 and loppee-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bankruptcy Observer has a quality signal of 57/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Loppee has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.