ChurchSuite MCP by usefulapi
REMOTE · CHURCHSUITE.USEFULAPI.IO
Read ChurchSuite contacts, children, small groups, rotas, events and attendance; add contact notes.
Available components
Last scanned (6 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Productivity and Notes
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3648 tokens (~145/item across 25 items; 25 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 25 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.4.0 → 1.5.0 functional
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 0
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 60
First indexed and scored.
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 18 Oct 2026 · Probed https://churchsuite.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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| 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 churchsuite.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://churchsuite.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://churchsuite.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://churchsuite.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://churchsuite.usefulapi.io/mcp |
| Authorisation server | https://churchsuite.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://churchsuite.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/churchsuite/ |
| http (plaintext) | http://churchsuite.usefulapi.io/mcp | Inconclusive | 302 | http://churchsuite.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 →
churchsuite_add_contact_note Add a note to a contact ~152
WRITE: add a new note to a contact's record in ChurchSuite (it is visible to other ChurchSuite users who can see the contact, unless private_to_me is true). Only adds a note: never edits or deletes anything, sends nothing to the contact. API: POST /addressbook/contacts/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact's numeric id. |
| content | string | yes | The note text. |
| pinned | boolean | – | Pin the note to the top of the contact's notes (default false). |
| private_to_me | boolean | – | true = only the API user can see the note (ChurchSuite visible_to.just_me). Default: no restriction. |
No output schema declared.
No examples provided.
churchsuite_get_account Get church account ~59
The church's ChurchSuite account summary: name, unique id, subdomain, time zone, currency, language and first day of week (no billing or data-protection contact details). A good first call. API: GET /account/info.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
churchsuite_get_child Get a child ~105
Get one child by id (names, date of birth, school, contact details, custom fields, consents, sites, status). Medical and additional-needs fields only with include_medical: true. API: GET /children/children/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| child_id | integer | yes | The child's numeric id. |
| include_medical | boolean | – | true = also return the medical, medical_short, doctor_details and additional_needs fields (sensitive; default false). |
No output schema declared.
No examples provided.
churchsuite_get_contact Get a contact ~74
Get one Address Book contact by id: names, sex, date of birth, marital status and spouse id, address, phones, email, job, custom fields, communication preferences, sites, status. API: GET /addressbook/contacts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact's numeric id. |
No output schema declared.
No examples provided.
churchsuite_get_event Get a calendar event ~55
Get one calendar event by id (times, status, category, location, description, visibility, sign-up options). API: GET /calendar/events/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | The event's numeric id. |
No output schema declared.
No examples provided.
churchsuite_get_small_group Get a small group ~56
Get one small group by id (schedule, location, description, custom fields, sign-up options, sites). API: GET /smallgroups/groups/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | integer | yes | The small group's numeric id. |
No output schema declared.
No examples provided.
churchsuite_list_attendance_records List attendance records ~165
List attendance records (headcounts per gathering and date: total number, total people, notes), sorted by date. Filter by gathering, weekday or a date window (YYYY-MM-DD). API: GET /attendance/records.
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | – | Only records on these weekdays. |
| gathering_ids | array | – | Only these gatherings (numeric ChurchSuite ids, up to 100). |
| is_after | string | – | Only records after this date (YYYY-MM-DD). |
| is_before | string | – | Only records before this date (YYYY-MM-DD). |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
No output schema declared.
No examples provided.
churchsuite_list_children List children ~254
Search or list children in the Children module (name, date of birth, school year, contact details, sites, status, consent flags). Medical and additional-needs fields are left out unless include_medical is true. API: GET /children/children.
| Name | Type | Req | Description |
|---|---|---|---|
| group_ids | array | – | Only these children's groups (see list_children_groups) (numeric ChurchSuite ids, up to 100). |
| include_medical | boolean | – | true = also return the medical, medical_short, doctor_details and additional_needs fields (sensitive; default false). |
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on first/last/formal name, email, mobile and address. |
| site_ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
| status | string | – | Only children with this status. |
| tag_ids | array | – | Only these tags (numeric ChurchSuite ids, up to 100). |
No output schema declared.
No examples provided.
churchsuite_list_children_groups List children's groups ~107
List the Children module's groups (classes/age groups: id, name, entry age, check-in capacity and ratio, status). API: GET /children/groups.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the group name. |
| status | string | – | – |
No output schema declared.
No examples provided.
churchsuite_list_contact_notes List contact notes ~61
List the pastoral/admin notes on a contact (content, pinned, visibility, who wrote it and when), pinned first. API: GET /addressbook/contacts/{id}/notes.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact's numeric id. |
No output schema declared.
No examples provided.
churchsuite_list_contact_tags List address book tags ~125
List Address Book tags (id, name, category, whether it is a smart tag). Use a tag id as tag_ids in list_contacts to list the people with that tag. API: GET /addressbook/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the tag name. |
No output schema declared.
No examples provided.
churchsuite_list_contacts List address book contacts ~196
Search or list adult contacts in the Address Book (name, contact details, address, sites, status, tags via tag_ids). Personal data: ask only for what you need. API: GET /addressbook/contacts.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on first/last/formal name, email, telephone, mobile and address. |
| site_ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
| status | string | – | Only contacts with this status. |
| tag_ids | array | – | Only these tags (contacts with ANY of them) (numeric ChurchSuite ids, up to 100). |
No output schema declared.
No examples provided.
churchsuite_list_event_categories List event categories ~102
List calendar categories (id, name, colour, status). Use the ids as category_ids in list_events. API: GET /calendar/categories.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the category name. |
| status | string | – | – |
No output schema declared.
No examples provided.
churchsuite_list_events List calendar events ~231
List calendar events (name, start/end, status, category, location, description, sign-up options, sites). Use starts_after/starts_before (YYYY-MM-DD) for a date window. API: GET /calendar/events.
| Name | Type | Req | Description |
|---|---|---|---|
| category_ids | array | – | Only these event categories (see list_event_categories) (numeric ChurchSuite ids, up to 100). |
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the event name. |
| sequence_id | integer | – | Only events of this recurring sequence. |
| site_ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
| starts_after | string | – | Only events starting after this date (YYYY-MM-DD). |
| starts_before | string | – | Only events starting before this date (YYYY-MM-DD). |
| status | string | – | – |
No output schema declared.
No examples provided.
churchsuite_list_gatherings List attendance gatherings ~128
List the Attendance module's gatherings (services/meetings whose attendance is counted: id, name, sites, status). API: GET /attendance/gatherings.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the gathering name. |
| site_ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
| status | string | – | – |
No output schema declared.
No examples provided.
churchsuite_list_giving_funds List giving funds ~122
List the church's giving funds (id, name, description, Gift Aid / tax-deductible flags, whether shown in Donate, status). Funds only: no donors, donations or amounts. API: GET /giving/funds.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the fund name. |
| status | string | – | – |
No output schema declared.
No examples provided.
churchsuite_list_ministries List rota ministries ~163
List the Rotas module's ministries (worship team, welcome team…: id, name, description, days, rota and rotation type, status, sites). API: GET /rotas/ministries.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these ministries (numeric ChurchSuite ids, up to 100). |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the ministry name. |
| site_ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
| statuses | array | – | Only ministries with these statuses. |
No output schema declared.
No examples provided.
churchsuite_list_ministry_members List ministry members ~174
List who serves in rota ministries (ministry id, team id, person = contact or child id, role ids). Look people up with get_contact / get_child. API: GET /rotas/ministry_members.
| Name | Type | Req | Description |
|---|---|---|---|
| ministry_ids | array | – | Only these ministries (numeric ChurchSuite ids, up to 100). |
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| role_ids | array | – | Only these roles (numeric ChurchSuite ids, up to 100). |
| team_ids | array | – | Only these teams (numeric ChurchSuite ids, up to 100). |
No output schema declared.
No examples provided.
churchsuite_list_ministry_teams List ministry teams ~123
List the teams inside rota ministries (id, ministry id, name, order). API: GET /rotas/ministry_teams.
| Name | Type | Req | Description |
|---|---|---|---|
| ministry_ids | array | – | Only these ministries (numeric ChurchSuite ids, up to 100). |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| team_ids | array | – | Only these teams (numeric ChurchSuite ids, up to 100). |
No output schema declared.
No examples provided.
churchsuite_list_plan_items List service plan items ~126
List the running order of one or more service plans (items: type, name, song arrangement, duration, start time, notes, people). API: GET /planning/plan_items.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| plan_ids | array | yes | The plan ids (from list_service_plans), up to 20. |
No output schema declared.
No examples provided.
churchsuite_list_service_plans List service plans ~174
List service plans from the Planning module (name, date, time, status, linked event, sites). API: GET /planning/plans.
| Name | Type | Req | Description |
|---|---|---|---|
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the plan name. |
| site_ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
| starts_after | string | – | Only plans dated after this date (YYYY-MM-DD). |
| starts_before | string | – | Only plans dated before this date (YYYY-MM-DD). |
| status | string | – | – |
No output schema declared.
No examples provided.
churchsuite_list_sites List sites ~70
List the church's sites (campuses/congregations: id, name, initials, address). Site ids filter contacts, children, groups, events and plans. API: GET /account/sites.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
No output schema declared.
No examples provided.
churchsuite_list_small_group_members List small group members ~214
List small group memberships (group id, person = contact or child id, status, role ids, joined date). Filter by group to get a group's members, or by contact/child to get a person's groups; look people up with get_contact / get_child. API: GET /smallgroups/members.
| Name | Type | Req | Description |
|---|---|---|---|
| child_ids | array | – | Only these children (numeric ChurchSuite ids, up to 100). |
| contact_ids | array | – | Only these contacts (numeric ChurchSuite ids, up to 100). |
| group_ids | array | – | Only these small groups (numeric ChurchSuite ids, up to 100). |
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| role_id | integer | – | Only members with this role id. |
| status | string | – | – |
No output schema declared.
No examples provided.
churchsuite_list_small_groups List small groups ~205
List small groups (home groups/life groups: name, day, time, frequency, location, description, dates, sign-up options). API: GET /smallgroups/groups.
| Name | Type | Req | Description |
|---|---|---|---|
| cluster_ids | array | – | Only these clusters (numeric ChurchSuite ids, up to 100). |
| days | array | – | Only groups meeting on these days. |
| frequency | string | – | – |
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| q | string | – | Fuzzy search on the group name and location. |
| site_ids | array | – | Only these sites (numeric ChurchSuite ids, up to 100). |
| view | string | – | Groups whose date range is in the past, active now, active or future, or future. |
No output schema declared.
No examples provided.
churchsuite_list_unavailability List rota unavailability ~204
List the dates people said they are unavailable to serve (person, description, start/end). Filter by person, ministry or a date window. API: GET /rotas/unavailability.
| Name | Type | Req | Description |
|---|---|---|---|
| child_ids | array | – | Only these children (numeric ChurchSuite ids, up to 100). |
| contact_ids | array | – | Only these contacts (numeric ChurchSuite ids, up to 100). |
| ministry_ids | array | – | Only these ministries (numeric ChurchSuite ids, up to 100). |
| order_by | string | – | Sort order, field:direction. |
| page | integer | – | Page number (default 1). Use next_page from the previous reply. |
| per_page | integer | – | Items per page, 1-100 (default 25). |
| starts_after | string | – | Only unavailability starting after this date (YYYY-MM-DD). |
| starts_before | string | – | Only unavailability starting before this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
How do I install the ChurchSuite MCP by usefulapi server?
ChurchSuite MCP by usefulapi is a hosted endpoint at https://churchsuite.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 · churchsuite.usefulapi.io
claude mcp add --transport http io-usefulapi-churchsuite 'https://churchsuite.usefulapi.io/mcp'
What is the ChurchSuite MCP by usefulapi server?
ChurchSuite MCP by usefulapi is listed in the public MCP registry as io.usefulapi/churchsuite. Read ChurchSuite contacts, children, small groups, rotas, events and attendance; add contact notes. This page covers its hosted endpoint (https://churchsuite.usefulapi.io/mcp).
Is the ChurchSuite MCP by usefulapi server safe to use?
ChurchSuite MCP by usefulapi scores 65 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 ChurchSuite MCP by usefulapi server expose?
ChurchSuite MCP by usefulapi exposes 25 tools: churchsuite_get_account, churchsuite_list_sites, churchsuite_list_contacts, churchsuite_get_contact, churchsuite_list_contact_notes, and 20 more. Their descriptions and schemas cost roughly 3,445 tokens of context every time the server is loaded.
Does the ChurchSuite MCP by usefulapi server require authentication?
Yes. ChurchSuite MCP by usefulapi 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 ChurchSuite MCP by usefulapi server still maintained?
ChurchSuite MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.