# io.usefulapi/bloomerang (remote · bloomerang.usefulapi.io)

Search Bloomerang constituents and donations; log interactions, notes and tasks.

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

## Components

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

## Channel facts

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

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

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

## Install

### How do I install the io.usefulapi/bloomerang MCP server?

io.usefulapi/bloomerang is a hosted endpoint at https://bloomerang.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-bloomerang 'https://bloomerang.usefulapi.io/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-bloomerang": {
      "type": "http",
      "url": "https://bloomerang.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-04 (score 77, +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.

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

- [functional] Server version: 1.3.0 → 1.5.1

### 2026-10-01 (score 75, +5)

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

### 2026-09-30 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (20)

### `bloomerang_get_current_user` (~55 tokens)

Get the current user

Fetch the Bloomerang user the API key belongs to — name, email and permission level. A cheap way to confirm the key works and see what it may do. Bloomerang: GET /user/current.

### `bloomerang_search_constituents` (~117 tokens)

Search constituents

Full-text search across constituents (individuals and organizations) and households by name, email, etc. Start here to find a donor's Id. Bloomerang: GET /constituents/search.

Input parameters:

- `search` (string, required): Text to search for, e.g. a name or email.
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.
- `type` (string): Only this record type.

### `bloomerang_list_constituents` (~206 tokens)

List constituents

List constituents with filters — by Id, type, favorites, last-modified date, or a custom field value — and sorting. Good for syncing recent changes. Bloomerang: GET /constituents.

Input parameters:

- `custom_field_id` (integer): Custom field Id to filter by.
- `custom_field_value` (string): Custom field value to filter by.
- `ids` (array): Only these constituent Ids.
- `is_favorite` (boolean): Only constituents the key's user has favorited.
- `last_modified` (string): Only records last modified after this date/time (ISO 8601, e.g. 2026-01-31).
- `order_by` (string)
- `order_direction` (string): Sort direction.
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.
- `type` (string)

### `bloomerang_get_constituent` (~71 tokens)

Get one constituent

Fetch one constituent's full profile — names, primary and secondary contact details, household, communication preferences, engagement score and custom values. Bloomerang: GET /constituent/{id}.

Input parameters:

- `constituent_id` (integer, required): The API Id of the constituent (not the CRM AccountNumber).

### `bloomerang_get_constituent_timeline` (~117 tokens)

Get a constituent's timeline

The activity timeline for a constituent — gifts, interactions, notes, tasks and more, newest first. Pass a household Id to get the timeline of every member. Bloomerang: GET /constituent/{id}/timeline.

Input parameters:

- `constituent_id` (integer, required): The API Id of the constituent or household (not the CRM AccountNumber).
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_list_constituent_relationships` (~138 tokens)

List a constituent's relationships

Relationships between this constituent and others (spouse, employer, board member ...), with the role on each side. Bloomerang: GET /constituent/{id}/relationships.

Input parameters:

- `constituent_id` (integer, required): The API Id of the constituent (not the CRM AccountNumber).
- `last_modified` (string): Only records last modified after this date/time (ISO 8601, e.g. 2026-01-31).
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_get_household` (~71 tokens)

Get one household

Fetch a household — its names, head of household (HeadId) and member constituent Ids. A constituent's HouseholdId points here. Bloomerang: GET /household/{id}.

Input parameters:

- `household_id` (integer, required): The API Id of the household (not the CRM AccountNumber).

### `bloomerang_list_transactions` (~242 tokens)

List transactions (gifts)

List transactions — donations, pledges, pledge payments, recurring donations and their payments — with their designations (fund, campaign, appeal). Filter by constituent, amount range, type or last-modified date. Read only. Bloomerang: GET /transactions.

Input parameters:

- `constituent_ids` (array): Only these constituent (AccountId) Ids.
- `ids` (array): Only these transaction Ids.
- `last_modified` (string): Only records last modified after this date/time (ISO 8601, e.g. 2026-01-31).
- `max_amount` (number): Maximum amount, inclusive.
- `min_amount` (number): Minimum amount, inclusive.
- `order_by` (string): Default Date.
- `order_direction` (string): Sort direction (default Desc).
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.
- `transaction_numbers` (array): Only these TransactionNumbers (called Payment Number in CRM reporting).
- `types` (array): Only transactions with at least one designation of these types.

