io.usefulapi/bloomerang
REMOTE · BLOOMERANG.USEFULAPI.IO · SCANNED OCT 4
Search Bloomerang constituents and donations; log interactions, notes and tasks.
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 2887 tokens (~144/item across 20 items; 20 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% 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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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/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.
remote · bloomerang.usefulapi.io
claude mcp add --transport http io-usefulapi-bloomerang 'https://bloomerang.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-bloomerang": {
"url": "https://bloomerang.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-bloomerang": {
"type": "http",
"url": "https://bloomerang.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-bloomerang] url = "https://bloomerang.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-bloomerang": {
"type": "remote",
"url": "https://bloomerang.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-bloomerang --url 'https://bloomerang.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-bloomerang:
url: "https://bloomerang.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-bloomerang": {
"Transport": "http",
"Url": "https://bloomerang.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-bloomerang -t streamable-http -u 'https://bloomerang.usefulapi.io/mcp'
{
"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.
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.
- 4 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.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Sept 26 70
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 5 Oct 2026 · Probed https://bloomerang.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 bloomerang.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://bloomerang.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://bloomerang.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://bloomerang.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://bloomerang.usefulapi.io/mcp |
| Authorisation server | https://bloomerang.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bloomerang.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://bloomerang.usefulapi.io/mcp | HTTPS enforced | 301 | https://bloomerang.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 →
bloomerang_create_constituent Create a constituent ~274
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Record type. |
| website | string | – | – |
No output schema declared.
No examples provided.
bloomerang_create_interaction Log an interaction ~132
WRITE: log an interaction with a constituent — a call, email, meeting, letter, etc. — on their timeline. Bloomerang: POST /interaction.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | How it happened. |
| constituent_id | integer | yes | The API Id of the constituent (not the CRM AccountNumber). |
| date | string | yes | When it happened (YYYY-MM-DD). |
| is_inbound | boolean | – | True if the constituent initiated it. |
| note | string | – | Details. |
| purpose | string | yes | Why it happened. |
| subject | string | yes | Short subject line. |
No output schema declared.
No examples provided.
bloomerang_create_note Add a note ~73
WRITE: add a note to a constituent's record. Bloomerang: POST /note.
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | integer | yes | The API Id of the constituent (not the CRM AccountNumber). |
| date | string | yes | Note date (YYYY-MM-DD). |
| note | string | yes | The note text. |
No output schema declared.
No examples provided.
bloomerang_create_task Create a task ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Short subject line. |
No output schema declared.
No examples provided.
bloomerang_get_constituent Get one constituent ~71
Fetch one constituent's full profile — names, primary and secondary contact details, household, communication preferences, engagement score and custom values. Bloomerang: GET /constituent/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | integer | yes | The API Id of the constituent (not the CRM AccountNumber). |
No output schema declared.
No examples provided.
bloomerang_get_constituent_timeline Get a constituent's timeline ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | integer | yes | 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. |
No output schema declared.
No examples provided.
bloomerang_get_current_user Get the current user ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bloomerang_get_household Get one household ~71
Fetch a household — its names, head of household (HeadId) and member constituent Ids. A constituent's HouseholdId points here. Bloomerang: GET /household/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| household_id | integer | yes | The API Id of the household (not the CRM AccountNumber). |
No output schema declared.
No examples provided.
bloomerang_get_transaction Get one transaction ~68
Fetch one transaction with its payment method, amounts, refund status and every designation (fund, campaign, appeal, tribute, acknowledgement status). Bloomerang: GET /transaction/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| transaction_id | integer | yes | The API Id of the transaction (not the CRM AccountNumber). |
No output schema declared.
No examples provided.
bloomerang_list_appeals List appeals ~151
List appeals — the specific asks (a year-end letter, a gala invitation) that gifts are attributed to. Bloomerang: GET /appeals.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
bloomerang_list_campaigns List campaigns ~160
List fundraising campaigns with their goals and dates. Bloomerang: GET /campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
bloomerang_list_constituent_relationships List a constituent's relationships ~138
Relationships between this constituent and others (spouse, employer, board member ...), with the role on each side. Bloomerang: GET /constituent/{id}/relationships.
| Name | Type | Req | Description |
|---|---|---|---|
| constituent_id | integer | yes | 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. |
No output schema declared.
No examples provided.
bloomerang_list_constituents List constituents ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
bloomerang_list_funds List funds ~134
List the funds gifts can be designated to (e.g. General Operating, Scholarship). Bloomerang: GET /funds.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
bloomerang_list_interactions List interactions ~141
List logged interactions (calls, emails, meetings, letters ...) — filter by constituent, channel or purpose. Bloomerang: GET /interactions.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
bloomerang_list_notes List notes ~106
List notes, optionally for specific constituents. Bloomerang: GET /notes.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
bloomerang_list_tasks List tasks ~201
List tasks (follow-ups) — filter by status, due-date range, assignee user, constituent, channel or purpose. Bloomerang: GET /tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
bloomerang_list_transactions List transactions (gifts) ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
bloomerang_search_constituents Search constituents ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | yes | 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. |
No output schema declared.
No examples provided.
bloomerang_update_constituent Update a constituent ~273
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| birthdate | string | – | Birth date (YYYY-MM-DD). |
| constituent_id | integer | yes | 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 | – | – |
No output schema declared.
No examples provided.
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.