# Funraise MCP by usefulapi (remote · funraise.usefulapi.io)

Read Funraise supporters, donations, recurring gifts and forms; add notes, tasks and supporters.

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

## Components

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

## Channel facts

- Endpoint: `https://funraise.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-25.

- **Endpoint Security**: 78/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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 64% 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 28 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 29 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.

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

## Install

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

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-funraise": {
      "type": "http",
      "url": "https://funraise.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-25 (score 61)

First indexed and scored.

## MCP tools (28)

### `funraise_list_supporters` (~148 tokens)

List supporters

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.

Input parameters:

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

### `funraise_get_supporter` (~52 tokens)

Get supporter

One supporter: name, email, phone, tags, opt-ins, household, primary address, institution. GET /api/v1/crm/supporter/{id}.

Input parameters:

- `supporter_id` (integer, required)

### `funraise_list_donations` (~228 tokens)

List donations

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.

Input parameters:

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

### `funraise_get_donation` (~60 tokens)

Get donation

One donation by its Funraise id: amount, date, supporter, household, form, allocation, dedication, fees, UTM, subscription. GET /api/v1/crm/donation/{id}.

Input parameters:

- `donation_id` (integer, required)

### `funraise_list_subscriptions` (~186 tokens)

List recurring subscriptions

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.

Input parameters:

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

### `funraise_get_subscription` (~53 tokens)

Get recurring subscription

One recurring gift by id: status, frequency, amount, last and next payment date, cancel date, supporter. GET /api/v1/crm/subscription/{id}.

Input parameters:

- `subscription_id` (integer, required)

### `funraise_list_forms` (~150 tokens)

List forms

List donation and event forms, filtered by type, status and version. Needs the CREATOR role on the key. GET /api/v1/form.

Input parameters:

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

### `funraise_list_campaign_sites` (~153 tokens)

List campaign sites

List campaign sites (fundraising pages), active by default or archived. Returns campaignSites with totalPageCount and totalRowCount. GET /api/v1/campaignSite/active or /archived.

Input parameters:

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

### `funraise_get_campaign_site` (~56 tokens)

Get campaign site

One campaign site by UUID: configuration preview (payment options, goals, form, homepage, fundraiser settings). GET /api/v1/campaignSite/{uuid}.

Input parameters:

- `campaign_site_uuid` (string, required): The campaign site UUID.

### `funraise_list_form_custom_questions` (~41 tokens)

List form custom questions

The custom questions attached to a form. GET /api/v2/form/{formId}/custom-question.

Input parameters:

- `form_id` (integer, required)

### `funraise_get_household` (~52 tokens)

Get household

One household: name, salutation, member count, primary contact, preferred address, total giving. GET /api/v1/household/{householdId}.

Input parameters:

- `household_id` (integer, required)

### `funraise_get_household_member` (~47 tokens)

Get household of a supporter

The household membership of a supporter (household and supporter details). GET /api/v1/household/member/{supporterId}.

Input parameters:

- `supporter_id` (integer, required)

### `funraise_list_household_addresses` (~140 tokens)

List household addresses

Addresses of a household (paginated: list, page, pageSize, totalPageCount, totalRowCount). GET /api/v1/household/{householdId}/address.

Input parameters:

- `household_id` (integer, required)
- `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.

### `funraise_list_supporter_addresses` (~124 tokens)

List supporter addresses

Addresses of a supporter (paginated). GET /api/v1/supporter/{supporterId}/address.

Input parameters:

- `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, required)

### `funraise_get_address` (~51 tokens)

Get address

One address by id (street, city, state, postal code, country, primary flag, household and supporter). GET /api/v1/address/{addressId}.

Input parameters:

- `address_id` (integer, required)

### `funraise_list_supporter_notes` (~124 tokens)

List supporter notes

Notes on a supporter's record (paginated). GET /api/v2/supporter/{id}/note.

Input parameters:

- `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, required)

### `funraise_list_household_notes` (~125 tokens)

List household notes

Notes on a household's record (paginated). GET /api/v2/household/{id}/note.

Input parameters:

- `household_id` (integer, required)
- `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.

### `funraise_get_note` (~42 tokens)

Get note

One note by id, with title, body, importance and author. GET /api/v2/note/{id}.

Input parameters:

- `note_id` (integer, required)

### `funraise_list_supporter_interactions` (~59 tokens)

List supporter interactions

The interaction log of a supporter (calls, emails, meetings): subject, description, action, assigned user, dates. GET /api/v1/interaction/donor/{donorId}.

Input parameters:

- `supporter_id` (integer, required)

### `funraise_list_user_interactions` (~44 tokens)

List interactions assigned to a user

Interactions assigned to a Funraise user (staff member). GET /api/v1/interaction/user/{userId}.

Input parameters:

- `user_id` (integer, required)

### `funraise_get_interaction` (~34 tokens)

Get interaction

One interaction by id. GET /api/v1/interaction/{id}.

Input parameters:

- `interaction_id` (integer, required)

### `funraise_get_task` (~49 tokens)

Get task

One task by id: title, description, due date, status, assigned user, supporter, linked donation. GET /api/v2/task/{id}.

Input parameters:

- `task_id` (integer, required)

### `funraise_create_supporter_note` (~85 tokens)

Add a note to a supporter

WRITE: add a note to a supporter's record in Funraise. Creates a new note each call. POST /api/v2/supporter/{id}/note.

Input parameters:

- `body` (string, required): Note text.
- `important` (boolean): Mark the note important (default false).
- `supporter_id` (integer, required)
- `title` (string, required): Note title.

### `funraise_create_household_note` (~86 tokens)

Add a note to a household

WRITE: add a note to a household's record in Funraise. Creates a new note each call. POST /api/v2/household/{id}/note.

Input parameters:

- `body` (string, required): Note text.
- `household_id` (integer, required)
- `important` (boolean): Mark the note important (default false).
- `title` (string, required): Note title.

### `funraise_create_interaction` (~119 tokens)

Log an interaction

WRITE: log an interaction (call, email, meeting) on a supporter's record. Creates a new interaction each call. POST /api/v1/interaction.

Input parameters:

- `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, required): Short subject line.
- `supporter_id` (integer, required)

### `funraise_create_task` (~191 tokens)

Create a task

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.

Input parameters:

- `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, required): Task title, 40 characters at most.
- `transaction_id` (integer): Donation (transaction) the task is about.

### `funraise_complete_task` (~57 tokens)

Complete a task

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.

Input parameters:

- `task_id` (integer, required)

### `funraise_create_supporter` (~168 tokens)

Create a supporter

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.

Input parameters:

- `address1` (string)
- `address2` (string)
- `city` (string)
- `country` (string)
- `email` (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.

## Diagnostics

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

## Score history

- 2026-10-25: 61

## Common questions

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

## Links

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