### `bloomerang_get_transaction` (~68 tokens)

Get one transaction

Fetch one transaction with its payment method, amounts, refund status and every designation (fund, campaign, appeal, tribute, acknowledgement status). Bloomerang: GET /transaction/{id}.

Input parameters:

- `transaction_id` (integer, required): The API Id of the transaction (not the CRM AccountNumber).

### `bloomerang_list_funds` (~134 tokens)

List funds

List the funds gifts can be designated to (e.g. General Operating, Scholarship). Bloomerang: GET /funds.

Input parameters:

- `ids` (array): Only these record Ids.
- `is_active` (boolean): Only active (true) or inactive (false).
- `is_default` (boolean): Only the default (true) or non-default (false) fund.
- `search` (string): Only names containing this text.
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_list_campaigns` (~160 tokens)

List campaigns

List fundraising campaigns with their goals and dates. Bloomerang: GET /campaigns.

Input parameters:

- `has_goal` (boolean): Only campaigns with a non-zero (true) or zero (false) goal.
- `ids` (array): Only these record Ids.
- `is_active` (boolean): Only active (true) or inactive (false).
- `last_modified` (string): Only records last modified after this date/time (ISO 8601, e.g. 2026-01-31).
- `search` (string): Only names containing this text.
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_list_appeals` (~151 tokens)

List appeals

List appeals — the specific asks (a year-end letter, a gala invitation) that gifts are attributed to. Bloomerang: GET /appeals.

Input parameters:

- `ids` (array): Only these record Ids.
- `is_active` (boolean): Only active (true) or inactive (false).
- `last_modified` (string): Only records last modified after this date/time (ISO 8601, e.g. 2026-01-31).
- `search` (string): Only names containing this text.
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_list_interactions` (~141 tokens)

List interactions

List logged interactions (calls, emails, meetings, letters ...) — filter by constituent, channel or purpose. Bloomerang: GET /interactions.

Input parameters:

- `channels` (array): Only these channels.
- `constituent_ids` (array): Only these constituent Ids.
- `ids` (array): Only these interaction Ids.
- `order_by` (string): Default Date.
- `order_direction` (string): Sort direction.
- `purposes` (array): Only these purposes.
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_list_notes` (~106 tokens)

List notes

List notes, optionally for specific constituents. Bloomerang: GET /notes.

Input parameters:

