io.usefulapi/elvanto
REMOTE · ELVANTO.USEFULAPI.IO · SCANNED OCT 3
Look up people, groups, service rosters, songs, follow-up flows and giving in Elvanto.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3597 tokens (~156/item across 23 items; 23 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 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
How do I install the io.usefulapi/elvanto MCP server?
io.usefulapi/elvanto is a hosted endpoint at https://elvanto.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 · elvanto.usefulapi.io
claude mcp add --transport http io-usefulapi-elvanto 'https://elvanto.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-elvanto": {
"url": "https://elvanto.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-elvanto": {
"type": "http",
"url": "https://elvanto.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-elvanto] url = "https://elvanto.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-elvanto": {
"type": "remote",
"url": "https://elvanto.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-elvanto --url 'https://elvanto.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-elvanto:
url: "https://elvanto.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-elvanto": {
"Transport": "http",
"Url": "https://elvanto.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-elvanto -t streamable-http -u 'https://elvanto.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-elvanto": {
"type": "http",
"url": "https://elvanto.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
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 3 Oct 2026 · Probed https://elvanto.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 elvanto.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://elvanto.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://elvanto.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://elvanto.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://elvanto.usefulapi.io/mcp |
| Authorisation server | https://elvanto.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://elvanto.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://elvanto.usefulapi.io/mcp | HTTPS enforced | 301 | https://elvanto.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 →
elvanto_add_person_to_flow_step Add a person to a people-flow step ~94
Put a person into a people-flow step (e.g. start a new guest's follow-up), optionally assigning a step admin. Elvanto: peopleFlows/steps/addPerson.
| Name | Type | Req | Description |
|---|---|---|---|
| assign_to | string | – | Person id of the step admin to assign them to. |
| person_id | string | yes | The person's id. |
| step_id | string | yes | The people flow step's id. |
No output schema declared.
No examples provided.
elvanto_add_person_to_group Add a person to a group ~88
Add a person to a group, optionally as Leader or Assistant Leader. Undoable by removing them from the group in Elvanto. Elvanto: groups/addPerson.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | The group's id. |
| person_id | string | yes | The person's id. |
| position | string | – | Position in the group. Omit for a regular member. |
No output schema declared.
No examples provided.
elvanto_create_calendar_event Create a calendar event ~349
Create an event on a calendar, optionally repeating. Times are 24-hour GMT. Use status "draft" to stage it unpublished. Elvanto: calendar/events/create.
| Name | Type | Req | Description |
|---|---|---|---|
| all_day | string | – | All-day event? Default no. |
| calendar_id | string | yes | Calendar id (see elvanto_list_calendars). |
| color | string | – | Hex color, e.g. #FF0000. |
| description | string | – | Description (basic HTML allowed). |
| end | string | yes | End, yyyy-mm-dd hh:mm:ss (24h, GMT). |
| locations | – | – | Location(s) to add to the event. |
| name | string | yes | Event name. |
| organizer | string | yes | Person id of the organizer. |
| register_url | string | – | Registration website URL. |
| repeat | string | – | Make it a repeating event. |
| repeat_end_date | string | – | Stop repeating at, yyyy-mm-dd hh:mm:ss (GMT). |
| repeat_frequency | integer | – | How often to repeat. Required for daily, monthly, yearly. |
| repeat_occurrences | integer | – | Number of repeats. |
| repeat_on | string | – | Weekly/fortnightly: monday..sunday. Monthly: weekday or monthday. |
| show_guest_list | string | – | Show the guest list on the event page? Default no. |
| start | string | yes | Start, yyyy-mm-dd hh:mm:ss (24h, GMT). |
| status | string | – | Visibility. Default public. |
| where | string | – | Where the event is held. |
| who_can_attend | string | – | "all" to let anyone attend; omit for invite-only. |
No output schema declared.
No examples provided.
elvanto_create_person Create a person ~324
Add a new person to the church database (e.g. a first-time guest). Returns the new person id and family id. Does not create a login. Elvanto: people/create.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | string | – | Mark the person archived (yes) or not (no). |
| category_id | string | – | People category id (see elvanto_list_people_categories). |
| contact | string | – | Mark the person a contact (yes) or not (no). |
| string | – | Email address. | |
| family_id | – | – | Family id to join an existing family, or "new" to start a new family. |
| family_relationship | string | – | Relationship within the family. |
| fields | object | – | Extra fields to set, e.g. {"gender":"Male","birthday":"1989-04-23","marital_status":"Married","departments":["Music"],"custom_<field id>":"value"}. Use *_replace / *_remove variants (e.g. departments… |
| firstname | string | yes | First name. |
| lastname | string | yes | Last name. |
| mobile | string | – | Mobile number (non-digits are stripped by Elvanto). |
| phone | string | – | Phone number (non-digits are stripped by Elvanto). |
| preferred_name | string | – | Preferred name (nickname). |
| volunteer | string | – | Mark the person a volunteer (yes) or not (no). |
No output schema declared.
No examples provided.
elvanto_get_group Get one group ~70
Fetch one group by id, optionally with its members (fields=["people"]). Elvanto: groups/getInfo.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional extra group fields: people (members and their position), categories, departments, demographics, locations. |
| id | string | yes | The group's id. |
No output schema declared.
No examples provided.
elvanto_get_person Get one person ~163
Fetch one person by id, optionally with extra fields (birthday, addresses, departments, locations, family, custom fields...). Elvanto: people/getInfo.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional extra person fields to return, e.g. gender, birthday, anniversary, school_grade, marital_status, development_child, special_needs_child, security_code, receipt_name, giving_number, mailing_a… |
| id | string | yes | The person's id. |
No output schema declared.
No examples provided.
elvanto_get_service Get one service ~115
Fetch one service by id with optional detail: service/rehearsal times, plan (order of service), volunteers roster, songs, files, notes. Elvanto: services/getInfo.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional extra service fields: series_name, service_times, rehearsal_times, other_times, plans (the order of service), volunteers (the roster: who is serving in which position, and whether confirmed)… |
| id | string | yes | The service's id. |
No output schema declared.
No examples provided.
elvanto_list_calendar_events List calendar events ~157
List calendar events between two dates, optionally for specific calendars (use "services" as a calendar to include services). Elvanto: calendar/events/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| calendar | – | – | Calendar id(s) to read from; "services" for services. |
| end | string | yes | End date (yyyy-mm-dd). |
| fields | array | – | Optional extra event fields, e.g. ["locations"]. |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| start | string | yes | Start date (yyyy-mm-dd). |
No output schema declared.
No examples provided.
elvanto_list_calendars List calendars ~30
List the church's calendars with their ids. Elvanto: calendar/getAll.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
elvanto_list_custom_fields List custom person fields ~52
List the church's custom person fields (id, name, type and allowed values). Use the id as custom_<id> in fields / search. Elvanto: people/customFields/getAll.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
elvanto_list_financial_categories List financial categories ~99
List giving / chart-of-accounts categories (funds) with ids; status 1 = active, 0 = archived. Elvanto: financial/categories/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
No output schema declared.
No examples provided.
elvanto_list_groups List groups ~161
List small groups / ministries with meeting day, time, place and frequency; add fields=["people"] to include members and leaders. Elvanto: groups/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | – | – | Only groups in this group category id (or any of these ids). |
| fields | array | – | Optional extra group fields: people (members and their position), categories, departments, demographics, locations. |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| suspended | string | – | yes = only suspended groups, no = exclude them. Default all. |
No output schema declared.
No examples provided.
elvanto_list_people List people ~291
List people in the church database, optionally filtered by category and by suspended / contact / archived status. Paginated (the response carries page, per_page, total). Elvanto: people/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | string | – | yes = only archived people, no = exclude them. Default all. |
| category_id | – | – | Only people in this people category id (or any of these ids). |
| contact | string | – | yes = only contacts, no = exclude contacts. Default all. |
| fields | array | – | Optional extra person fields to return, e.g. gender, birthday, anniversary, school_grade, marital_status, development_child, special_needs_child, security_code, receipt_name, giving_number, mailing_a… |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| suspended | string | – | yes = only suspended people, no = exclude them. Default all. |
No output schema declared.
No examples provided.
elvanto_list_people_categories List people categories ~42
List the people categories (e.g. New People, Church Members, Inactive) with their ids. Elvanto: people/categories/getAll.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
elvanto_list_people_flow_step_people List people in a flow step ~109
List the people currently in one people-flow step, with status, due date and assigned admin — e.g. who still needs a follow-up call. Not paginated. Elvanto: peopleFlows/steps/people.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned | string | – | Only people assigned to this admin (person id), or "unassigned". |
| status | string | – | Only people with this status in the step. |
| step_id | string | yes | The people flow step's id. |
No output schema declared.
No examples provided.
elvanto_list_people_flow_steps List a people flow's steps ~54
List the steps of one people flow with descriptions, instructions, due rules and admins. Elvanto: peopleFlows/steps/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| flow_id | string | yes | The people flow's id. |
No output schema declared.
No examples provided.
elvanto_list_people_flows List people flows ~49
List people flows — the church's follow-up pipelines (e.g. First Time Guest Follow Up) — with their steps and admins. Elvanto: peopleFlows/getAll.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
elvanto_list_services List services ~250
List services (upcoming by default). Add fields such as volunteers (the roster), plans (order of service) and songs to answer 'who is serving Sunday?' or 'what are we singing?'. Elvanto: services/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| all | string | – | yes = include past services too. Ignored when start/end are given. |
| end | string | – | Only services on/before this date (yyyy-mm-dd). |
| fields | array | – | Optional extra service fields: series_name, service_times, rehearsal_times, other_times, plans (the order of service), volunteers (the roster: who is serving in which position, and whether confirmed)… |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| service_types | – | – | Only these service type id(s). |
| start | string | – | Only services on/after this date (yyyy-mm-dd). |
| status | string | – | Only published or only draft services. Default both. |
No output schema declared.
No examples provided.
elvanto_list_song_arrangements List a song's arrangements ~152
List the arrangements of one song — sequence, BPM, keys, lyrics and chord chart (optionally transposed). Elvanto: songs/arrangements/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| chord_chart_key | string | – | Transpose the chord chart into this key, e.g. F#. |
| files | boolean | – | Also return attached files. |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| song_id | string | yes | The song's id (from elvanto_list_songs). |
No output schema declared.
No examples provided.
elvanto_list_songs List songs ~142
List or search the song library by title, artist or lyrics (with CCLI number, categories and locations). Elvanto: songs/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| artist | string | – | Only songs by this artist. |
| files | boolean | – | Also return attached files. |
| lyrics | string | – | Only songs whose lyrics contain this text. |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| title | string | – | Only songs whose title matches. |
No output schema declared.
No examples provided.
elvanto_list_transactions List giving transactions ~149
List giving transactions between two dates, optionally for one fund — donor, date, method, batch and per-fund amounts. Read-only: this server never writes financial records. Elvanto: financial/transactions/getAll.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | string | – | Only this financial category (fund) id. |
| end | string | yes | End date (yyyy-mm-dd). |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| start | string | yes | Start date (yyyy-mm-dd). |
No output schema declared.
No examples provided.
elvanto_search_people Search people ~318
Find people matching field values, e.g. {"email":"john@example.com"} or {"lastname":"Smith","volunteer":"yes"}. Searchable keys: firstname, preferred_name, lastname, email, phone, mobile, category_id, archived, contact, deceased, volunteer, gender, birthday, anniversary, marital_status, school_grade, security_code, receipt_name, giving_number, groups, date_added / date_modified / last_login (UTC, yyyy-mm-dd or yyyy-mm-dd hh:mm:ss; matched as on-or-after), and custom_<field id>. Use only one of archived / contact / deceased at a time. Elvanto: people/search.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | array | – | Optional extra person fields to return, e.g. gender, birthday, anniversary, school_grade, marital_status, development_child, special_needs_child, security_code, receipt_name, giving_number, mailing_a… |
| page | integer | – | Results page to retrieve (1-based). Default 1. |
| page_size | integer | – | Records per page, 1-1000. Default 100 here (Elvanto's own default is 1000). |
| search | object | yes | Field → value pairs to match. |
No output schema declared.
No examples provided.
elvanto_update_person Update a person ~339
Edit an existing person's details — name, contact info, category, flags, family, or extra fields. Only the fields you pass change. Cannot touch username, password or login status. Elvanto: people/edit.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | string | – | Mark the person archived (yes) or not (no). |
| category_id | string | – | People category id (see elvanto_list_people_categories). |
| contact | string | – | Mark the person a contact (yes) or not (no). |
| string | – | Email address. | |
| family_id | – | – | Family id to join an existing family, or "new" to start a new family. |
| family_relationship | string | – | Relationship within the family. |
| fields | object | – | Extra fields to set, e.g. {"gender":"Male","birthday":"1989-04-23","marital_status":"Married","departments":["Music"],"custom_<field id>":"value"}. Use *_replace / *_remove variants (e.g. departments… |
| firstname | string | – | First name. |
| id | string | yes | The person's id. |
| lastname | string | – | Last name. |
| mobile | string | – | Mobile number (non-digits are stripped by Elvanto). |
| phone | string | – | Phone number (non-digits are stripped by Elvanto). |
| preferred_name | string | – | Preferred name (nickname). |
| volunteer | string | – | Mark the person a volunteer (yes) or not (no). |
No output schema declared.
No examples provided.
What is the io.usefulapi/elvanto MCP server?
io.usefulapi/elvanto is an MCP server listed in the public MCP registry as io.usefulapi/elvanto. Look up people, groups, service rosters, songs, follow-up flows and giving in Elvanto. This page covers its hosted endpoint (https://elvanto.usefulapi.io/mcp).
Is the io.usefulapi/elvanto MCP server safe to use?
io.usefulapi/elvanto scores 76 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/elvanto MCP server expose?
io.usefulapi/elvanto exposes 23 tools: elvanto_list_people, elvanto_search_people, elvanto_get_person, elvanto_list_people_categories, elvanto_list_custom_fields, and 18 more. Their descriptions and schemas cost roughly 3,597 tokens of context every time the server is loaded.
Does the io.usefulapi/elvanto MCP server require authentication?
Yes. io.usefulapi/elvanto 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/elvanto MCP server still maintained?
io.usefulapi/elvanto 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.