Funraise MCP by usefulapi
REMOTE · FUNRAISE.USEFULAPI.IO
Read Funraise supporters, donations, recurring gifts and forms; add notes, tasks and supporters.
Available components
Last scanned (3 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
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 2983 tokens (~106/item across 28 items; 28 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 64% 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 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 29 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 25 Oct 26 61
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 25 Oct 2026 · Probed https://funraise.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 funraise.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 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://funraise.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://funraise.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://funraise.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://funraise.usefulapi.io/mcp |
| Authorisation server | https://funraise.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://funraise.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/funraise/ |
| http (plaintext) | http://funraise.usefulapi.io/mcp | Inconclusive | 302 | http://funraise.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 →
funraise_complete_task Complete a task ~57
WRITE: mark a task complete (sets the completed date to now; Funraise may also log an interaction if the task automation says so). PUT /api/v1/task/{id}/complete.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_create_household_note Add a note to a household ~86
WRITE: add a note to a household's record in Funraise. Creates a new note each call. POST /api/v2/household/{id}/note.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Note text. |
| household_id | integer | yes | – |
| important | boolean | – | Mark the note important (default false). |
| title | string | yes | Note title. |
No output schema declared.
No examples provided.
funraise_create_interaction Log an interaction ~119
WRITE: log an interaction (call, email, meeting) on a supporter's record. Creates a new interaction each call. POST /api/v1/interaction.
| Name | Type | Req | Description |
|---|---|---|---|
| action_required | string | – | Type of action. |
| completed_date | string | – | When it was completed, ISO 8601, e.g. 2026-10-20T15:00:00Z. |
| description | string | – | Details of the interaction. |
| subject | string | yes | Short subject line. |
| supporter_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_create_supporter Create a supporter ~168
WRITE: create a supporter (donor) record in Funraise. Creates a new record each call, so search with funraise_list_supporters (email) first to avoid duplicates. POST /api/v1/crm/supporter.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | – |
| address2 | string | – | – |
| city | string | – | – |
| country | string | – | – |
| string | – | – | |
| email_opt_in | boolean | – | – |
| first_name | string | – | – |
| last_name | string | – | – |
| phone | string | – | – |
| postal_code | string | – | – |
| sms_opt_in | boolean | – | – |
| state | string | – | – |
| tags | string | – | Tags as one string, as Funraise stores them. |
No output schema declared.
No examples provided.
funraise_create_supporter_note Add a note to a supporter ~85
WRITE: add a note to a supporter's record in Funraise. Creates a new note each call. POST /api/v2/supporter/{id}/note.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Note text. |
| important | boolean | – | Mark the note important (default false). |
| supporter_id | integer | yes | – |
| title | string | yes | Note title. |
No output schema declared.
No examples provided.
funraise_create_task Create a task ~191
WRITE: create a task in Funraise, linked to a supporter or to a donation (give at least one). Title is 40 characters at most. Creates a new task each call. POST /api/v2/task.
| Name | Type | Req | Description |
|---|---|---|---|
| action_required | string | – | Type of action. |
| assigned_to_user_id | integer | – | Funraise user id the task is assigned to. |
| color | string | – | Task colour in Funraise, hex like #2979ff. |
| description | string | – | Task details. |
| due_date | string | – | Due date, ISO 8601, e.g. 2026-11-01T00:00:00Z. |
| supporter_id | integer | – | Supporter the task is about. |
| title | string | yes | Task title, 40 characters at most. |
| transaction_id | integer | – | Donation (transaction) the task is about. |
No output schema declared.
No examples provided.
funraise_get_address Get address ~51
One address by id (street, city, state, postal code, country, primary flag, household and supporter). GET /api/v1/address/{addressId}.
| Name | Type | Req | Description |
|---|---|---|---|
| address_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_campaign_site Get campaign site ~56
One campaign site by UUID: configuration preview (payment options, goals, form, homepage, fundraiser settings). GET /api/v1/campaignSite/{uuid}.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_site_uuid | string | yes | The campaign site UUID. |
No output schema declared.
No examples provided.
funraise_get_donation Get donation ~60
One donation by its Funraise id: amount, date, supporter, household, form, allocation, dedication, fees, UTM, subscription. GET /api/v1/crm/donation/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| donation_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_household Get household ~52
One household: name, salutation, member count, primary contact, preferred address, total giving. GET /api/v1/household/{householdId}.
| Name | Type | Req | Description |
|---|---|---|---|
| household_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_household_member Get household of a supporter ~47
The household membership of a supporter (household and supporter details). GET /api/v1/household/member/{supporterId}.
| Name | Type | Req | Description |
|---|---|---|---|
| supporter_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_interaction Get interaction ~34
One interaction by id. GET /api/v1/interaction/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| interaction_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_note Get note ~42
One note by id, with title, body, importance and author. GET /api/v2/note/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| note_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_subscription Get recurring subscription ~53
One recurring gift by id: status, frequency, amount, last and next payment date, cancel date, supporter. GET /api/v1/crm/subscription/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| subscription_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_supporter Get supporter ~52
One supporter: name, email, phone, tags, opt-ins, household, primary address, institution. GET /api/v1/crm/supporter/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| supporter_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_get_task Get task ~49
One task by id: title, description, due date, status, assigned user, supporter, linked donation. GET /api/v2/task/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_list_campaign_sites List campaign sites ~153
List campaign sites (fundraising pages), active by default or archived. Returns campaignSites with totalPageCount and totalRowCount. GET /api/v1/campaignSite/active or /archived.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_fundraisers | boolean | – | Active sites only: filter by whether peer-to-peer fundraisers are allowed. |
| archived | boolean | – | true = archived sites, otherwise active sites. |
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
No output schema declared.
No examples provided.
funraise_list_donations List donations ~228
List donations (transactions) with amount, date, supporter, form, campaign page, allocation, fees and tags. Filter by an exact transactionId, by last N hours, or by a lastUpdated timestamp; use last_id to continue from the last donation id of the previous page. GET /api/v1/crm/donation.
| Name | Type | Req | Description |
|---|---|---|---|
| last_hours | integer | – | Only donations created or changed in the last N hours. |
| last_id | integer | – | Continue after this donation id (the last id of the previous page). |
| last_updated | string | – | Only donations updated since this ISO 8601 timestamp, e.g. 2026-10-01T00:00:00Z. |
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
| transaction_id | string | – | Exact payment transaction id. |
No output schema declared.
No examples provided.
funraise_list_form_custom_questions List form custom questions ~41
The custom questions attached to a form. GET /api/v2/form/{formId}/custom-question.
| Name | Type | Req | Description |
|---|---|---|---|
| form_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_list_forms List forms ~150
List donation and event forms, filtered by type, status and version. Needs the CREATOR role on the key. GET /api/v1/form.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
| status | string | – | Form status filter, for example active or archived. |
| type | string | – | Form type filter, as shown in Funraise (for example donation or event). |
| version | string | – | Form version filter. |
No output schema declared.
No examples provided.
funraise_list_household_addresses List household addresses ~140
Addresses of a household (paginated: list, page, pageSize, totalPageCount, totalRowCount). GET /api/v1/household/{householdId}/address.
| Name | Type | Req | Description |
|---|---|---|---|
| household_id | integer | yes | – |
| order | string | – | Sort direction. |
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
| sort | string | – | Field to sort by. |
No output schema declared.
No examples provided.
funraise_list_household_notes List household notes ~125
Notes on a household's record (paginated). GET /api/v2/household/{id}/note.
| Name | Type | Req | Description |
|---|---|---|---|
| household_id | integer | yes | – |
| order | string | – | Sort direction. |
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
| sort | string | – | Field to sort by. |
No output schema declared.
No examples provided.
funraise_list_subscriptions List recurring subscriptions ~186
List recurring gifts (subscriptions) with status, frequency, amount, next payment date and supporter. The q filter is a Funraise expression (Funraise requires it; default: id > 0 order by id asc), for example: id > 10 and status = "Cancelled" order by id asc. GET /api/v1/crm/subscription.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
| q | string | – | Filter expression, e.g. id > 10 and status = "Cancelled" order by id asc. Default: id > 0 order by id asc (all subscriptions). |
No output schema declared.
No examples provided.
funraise_list_supporter_addresses List supporter addresses ~124
Addresses of a supporter (paginated). GET /api/v1/supporter/{supporterId}/address.
| Name | Type | Req | Description |
|---|---|---|---|
| order | string | – | Sort direction. |
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
| sort | string | – | Field to sort by. |
| supporter_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_list_supporter_interactions List supporter interactions ~59
The interaction log of a supporter (calls, emails, meetings): subject, description, action, assigned user, dates. GET /api/v1/interaction/donor/{donorId}.
| Name | Type | Req | Description |
|---|---|---|---|
| supporter_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_list_supporter_notes List supporter notes ~124
Notes on a supporter's record (paginated). GET /api/v2/supporter/{id}/note.
| Name | Type | Req | Description |
|---|---|---|---|
| order | string | – | Sort direction. |
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
| sort | string | – | Field to sort by. |
| supporter_id | integer | yes | – |
No output schema declared.
No examples provided.
funraise_list_supporters List supporters ~148
List supporters (donors) in the Funraise CRM, newest first as Funraise returns them. Filter by exact email or by records changed in the last N hours. GET /api/v1/crm/supporter.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Exact email address to look up. | |
| last_hours | integer | – | Only supporters created or changed in the last N hours. |
| page | integer | – | Page number. Funraise does not document whether paging starts at 0 or 1: omit it for the first page; if page 1 repeats the first page, numbering starts at 1. |
| page_size | integer | – | Records per page, 1-100. |
No output schema declared.
No examples provided.
funraise_list_user_interactions List interactions assigned to a user ~44
Interactions assigned to a Funraise user (staff member). GET /api/v1/interaction/user/{userId}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | – |
No output schema declared.
No examples provided.
How do I install the Funraise MCP by usefulapi server?
Funraise MCP by usefulapi is a hosted endpoint at https://funraise.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 · funraise.usefulapi.io
claude mcp add --transport http io-usefulapi-funraise 'https://funraise.usefulapi.io/mcp'
What is the Funraise MCP by usefulapi server?
Funraise MCP by usefulapi is listed in the public MCP registry as io.usefulapi/funraise. Read Funraise supporters, donations, recurring gifts and forms; add notes, tasks and supporters. This page covers its hosted endpoint (https://funraise.usefulapi.io/mcp).
Is the Funraise MCP by usefulapi server safe to use?
Funraise MCP by usefulapi scores 61 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 Funraise MCP by usefulapi server expose?
Funraise MCP by usefulapi exposes 28 tools: funraise_list_supporters, funraise_get_supporter, funraise_list_donations, funraise_get_donation, funraise_list_subscriptions, and 23 more. Their descriptions and schemas cost roughly 2,724 tokens of context every time the server is loaded.
Does the Funraise MCP by usefulapi server require authentication?
Yes. Funraise 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 Funraise MCP by usefulapi server still maintained?
Funraise MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.