- `constituent_ids` (array): Only these constituent Ids.
- `ids` (array): Only these note Ids.
- `order_by` (string): Default Date.
- `order_direction` (string): Sort direction.
- `skip` (integer): Records to skip (offset). Default 0.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_list_tasks` (~201 tokens)

List tasks

List tasks (follow-ups) — filter by status, due-date range, assignee user, constituent, channel or purpose. Bloomerang: GET /tasks.

Input parameters:

- `assignee_user_ids` (array): Only tasks assigned to these user Ids.
- `channels` (array)
- `constituent_ids` (array): Only these constituent Ids.
- `ids` (array): Only these task Ids.
- `max_due_date` (string): Due on or before this date (YYYY-MM-DD).
- `min_due_date` (string): Due on or after this date (YYYY-MM-DD).
- `order_by` (string)
- `order_direction` (string): Sort direction.
- `purposes` (array)
- `skip` (integer): Records to skip (offset). Default 0.
- `statuses` (array): Only these statuses.
- `take` (integer): Page size, 1-50. Default 50.

### `bloomerang_create_constituent` (~274 tokens)

Create a constituent

WRITE: create a new individual or organization constituent. For an individual give first_name/last_name; for an organization give full_name. Search first (bloomerang_search_constituents) to avoid creating a duplicate donor. Bloomerang: POST /constituent.

Input parameters:

- `birthdate` (string): Birth date (YYYY-MM-DD).
- `employer` (string)
- `envelope_name` (string)
- `first_name` (string)
- `formal_name` (string)
- `full_name` (string): Organization name, or an explicit individual full name.
- `gender` (string)
- `informal_name` (string)
- `job_title` (string)
- `last_name` (string)
- `middle_name` (string)
- `prefix` (string): Must match a prefix configured in the CRM, e.g. Mr., Ms., Dr.
- `primary_address` (object): Primary postal address.
- `primary_email` (object): Primary email address.
- `primary_phone` (object): Primary phone.
- `recognition_name` (string)
- `status` (string): Constituent status.
- `suffix` (string): Must match a suffix configured in the CRM.
- `type` (string, required): Record type.
- `website` (string)

### `bloomerang_update_constituent` (~273 tokens)

Update a constituent

WRITE: update fields on an existing constituent's profile (names, job, status, primary address/email/phone). Only the fields you supply are sent. Bloomerang: PUT /constituent/{id}.

Input parameters:

- `birthdate` (string): Birth date (YYYY-MM-DD).
- `constituent_id` (integer, required): The API Id of the constituent (not the CRM AccountNumber).
- `employer` (string)
- `envelope_name` (string)
- `first_name` (string)
- `formal_name` (string)
- `full_name` (string): Organization name, or an explicit individual full name.
- `gender` (string)
- `informal_name` (string)
- `job_title` (string)
- `last_name` (string)
- `middle_name` (string)
- `prefix` (string): Must match a prefix configured in the CRM, e.g. Mr., Ms., Dr.
- `primary_address` (object): Primary postal address.
- `primary_email` (object): Primary email address.
- `primary_phone` (object): Primary phone.
- `recognition_name` (string)
- `status` (string): Constituent status.
- `suffix` (string): Must match a suffix configured in the CRM.
- `website` (string)

### `bloomerang_create_interaction` (~132 tokens)

Log an interaction

WRITE: log an interaction with a constituent — a call, email, meeting, letter, etc. — on their timeline. Bloomerang: POST /interaction.

Input parameters:

- `channel` (string, required): How it happened.
- `constituent_id` (integer, required): The API Id of the constituent (not the CRM AccountNumber).
- `date` (string, required): When it happened (YYYY-MM-DD).
- `is_inbound` (boolean): True if the constituent initiated it.
- `note` (string): Details.
- `purpose` (string, required): Why it happened.
- `subject` (string, required): Short subject line.

### `bloomerang_create_note` (~73 tokens)

Add a note

WRITE: add a note to a constituent's record. Bloomerang: POST /note.

Input parameters:

- `constituent_id` (integer, required): The API Id of the constituent (not the CRM AccountNumber).
- `date` (string, required): Note date (YYYY-MM-DD).
- `note` (string, required): The note text.

### `bloomerang_create_task` (~157 tokens)

Create a task

WRITE: create a follow-up task, optionally tied to a constituent and assigned to a user (find user Ids via bloomerang_get_current_user or existing tasks). Bloomerang: POST /task.

Input parameters:

- `assignee_user_id` (integer): User Id to assign it to.
- `channel` (string): Planned channel.
- `constituent_id` (integer): Constituent the task is about.
- `due_date` (string, required): Due date (YYYY-MM-DD).
- `note` (string): Details.
- `purpose` (string): Planned purpose.
- `send_notifications` (boolean): If true, Bloomerang emails the assignee about the task. Default false.
- `subject` (string, required): Short subject line.

## Diagnostics

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

## Score history

- 2026-10-04: 77
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 75
- 2026-09-30: 70
- 2026-09-29: 70

## Common questions

### What is the io.usefulapi/bloomerang MCP server?

io.usefulapi/bloomerang is an MCP server listed in the public MCP registry as io.usefulapi/bloomerang. Search Bloomerang constituents and donations; log interactions, notes and tasks. This page covers its hosted endpoint (https://bloomerang.usefulapi.io/mcp).

### Is the io.usefulapi/bloomerang MCP server safe to use?

io.usefulapi/bloomerang scores 77 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/bloomerang MCP server expose?

io.usefulapi/bloomerang exposes 20 tools: bloomerang_get_current_user, bloomerang_search_constituents, bloomerang_list_constituents, bloomerang_get_constituent, bloomerang_get_constituent_timeline, and 15 more. Their descriptions and schemas cost roughly 2,887 tokens of context every time the server is loaded.

### Does the io.usefulapi/bloomerang MCP server require authentication?

Yes. io.usefulapi/bloomerang 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/bloomerang MCP server still maintained?

io.usefulapi/bloomerang is still listed as active in the MCP registry. We last reached this channel on 4 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://bloomerang.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-bloomerang/bloomerang.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-bloomerang/bloomerang.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-bloomerang/bloomerang