10 actions in 3 pieces of software · ranked by words, meaning and measured trust · 640 ms
- 1tetralfound in code, not yet checkedno passport yet
MCP servertetral-ai/tetral
- memory
- 2com.jamesrosingmd/tebrafound in code, not yet checkedno passport yet
- tebra_get_patient
Get a full patient record from Tebra by patient ID, or by external system ID (optionally scoped to an external vendor). Includes demographics, contact info, cases, insurance policies, and authorizations. Insurance policy and group numbers are omitted unless named in `fields`.
- tebra_get_procedure_codes
Get procedure codes configured in the Tebra practice. Optionally filter by CPT code, active status, or customer-specific codes. Returns codes with official names, descriptions, and default units.
- tebra_get_patient_authorizations
Get all insurance authorizations for a Tebra patient across all cases and policies. Returns auth number, approved/used/remaining visits, start/end dates, computed status (active/exhausted/expired/pending), payer contact info, and an expiring-soon warning.
- tebra_create_patient
Create a new patient in Tebra with demographics, address, insurance, and guarantor information. The practice is required by Tebra; if practiceName/practiceId are omitted, the account's first practice is used automatically.
- tebra_get_encounter
Get encounter details from Tebra by encounter ID, including patient, providers, status, service dates, place of service, and service line IDs.
- tebra_get_appointments
Get appointments from Tebra within a date range. Filter by resource (provider name), patient, confirmation status, service location, reason, type, and more. To filter by provider, use resourceName with the provider full name (the WSDL has no provider ID filter).
- tebra_get_practices
Get all practices associated with the Tebra account. Returns practice IDs, names, NPI, tax ID, and contact info.
- tebra_create_document
Tebra patient ID
- tebra_get_patient
APIrecord
- users.chats.tabs.GetTeamsApp
Get teamsApp from users
- users.chats.tabs.GetTeamsApp
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.