Breeze ChMS MCP by usefulapi
REMOTE · BREEZE-CHMS.USEFULAPI.IO
Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions.
Available components
Last scanned (14 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_an_event_record_attendance_or_schedule_a_volunteer” functional
- New prompt “add_or_update_a_person_and_tag_them” functional
- New prompt “find_people_by_tag_status_or_profile_field” functional
- New prompt “review_gifts_given_in_a_date_range” functional
- New prompt “review_who_checked_in_to_an_event” functional
- New prompt “see_who_is_scheduled_to_volunteer_for_an_event” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 +1
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 +1
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 +1
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.2 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://breeze-chms.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of breeze-chms.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://breeze-chms.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/breeze-chms/ |
| http (plaintext) | http://breeze-chms.usefulapi.io/mcp | Inconclusive | 302 | http://breeze-chms.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
breeze_add_event Add an event ~183
WRITE: create an event on the church calendar, optionally as another instance of an existing series. Times are Unix timestamps in seconds. This server cannot delete events, so a mistaken event must be removed in the Breeze app. Breeze: GET /api/events/add.
| Name | Type | Req | Description |
|---|---|---|---|
| all_day | boolean | – | All-day event; only the date of starts_on is used. |
| category_id | string | – | Numeric Breeze id of the calendar to place the event on (default: main). |
| description | string | – | Event description (HTML allowed). |
| ends_on | integer | – | End time, Unix timestamp in seconds (default: one hour after start). |
| event_id | string | – | Numeric Breeze id of the existing event series to add this instance to. |
| name | string | yes | Event name. |
| starts_on | integer | yes | Start time, Unix timestamp in seconds. |
No output schema declared.
No examples provided.
breeze_add_person Add a person ~101
WRITE: create a new person profile with a first and last name, and optionally set profile fields in the same call (same field shape as breeze_update_person). Check breeze_list_people first to avoid duplicates. Returns the new profile including its id. Breeze: GET /api/people/add.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Profile fields to set (sent as fields_json). |
| first | string | yes | First name. |
| last | string | yes | Last name. |
No output schema declared.
No examples provided.
breeze_add_tag Create a tag ~83
WRITE: create a new tag, at the top level or inside a folder. Returns the new tag with its id. Breeze: GET /api/tags/add_tag.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | – | Numeric Breeze id of the folder to place the tag in (default: top level). |
| name | string | yes | Tag name, e.g. "Small Groups". |
No output schema declared.
No examples provided.
breeze_assign_tag Assign a tag to a person ~75
WRITE: add a tag to one person (e.g. put them in a small group or list). Undo with breeze_unassign_tag. Breeze: GET /api/tags/assign.
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | string | yes | Numeric Breeze id of the person. |
| tag_id | string | yes | Numeric Breeze id of the tag. |
No output schema declared.
No examples provided.
breeze_get_account_summary Get the account summary ~59
The church account this key belongs to: name, subdomain, status, timezone and country/currency. A cheap way to confirm BREEZE_SUBDOMAIN and BREEZE_API_KEY are right. Breeze: GET /api/account/summary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
breeze_get_event Get an event instance ~159
Fetch one event instance, optionally with the other instances in its series (then the response is an array of {id, start} only). Cached by Breeze, may lag up to 15 minutes. Breeze: GET /api/events/list_event.
| Name | Type | Req | Description |
|---|---|---|---|
| details | boolean | – | Include description, check-in settings, etc. |
| eligible | boolean | – | Include check-in eligibility details. |
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| schedule | boolean | – | Also return other instances in the same series. |
| schedule_direction | string | – | With schedule: instances before (default) or after this one. |
| schedule_limit | integer | – | With schedule: how many series instances, 1-100 (default 10). |
No output schema declared.
No examples provided.
breeze_get_person Get a person ~92
Fetch one person's profile by id, including address and — by default — every profile field keyed by field_id, plus family members. Pair with breeze_list_profile_fields to label the field ids. Breeze: GET /api/people/{person_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| details | boolean | – | Defaults to true (all information). false = only id and name. |
| person_id | string | yes | Numeric Breeze id of the person. |
No output schema declared.
No examples provided.
breeze_list_account_log List the account log ~167
The account's audit log for one action type (e.g. person_updated, tag_assign, contribution_added), optionally within a date range or by one user. Good for 'what changed since…' and incremental sync. Breeze: GET /api/account/list_log.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Which logged action to return (required by Breeze). |
| details | boolean | – | Include a free-form description of each action (not standardized). |
| end | string | – | Actions on or before (YYYY-MM-DD). |
| limit | integer | – | Max rows, 1-3000 (Breeze default 500). |
| start | string | – | Actions on or after (YYYY-MM-DD). |
| user_id | string | – | Numeric Breeze id of the Breeze user who made the change. |
No output schema declared.
No examples provided.
breeze_list_attendance List attendance ~101
Who checked in to one event instance (person_id, check-in time created_on, check_out), optionally with each person's details, or the anonymous head count instead. Breeze: GET /api/events/attendance/list.
| Name | Type | Req | Description |
|---|---|---|---|
| details | boolean | – | Include each attendee's profile details. |
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| type | string | – | person (default) = named check-ins; anonymous = head count. |
No output schema declared.
No examples provided.
breeze_list_calendars List calendars ~55
List the church's event calendars (id, name, color and iCal feed address). The id is the category_id for breeze_list_events and breeze_add_event. Breeze: GET /api/events/calendars/list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
breeze_list_contributions List contributions ~258
List recorded contributions (gifts) given within a date range, optionally narrowed by giver (with their family), amount, payment method, fund, envelope, batch or form. Read-only: this server never adds, edits or deletes gifts. Legacy endpoint: no longer shown on Breeze's current API reference; churches whose giving runs through Tithely may get an error. Breeze: GET /api/giving/list.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_max | number | – | Only gifts of at most this amount. |
| amount_min | number | – | Only gifts of at least this amount. |
| batches | array | – | Only these batch number ids. |
| end | string | yes | Contributions given on or before (YYYY-MM-DD). |
| envelope_number | string | – | Only gifts with this envelope number. |
| forms | array | – | Only these form ids. |
| fund_ids | array | – | Only these fund (from breeze_list_funds) ids. |
| include_family | boolean | – | With person_id: include gifts from the giver's family members. |
| method_ids | array | – | Only these payment method ids. |
| person_id | string | – | Numeric Breeze id of the giver. |
| start | string | yes | Contributions given on or after (YYYY-MM-DD). |
No output schema declared.
No examples provided.
breeze_list_events List events ~186
List event instances in a date range (default: the current month), optionally on one calendar. Each row's `id` is the INSTANCE id used by attendance, volunteer and get_event tools; `event_id` is the series. Responses are cached by Breeze and may lag up to 15 minutes. Breeze: GET /api/events.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | string | – | Numeric Breeze id of the calendar (from breeze_list_calendars). |
| details | boolean | – | Include description, check-in settings, etc. |
| eligible | boolean | – | Include who is eligible to check in (everyone / tags / forms / none). |
| end | string | – | Events on or before (YYYY-MM-DD). |
| limit | integer | – | Max events, 1-1000 (Breeze default 500). |
| start | string | – | Events on or after (YYYY-MM-DD). |
No output schema declared.
No examples provided.
breeze_list_form_entries List form entries ~81
Submissions to one form (id, created_on, person_id), and with details=true each entry's responses keyed by form field_id (see breeze_list_form_fields). Breeze: GET /api/forms/list_form_entries.
| Name | Type | Req | Description |
|---|---|---|---|
| details | boolean | – | Include each entry's field responses. |
| form_id | string | yes | Numeric Breeze id of the form. |
No output schema declared.
No examples provided.
breeze_list_form_fields List form fields ~60
The fields of one form (field_id, field_type, name, options). Form entry responses are keyed by these field_ids. Breeze: GET /api/forms/list_form_fields.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | string | yes | Numeric Breeze id of the form. |
No output schema declared.
No examples provided.
breeze_list_forms List forms ~62
List the church's online forms (id, name, url_slug, is_archived) — active ones by default, or archived ones. Breeze: GET /api/forms/list_forms.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = list archived forms instead of active ones. |
No output schema declared.
No examples provided.
breeze_list_funds List funds ~85
List giving funds (id, name, tax_deductible, is_default), optionally with the total given to each. Legacy endpoint: no longer shown on Breeze's current API reference; churches whose giving runs through Tithely may get an error. Breeze: GET /api/funds/list.
| Name | Type | Req | Description |
|---|---|---|---|
| include_totals | boolean | – | Include the amount given to each fund. |
No output schema declared.
No examples provided.
breeze_list_people List people ~224
List people in the church database, optionally filtered (by tag, status, gender, etc.) and paginated with limit/offset. Without details you get id, first_name, last_name and photo path; with details=true every profile field is returned keyed by field_id (slower). Filter keys are profile field_ids (see breeze_list_profile_fields) or special keys, e.g. {"tag_contains":"y_16681"} for people in a tag, or {"2000138015":"226-227"} for a Status field matching options 226 or 227. Breeze: GET /api/people.
| Name | Type | Req | Description |
|---|---|---|---|
| details | boolean | – | true = every profile field (slower); false/omitted = id and name only. |
| filter | object | – | Filter object, sent as Breeze's filter_json, e.g. {"tag_contains":"y_16681"}. |
| limit | integer | – | Number of people to return. Omit to return everyone (can be large). |
| offset | integer | – | People to skip, for pagination with limit. |
No output schema declared.
No examples provided.
breeze_list_profile_fields List profile fields ~78
The church's profile layout: sections, each with its fields (field_id, field_type, name) and, for multiple-choice fields, their options (option_id, name). Needed to read person details, to build list_people filters, and to write fields with breeze_add_person / breeze_update_person. Breeze: GET /api/profile.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
breeze_list_tags List tags ~86
List tags (Breeze's groups/lists) with id, name, created_on and folder_id, optionally only those in one folder. To list the people in a tag, call breeze_list_people with filter {"tag_contains":"y_<tag_id>"}. Breeze: GET /api/tags/list_tags.
| Name | Type | Req | Description |
|---|---|---|---|
| folder_id | string | – | Numeric Breeze id of the tag folder. |
No output schema declared.
No examples provided.
breeze_list_volunteers List volunteers ~57
Volunteers scheduled for one event instance: person_id, response, comment, rsvped_on and role_ids. Breeze: GET /api/volunteers/list.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | string | yes | Numeric Breeze id of the event instance. |
No output schema declared.
No examples provided.
breeze_record_attendance Check a person in or out ~105
WRITE: record attendance for one person at one event instance — check them in (default) or check them out (records when they left; checking out someone not checked in creates a record with matching in/out times). Breeze: GET /api/events/attendance/add.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | in (default) or out. |
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| person_id | string | yes | Numeric Breeze id of the person. |
No output schema declared.
No examples provided.
breeze_schedule_volunteer Schedule a volunteer ~62
WRITE: schedule one person as a volunteer for one event instance. Breeze: GET /api/volunteers/add.
| Name | Type | Req | Description |
|---|---|---|---|
| instance_id | string | yes | Numeric Breeze id of the event instance. |
| person_id | string | yes | Numeric Breeze id of the person. |
No output schema declared.
No examples provided.
breeze_unassign_tag Remove a tag from a person ~73
WRITE: remove a tag from one person. The person and the tag both remain; re-assign with breeze_assign_tag. Breeze: GET /api/tags/unassign.
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | string | yes | Numeric Breeze id of the person. |
| tag_id | string | yes | Numeric Breeze id of the tag. |
No output schema declared.
No examples provided.
breeze_update_person Update a person ~117
WRITE: set profile fields on an existing person — email, phone, address, dates, multiple-choice options, family role, and custom fields. Only the fields you pass change; the previous values are overwritten (read them first with breeze_get_person if you may need to restore them). field_id and option ids come from breeze_list_profile_fields. Breeze: GET /api/people/update.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | yes | Profile fields to set (sent as fields_json). |
| person_id | string | yes | Numeric Breeze id of the person. |
No output schema declared.
No examples provided.
How do I install the Breeze ChMS MCP by usefulapi server?
Breeze ChMS MCP by usefulapi is a hosted endpoint at https://breeze-chms.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · breeze-chms.usefulapi.io
claude mcp add --transport http io-usefulapi-breeze-chms 'https://breeze-chms.usefulapi.io/mcp'
What is the Breeze ChMS MCP by usefulapi server?
Breeze ChMS MCP by usefulapi is listed in the public MCP registry as io.usefulapi/breeze-chms. Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions. This page covers its hosted endpoint (https://breeze-chms.usefulapi.io/mcp).
Is the Breeze ChMS MCP by usefulapi server safe to use?
Breeze ChMS MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Breeze ChMS MCP by usefulapi server expose?
Breeze ChMS MCP by usefulapi exposes 24 tools: breeze_get_account_summary, breeze_list_people, breeze_get_person, breeze_list_profile_fields, breeze_list_tags, and 19 more. Their descriptions and schemas cost roughly 2,609 tokens of context every time the server is loaded.
Does the Breeze ChMS MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Breeze ChMS MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Breeze ChMS MCP by usefulapi server still maintained?
Breeze ChMS MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Breeze ChMS MCP by usefulapi server?
VerifyMCP ran 4 checks on Breeze ChMS MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Breeze ChMS MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.