Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Data access / search
Read patients, calendars, appointments and open slots; book and move appointments in Progenda.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Progenda MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http progenda-mcp-by-usefulapi https://progenda.usefulapi.io/mcpCapabilities
Create an appointment in a calendar under your own remote_id, for a patient remote_id and a service remote_id. Each run creates a new appointment. Progenda API: POST /api/v2/calendars/{calendar_id}/appointments.
DiscoveredCreate a patient in a center under your own remote_id. Creates a new record each time it runs with a new remote_id; use progenda_update_patient to change an existing one. Progenda API: POST /api/v2/centers/{center_id}/patients.
DiscoveredGet one appointment by your own remote_id. Progenda API: GET /api/v2/calendars/{calendar_id}/appointments/remote_id:{remote_id}.
DiscoveredGet one patient by your own remote_id. Progenda API: GET /api/v2/centers/{center_id}/patients/remote_id:{remote_id}.
DiscoveredCompute suggested free slots in one calendar for one service. Live route: GET /api/v2/calendars/{calendar_id}/suggestions?service_id= (the route named in the docs answers 404).
DiscoveredList the appointments of one calendar, optionally between two Unix times (start, stop) or updated since a time. Progenda API: GET /api/v2/calendars/{calendar_id}/appointments.
DiscoveredList the calendars (one agenda per practitioner) your Progenda user can access. The calendar id is needed by the appointment and service tools. Progenda API: GET /api/v2/calendars.
DiscoveredList the centers (practices) your Progenda user can access. Start here: the center id is needed by the patient tools. Progenda API: GET /api/v2/centers.
DiscoveredList the patients of a center, 1000 per page. Contains personal and health-adjacent data: fetch only what the user asks for. Progenda API: GET /api/v2/centers/{center_id}/patients.
DiscoveredList the services (appointment types) of one calendar. The service remote_id is used when you create an appointment. Progenda API: GET /api/v2/calendars/{calendar_id}/services.
DiscoveredChange an appointment found by your remote_id: time, status (booked, cancelled, noshow), arrival or no-show. Send only the fields to change. Progenda API: PUT /api/v2/calendars/{calendar_id}/appointments/remote_id:{remote_id}.
DiscoveredUpdate a patient found by your own remote_id. The four contact fields are required by the API: send the current values for the ones you do not change. Progenda API: PUT /api/v2/centers/{center_id}/patients/remote_id:{remote_id}.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 49 ms | 12 |