# io.usefulapi/breeze-chms (remote · breeze-chms.usefulapi.io)

Manage Breeze ChMS people, tags, events, check-ins, volunteers and contributions.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-03

## Components

- remote · `breeze-chms.usefulapi.io`: 78/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-breeze-chms/breeze-chms.md), [page](https://verifymcp.io/servers/io-usefulapi-breeze-chms/breeze-chms)

## Channel facts

- Endpoint: `https://breeze-chms.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2609 tokens (~108/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/breeze-chms MCP server?

io.usefulapi/breeze-chms 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.

### Claude

```bash
claude mcp add --transport http io-usefulapi-breeze-chms 'https://breeze-chms.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-breeze-chms": {
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-breeze-chms": {
      "type": "http",
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-breeze-chms]
url = "https://breeze-chms.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-breeze-chms": {
      "type": "remote",
      "url": "https://breeze-chms.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-breeze-chms --url 'https://breeze-chms.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-breeze-chms:
    url: "https://breeze-chms.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-breeze-chms": {
      "Transport": "http",
      "Url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-breeze-chms -t streamable-http -u 'https://breeze-chms.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-breeze-chms": {
      "type": "http",
      "url": "https://breeze-chms.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-02 (score 78, +1)

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 77, +4)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.3.0

### 2026-09-30 (score 73, +55)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (24)

### `breeze_get_account_summary` (~59 tokens)

Get the account summary

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.

### `breeze_list_people` (~224 tokens)

List people

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.

Input parameters:

- `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.

### `breeze_get_person` (~92 tokens)

Get a person

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}.

Input parameters:

- `details` (boolean): Defaults to true (all information). false = only id and name.
- `person_id` (string, required): Numeric Breeze id of the person.

### `breeze_list_profile_fields` (~78 tokens)

List profile fields

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.

### `breeze_list_tags` (~86 tokens)

List tags

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.

Input parameters:

- `folder_id` (string): Numeric Breeze id of the tag folder.

### `breeze_list_events` (~186 tokens)

List events

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.

Input parameters:

- `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).

### `breeze_get_event` (~159 tokens)

Get an event instance

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.

Input parameters:

- `details` (boolean): Include description, check-in settings, etc.
- `eligible` (boolean): Include check-in eligibility details.
- `instance_id` (string, required): 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).

### `breeze_list_calendars` (~55 tokens)

List calendars

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.

### `breeze_list_attendance` (~101 tokens)

List attendance

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.

Input parameters:

- `details` (boolean): Include each attendee's profile details.
- `instance_id` (string, required): Numeric Breeze id of the event instance.
- `type` (string): person (default) = named check-ins; anonymous = head count.

### `breeze_list_forms` (~62 tokens)

List forms

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.

Input parameters:

- `archived` (boolean): true = list archived forms instead of active ones.

### `breeze_list_form_fields` (~60 tokens)

List form fields

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.

Input parameters:

- `form_id` (string, required): Numeric Breeze id of the form.

### `breeze_list_form_entries` (~81 tokens)

List form entries

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.

Input parameters:

- `details` (boolean): Include each entry's field responses.
- `form_id` (string, required): Numeric Breeze id of the form.

### `breeze_list_volunteers` (~57 tokens)

List volunteers

Volunteers scheduled for one event instance: person_id, response, comment, rsvped_on and role_ids. Breeze: GET /api/volunteers/list.

Input parameters:

- `instance_id` (string, required): Numeric Breeze id of the event instance.

### `breeze_list_account_log` (~167 tokens)

List the account log

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.

Input parameters:

- `action` (string, required): 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.

### `breeze_list_funds` (~85 tokens)

List funds

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.

Input parameters:

- `include_totals` (boolean): Include the amount given to each fund.

### `breeze_list_contributions` (~258 tokens)

List contributions

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.

Input parameters:

- `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, required): 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, required): Contributions given on or after (YYYY-MM-DD).

### `breeze_add_person` (~101 tokens)

Add a person

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.

Input parameters:

- `fields` (array): Profile fields to set (sent as fields_json).
- `first` (string, required): First name.
- `last` (string, required): Last name.

### `breeze_update_person` (~117 tokens)

Update a person

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.

Input parameters:

- `fields` (array, required): Profile fields to set (sent as fields_json).
- `person_id` (string, required): Numeric Breeze id of the person.

### `breeze_add_tag` (~83 tokens)

Create a tag

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.

Input parameters:

- `folder_id` (string): Numeric Breeze id of the folder to place the tag in (default: top level).
- `name` (string, required): Tag name, e.g. "Small Groups".

### `breeze_assign_tag` (~75 tokens)

Assign a tag to a person

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.

Input parameters:

- `person_id` (string, required): Numeric Breeze id of the person.
- `tag_id` (string, required): Numeric Breeze id of the tag.

### `breeze_unassign_tag` (~73 tokens)

Remove a tag from a person

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.

Input parameters:

- `person_id` (string, required): Numeric Breeze id of the person.
- `tag_id` (string, required): Numeric Breeze id of the tag.

### `breeze_add_event` (~183 tokens)

Add an event

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.

Input parameters:

- `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, required): Event name.
- `starts_on` (integer, required): Start time, Unix timestamp in seconds.

### `breeze_record_attendance` (~105 tokens)

Check a person in or out

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.

Input parameters:

- `direction` (string): in (default) or out.
- `instance_id` (string, required): Numeric Breeze id of the event instance.
- `person_id` (string, required): Numeric Breeze id of the person.

### `breeze_schedule_volunteer` (~62 tokens)

Schedule a volunteer

WRITE: schedule one person as a volunteer for one event instance. Breeze: GET /api/volunteers/add.

Input parameters:

- `instance_id` (string, required): Numeric Breeze id of the event instance.
- `person_id` (string, required): Numeric Breeze id of the person.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-breeze-chms/breeze-chms#diagnostics

## Score history

- 2026-10-03: 78
- 2026-10-02: 78
- 2026-10-01: 77
- 2026-09-30: 73
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/breeze-chms MCP server?

io.usefulapi/breeze-chms is an MCP server 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 io.usefulapi/breeze-chms MCP server safe to use?

io.usefulapi/breeze-chms scores 78 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 io.usefulapi/breeze-chms MCP server expose?

io.usefulapi/breeze-chms 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 io.usefulapi/breeze-chms MCP server require authentication?

Yes. io.usefulapi/breeze-chms asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.usefulapi/breeze-chms MCP server still maintained?

io.usefulapi/breeze-chms is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://breeze-chms.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-breeze-chms/breeze-chms.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-breeze-chms/breeze-chms.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-breeze-chms/breeze-chms