Practice-native
One resolved record per location. The people, the organization, and the website stay attached to that door.
Why
Built for the practice. Not retrofitted from the hospital.
PracticeMCP is the practice-level data layer for anyone who sells to, partners with, or studies US healthcare practices. Self-serve, verifiable field by field, delivered into the tools and agents you already use.
| PracticeMCP | Enterprise suites | Contact databases | Registry files | |
|---|---|---|---|---|
| Unit of record | Practice location | Hospital, IDN, claims | Company | Clinician |
| Small-practice depth | The point of the product | Thins out below the system | Weak under 20 people | Rows, not businesses |
| Field-level evidence | Source, quote, status | Usually hidden | Not provided | The file is the source |
| Self-serve access | API key | Sales-gated | Yes | Yes, as a download |
| API, MCP, and CRM | Included | Often priced as add-ons | API, rarely MCP | Not included |
| Pricing model | Usage, no seats | Annual contract | Seats | File fee |
Evidence on every field
A source, a quote, and a status. Unknown is allowed. Guessing an email, an owner, or a website is not.
Delivered where you work
API, MCP, Salesforce, HubSpot, webhooks, and bulk files. The record does not live in a portal you have to export.
When to look elsewhere
We are the wrong product for some questions.
Claims and utilization
We do not sell claims, referral flow, or what was billed. If the question is clinical volume, look at a claims house.
Hospitals and IDNs
The record is the practice location. A health system appears when it explains who operates that location, not as a hospital profile.
Patient-level data
There is no patient record, no eligibility file, and no PHI. The product is business information practices publish about themselves, plus public registries.
Start with one practice. Scale to all of them.
Get a key, read a record, and widen the query when the shape is right.