Raisely MCP by usefulapi
REMOTE · RAISELY.USEFULAPI.IO
Read campaigns, donations, profiles and supporters; record offline donations and upsert users.
Available components
Last scanned (29 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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
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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: 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.
- 2 Nov 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “compare_our_fundraising_campaigns” functional
- New prompt “list_recent_donations_for_a_campaign” functional
- New prompt “look_up_or_add_a_supporter” functional
- New prompt “record_an_offline_donation” functional
- New prompt “review_recurring_donations” functional
- New prompt “show_the_giving_history_of_a_donor” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.32.0 → 1.34.0 functional
- Server version: 1.31.0 → 1.32.0 functional
- Server version: 1.30.2 → 1.31.0 functional
- 30 Oct 26 0
- Server version: 1.30.1 → 1.30.2 functional
- Server version: 1.30.0 → 1.30.1 functional
- 29 Oct 26 +1
- Server version: 1.29.0 → 1.30.0 functional
- Server version: 1.28.0 → 1.29.0 functional
- 28 Oct 26 0
- Server version: 1.26.0 → 1.28.0 functional
- 27 Oct 26 0
- Server version: 1.25.0 → 1.26.0 functional
- 25 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.3 → 1.23.0 functional
- Server version: 1.22.0 → 1.22.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.21.0 → 1.22.0 functional
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.18.0 → 1.20.0 functional
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 Nov 2026 · Probed https://raisely.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 raisely.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://raisely.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/raisely/ |
| http (plaintext) | http://raisely.usefulapi.io/mcp | Inconclusive | 302 | http://raisely.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 →
raisely_create_donation Record a donation ~343
MUTATES Raisely data: records a donation (use for OFFLINE/manual donations — e.g. cash or cheque). Raisely API: POST /donations with the body wrapped as { data: {...} }. Required by the API: amount (integer, in cents/smallest currency unit), currency (3-letter code), email (donor), type (ONLINE or OFFLINE), method (payment gateway, e.g. OFFLINE). Link it to a campaign/profile via campaignUuid/profileUuid. Everything else (firstName, lastName, message, date, items, public, private, ...) goes through `fields`. Returns the created donation.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Total donation amount in the smallest currency unit (e.g. cents). Required. |
| campaignUuid | string | – | Uuid of the campaign the donation belongs to. |
| currency | string | yes | 3-letter currency code, e.g. AUD, USD, GBP. Required. |
| string | yes | Email address of the donor. Required. | |
| fields | object | – | Additional documented Raisely fields to send in the JSON write body's `data` object — merged OVER the typed fields above. |
| firstName | string | – | Donor first name. |
| lastName | string | – | Donor last name. |
| method | string | – | The payment gateway/method, e.g. "OFFLINE", "CREDIT". Required by the API. |
| profileUuid | string | – | Uuid of the fundraising profile the donation is credited to. |
| type | string | – | ONLINE or OFFLINE (default OFFLINE — this tool is for manual/offline donations). |
No output schema declared.
No examples provided.
raisely_create_post Create a post ~188
MUTATES Raisely data: publishes a post (a campaign/profile update). Raisely API: POST /posts with the body wrapped as { data: {...} }. Required by the API: path (the post's URL slug), body (the content), photoUrl. Link it to a profile via profileUuid (pass through `fields`). Extra fields (title, date, ...) via `fields`. Returns the created post.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | The post content/body. Required by the API. |
| fields | object | – | Additional documented Raisely fields to send in the JSON write body's `data` object — merged OVER the typed fields above. |
| path | string | yes | The post's URL slug/path. Required by the API. |
| photoUrl | string | – | URL of the post's photo. Required by the API. |
| title | string | – | The post title. |
No output schema declared.
No examples provided.
raisely_get_authenticated_user Get authenticated user ~52
Verify credentials and show the currently authenticated user plus their privileges. Raisely API: GET /authenticate. Use this first to confirm RAISELY_API_KEY works. Returns { data:{...} }.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
raisely_get_campaign Get a campaign ~55
Fetch a single campaign by id or path/slug. Raisely API: GET /campaigns/{campaign}. Returns { data:{...} }.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | yes | The campaign uuid or URL path/slug. |
No output schema declared.
No examples provided.
raisely_get_donation Get a donation ~47
Fetch a single donation by uuid. Raisely API: GET /donations/{uuid}. Returns { data:{...} }.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The donation uuid. |
No output schema declared.
No examples provided.
raisely_get_profile Get a fundraising profile ~64
Fetch a single fundraising profile by path (a URL slug OR the uuid — a string either way). Raisely API: GET /profiles/{path}. Returns { data:{...} }.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The profile path (URL slug) or uuid. |
No output schema declared.
No examples provided.
raisely_get_subscription Get a subscription ~50
Fetch a single subscription (recurring donation) by uuid. Raisely API: GET /subscriptions/{uuid}. Returns { data:{...} }.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The subscription uuid. |
No output schema declared.
No examples provided.
raisely_get_user Get a user ~51
Fetch a single user (donor/supporter) by uuid. Raisely API: GET /users/{uuid}. Returns { data:{...} }.
| Name | Type | Req | Description |
|---|---|---|---|
| uuid | string | yes | The user uuid. |
No output schema declared.
No examples provided.
raisely_list_campaign_donations List a campaign's donations ~142
Convenience: list donations for a specific campaign. Raisely API: GET /campaigns/{campaign}/donations. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | yes | The campaign uuid or URL path/slug. |
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_campaign_profiles List a campaign's profiles ~140
Convenience: list fundraising profiles for a specific campaign. Raisely API: GET /campaigns/{campaign}/profiles. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | yes | The campaign uuid or URL path/slug. |
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_campaigns List campaigns ~118
List fundraising campaigns. Raisely API: GET /campaigns. Returns the list envelope { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_donations List donations ~132
List donations. Raisely API: GET /donations. Filter via `params` (e.g. campaign, status, sort, order). Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_orders List orders ~121
List orders (ticket/product purchases). Raisely API: GET /orders. Filter via `params`. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_posts List posts ~121
List posts (campaign/profile updates). Raisely API: GET /posts. Filter via `params`. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_profiles List fundraising profiles ~135
List fundraising profiles (individual/team fundraising pages). Raisely API: GET /profiles. Filter via `params` (e.g. campaign, type, sort, order). Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_segments List segments ~114
List saved audience segments. Raisely API: GET /segments. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_subscriptions List subscriptions ~122
List subscriptions (recurring donations). Raisely API: GET /subscriptions. Filter via `params`. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_tags List tags ~116
List tags used to label records. Raisely API: GET /tags. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_list_user_donations List a user's donations ~135
Convenience: a donor's giving history. Raisely API: GET /users/{uuid}/donations. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
| uuid | string | yes | The user uuid. |
No output schema declared.
No examples provided.
raisely_list_users List users ~125
List users (donors/supporters/fundraisers). Raisely API: GET /users. Filter via `params`. Returns { data:[...], pagination }.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max records to return (Raisely `limit`, default 20). |
| offset | integer | – | Records to skip for pagination (Raisely `offset`, default 0). |
| params | object | – | Additional documented query-string filters to send verbatim (e.g. campaign, status, sort, order, private) — merged with the typed limit/offset above. |
No output schema declared.
No examples provided.
raisely_request Raw read request ~107
Power-user escape hatch: GET any Raisely API path not wrapped by a dedicated tool. READ-ONLY — only GET is allowed. Pass the FULL API path after the base, starting with a slash, INCLUDING any query string, e.g. "/subscriptions/{uuid}/donations" or "/donations?limit=50". Returns the parsed JSON.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Full API path after the base, starting with "/", e.g. "/donations?limit=50". |
No output schema declared.
No examples provided.
raisely_update_profile Update a fundraising profile ~203
MUTATES Raisely data: updates a fundraising profile's goal/name/story. Raisely API: PATCH /profiles/{path} with the body wrapped as { data: {...} } (only included fields change). Use `fields` for goal, name, description/story, public, private, and any other documented field. Set overwriteCustomFields:true to overwrite (rather than preserve) unspecified custom fields. The path is never sent in the body.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | object | – | Additional documented Raisely fields to send in the JSON write body's `data` object — merged OVER the typed fields above. |
| goal | number | – | New fundraising goal (in the smallest currency unit). |
| name | string | – | New profile name. |
| overwriteCustomFields | boolean | – | When true, overwrite (instead of preserve) custom fields not included in this update. |
| path | string | yes | The profile path (URL slug) or uuid to update (path only; required). |
No output schema declared.
No examples provided.
raisely_upsert_user Upsert a user ~169
MUTATES Raisely data: creates OR updates a supporter/donor, matched by email (safer than a plain create — no duplicates). Raisely API: POST /users/upsert with the body wrapped as { data: {...} }. Typed: email (the match key), firstName, lastName; everything else (phoneNumber, address, public, private, ...) via `fields`. Returns the upserted user.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's email address — the match key for upsert. Required. | |
| fields | object | – | Additional documented Raisely fields to send in the JSON write body's `data` object — merged OVER the typed fields above. |
| firstName | string | – | User first name. |
| lastName | string | – | User last name. |
No output schema declared.
No examples provided.
How do I install the Raisely MCP by usefulapi server?
Raisely MCP by usefulapi is a hosted endpoint at https://raisely.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 · raisely.usefulapi.io
claude mcp add --transport http io-usefulapi-raisely 'https://raisely.usefulapi.io/mcp'
What is the Raisely MCP by usefulapi server?
Raisely MCP by usefulapi is listed in the public MCP registry as io.usefulapi/raisely. Read campaigns, donations, profiles and supporters; record offline donations and upsert users. This page covers its hosted endpoint (https://raisely.usefulapi.io/mcp).
Is the Raisely MCP by usefulapi server safe to use?
Raisely MCP by usefulapi scores 18 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 Raisely MCP by usefulapi server expose?
Raisely MCP by usefulapi exposes 23 tools: raisely_get_authenticated_user, raisely_list_campaigns, raisely_get_campaign, raisely_list_profiles, raisely_get_profile, and 18 more. Their descriptions and schemas cost roughly 2,850 tokens of context every time the server is loaded.
Does the Raisely MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Raisely MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Raisely MCP by usefulapi server still maintained?
Raisely MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.