Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Progenda MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read patients, calendars, appointments and open slots; book and move appointments in Progenda.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http progenda-mcp-by-usefulapi https://progenda.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# progenda_list_centers, progenda_list_calendars, progenda_list_patients and 9 more
Progenda MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 664 servers
usefulapi664 servers
25 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http progenda-mcp-by-usefulapi https://progenda.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List 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.
No parameter schema on file.
List 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.
No parameter schema on file.
List 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| center_id | integer | yes | Center id (from progenda_list_centers). |
| page | integer | no | Page number (1000 patients per page). |
| since | integer | no | Unix timestamp in seconds: return only records updated after this time (use the X-Date of your last sync). |
Get one patient by your own remote_id. Progenda API: GET /api/v2/centers/{center_id}/patients/remote_id:{remote_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| center_id | integer | yes | Center id (from progenda_list_centers). |
| remote_id | string | yes | Your own identifier for the record (the remote_id you set when you created it). |
List 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | integer | yes | Calendar id (from progenda_list_calendars). |
| start | integer | no | Only appointments from this Unix time. |
| stop | integer | no | Only appointments until this Unix time. |
| since | integer | no | Unix timestamp in seconds: return only records updated after this time (use the X-Date of your last sync). |
Get one appointment by your own remote_id. Progenda API: GET /api/v2/calendars/{calendar_id}/appointments/remote_id:{remote_id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | integer | yes | Calendar id (from progenda_list_calendars). |
| remote_id | string | yes | Your own identifier for the record (the remote_id you set when you created it). |
List 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | integer | yes | Calendar id (from progenda_list_calendars). |
Compute 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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | integer | yes | Calendar id (from progenda_list_calendars). |
| service_id | integer | yes | Service id (the Progenda id of the service). |
Create 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| center_id | integer | yes | Center id (from progenda_list_centers). |
| remote_id | string | yes | Your own identifier for the record (the remote_id you set when you created it). |
| first_name | string | yes | Patient's first name (may be blank). |
| last_name | string | yes | Patient's last name (may be blank). |
| string | yes | Patient's e-mail address (may be blank). | |
| phone_number | string | yes | Patient's phone number, preferably mobile (text reminders are sent to it; may be blank). |
| birthdate | string | no | Birthdate, yyyy-mm-dd. |
| address | string | no | Postal address. |
| notes | string | no | Personal notes about the patient. |
| language_code | string | no | Patient language code, e.g. en, fr, nl, es. |
Update 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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| center_id | integer | yes | Center id (from progenda_list_centers). |
| remote_id | string | yes | Your own identifier for the record (the remote_id you set when you created it). |
| first_name | string | yes | Patient's first name (may be blank). |
| last_name | string | yes | Patient's last name (may be blank). |
| string | yes | Patient's e-mail address (may be blank). | |
| phone_number | string | yes | Patient's phone number, preferably mobile (text reminders are sent to it; may be blank). |
| birthdate | string | no | Birthdate, yyyy-mm-dd. |
| address | string | no | Postal address. |
| notes | string | no | Personal notes about the patient. |
| language_code | string | no | Patient language code, e.g. en, fr, nl, es. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | integer | yes | Calendar id (from progenda_list_calendars). |
| remote_id | string | yes | Your own identifier for the record (the remote_id you set when you created it). |
| start | integer | yes | Start time, Unix seconds (UTC). |
| stop | integer | yes | End time, Unix seconds (UTC). |
| patient_remote_id | string | no | Your identifier of the patient (must exist in Progenda). |
| service_remote_id | string | no | Your identifier of the service (appointment type). |
| title | string | no | Title, e.g. Meeting or Lunch. |
| notes | string | no | Notes about the appointment. |
| color | string | no | Colour on the Progenda calendar, as #rrggbb. |
| status | string | no | Appointment status. A cancelled appointment cannot become booked again. |
| noshow | boolean | no | True if the patient missed the appointment. |
| patient_arrived_at | no | Unix time the patient arrived, or null. |
Change 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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| calendar_id | integer | yes | Calendar id (from progenda_list_calendars). |
| remote_id | string | yes | Your own identifier for the record (the remote_id you set when you created it). |
| start | integer | no | New start time, Unix seconds. |
| stop | integer | no | New end time, Unix seconds. |
| patient_remote_id | string | no | — |
| service_remote_id | string | no | — |
| title | string | no | — |
| notes | string | no | — |
| color | string | no | Colour on the Progenda calendar, as #rrggbb. |
| status | string | no | Appointment status. A cancelled appointment cannot become booked again. |
| noshow | boolean | no | — |
| patient_arrived_at | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Progenda MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.3.5 · scanned 8 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestcacceb4540bd632949a81a7585c61d01ea2b8351e3f3491efce3ec0f2674b04b
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| progenda_list_centers | no tags | |
| progenda_list_calendars | no tags | |
| progenda_list_patients | untrusted-input | untrusted-input: keyword "fetch" |
| progenda_get_patient | no tags | |
| progenda_list_appointments | no tags | |
| progenda_get_appointment | no tags | |
| progenda_list_services | no tags | |
| progenda_get_suggestions | no tags | |
| progenda_create_patient | state-write | state-write: declares destructiveHint: true |
| progenda_update_patient | no tags | |
| progenda_create_appointment | state-write | state-write: declares destructiveHint: true |
| progenda_update_appointment | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestcacceb4540bd6329
Scanned2026-11-08
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.5.
1.3.5
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Progenda MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.