Raisely MCP by usefulapi
io.usefulapi/raiselyusefulapi.iostreamable-httpv1.41.4Scanned
Read campaigns, donations, profiles and supporters; record offline donations and upsert users.
23 tools: 4 can delete or cancel things, 1 change things and 18 only read.
- Reads private data · 1
- Reads text others write · 3
- Can send data out · 1
- 2 findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Raisely MCP by usefulapi can do
The Raisely MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 23 tools. It can delete or cancel things (4 tools: raisely_create_donation, raisely_upsert_user, raisely_update_profile and raisely_create_post) and create or change data (1 tool: raisely_request). 18 tools only read.
1 tool reads private data (raisely_get_authenticated_user); 3 tools bring in text other people can write (raisely_get_profile, raisely_list_posts and raisely_list_orders); 1 tool can send data out of your system (raisely_create_post). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its tools changed once since Anlyon Radar first saw them.
Last scanned Oct 25, 2026, version 1.41.4.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
23 tools
Deletes or cancels 4Claude Code: deny
raisely_create_donationMUTATES Raisely data: records a donation (use for OFFLINE/manual donations — e.g.No findings
Why it is in this group
- The name "raisely_create_donation" says "create": a word for a change.
- The input carries an amount (input.amount) and a currency, so it moves money.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Record a donation
- destructiveHint: true
raisely_create_postMUTATES Raisely data: publishes a post (a campaign/profile update).Can send data outNo findings
Why it is in this group
- The name "raisely_create_post" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "raisely_create_post" says "create" and "post": it writes something other people read.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a post
- destructiveHint: true
raisely_update_profileMUTATES Raisely data: updates a fundraising profile's goal/name/story.No findings
Why it is in this group
- The name "raisely_update_profile" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Update a fundraising profile
- destructiveHint: true
raisely_upsert_userMUTATES Raisely data: creates OR updates a supporter/donor, matched by email (safer than a plain create — no duplicates).No findings
Why it is in this group
- The name "raisely_upsert_user" says "upsert": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Upsert a user
- destructiveHint: true
Changes things 1Claude Code: ask
raisely_requestPower-user escape hatch: GET any Raisely API path not wrapped by a dedicated tool.1 finding
Why it is in this group
- The name "raisely_request" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "raisely_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "raisely_request" says "request": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Raw read request
- readOnlyHint: true
Only reads 18Show 18 read-only tools
raisely_get_authenticated_userVerify credentials and show the currently authenticated user plus their privileges.Reads private data1 finding
Why it is in this group
- The name "raisely_get_authenticated_user" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "credential": it reads secrets.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Verify credentials and show the currently authenticated us..."
Description, as the server wrote it 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:{...} }.
Annotations the server declares
- title: Get authenticated user
- readOnlyHint: true
raisely_get_campaignFetch a single campaign by id or path/slug.No findings
Why it is in this group
- The name "raisely_get_campaign" says "get": a word for reading.
Description, as the server wrote it Fetch a single campaign by id or path/slug. Raisely API: GET /campaigns/{campaign}. Returns { data:{...} }.
Annotations the server declares
- title: Get a campaign
- readOnlyHint: true
raisely_get_donationFetch a single donation by uuid.No findings
Why it is in this group
- The name "raisely_get_donation" says "get": a word for reading.
Description, as the server wrote it Fetch a single donation by uuid. Raisely API: GET /donations/{uuid}. Returns { data:{...} }.
Annotations the server declares
- title: Get a donation
- readOnlyHint: true
raisely_get_profileFetch a single fundraising profile by path (a URL slug OR the uuid — a string either way).Reads text others writeNo findings
Why it is in this group
- The name "raisely_get_profile" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Fetch a single fundraising profile by path (a URL slug OR the uuid — a string either way). Raisely API: GET /profiles/{path}. Returns { data:{...} }.
Annotations the server declares
- title: Get a fundraising profile
- readOnlyHint: true
raisely_get_subscriptionFetch a single subscription (recurring donation) by uuid.No findings
Why it is in this group
- The name "raisely_get_subscription" says "get": a word for reading.
Description, as the server wrote it Fetch a single subscription (recurring donation) by uuid. Raisely API: GET /subscriptions/{uuid}. Returns { data:{...} }.
Annotations the server declares
- title: Get a subscription
- readOnlyHint: true
raisely_get_userFetch a single user (donor/supporter) by uuid.No findings
Why it is in this group
- The name "raisely_get_user" says "get": a word for reading.
Description, as the server wrote it Fetch a single user (donor/supporter) by uuid. Raisely API: GET /users/{uuid}. Returns { data:{...} }.
Annotations the server declares
- title: Get a user
- readOnlyHint: true
raisely_list_campaign_donationsConvenience: list donations for a specific campaign.No findings
Why it is in this group
- The name "raisely_list_campaign_donations" says "list": a word for reading.
Description, as the server wrote it Convenience: list donations for a specific campaign. Raisely API: GET /campaigns/{campaign}/donations. Returns { data:[...], pagination }.
Annotations the server declares
- title: List a campaign's donations
- readOnlyHint: true
raisely_list_campaign_profilesConvenience: list fundraising profiles for a specific campaign.No findings
Why it is in this group
- The name "raisely_list_campaign_profiles" says "list": a word for reading.
Description, as the server wrote it Convenience: list fundraising profiles for a specific campaign. Raisely API: GET /campaigns/{campaign}/profiles. Returns { data:[...], pagination }.
Annotations the server declares
- title: List a campaign's profiles
- readOnlyHint: true
raisely_list_campaignsList fundraising campaigns.No findings
Why it is in this group
- The name "raisely_list_campaigns" says "list": a word for reading.
Description, as the server wrote it List fundraising campaigns. Raisely API: GET /campaigns. Returns the list envelope { data:[...], pagination }.
Annotations the server declares
- title: List campaigns
- readOnlyHint: true
raisely_list_donationsList donations.No findings
Why it is in this group
- The name "raisely_list_donations" says "list": a word for reading.
Description, as the server wrote it List donations. Raisely API: GET /donations. Filter via `params` (e.g. campaign, status, sort, order). Returns { data:[...], pagination }.
Annotations the server declares
- title: List donations
- readOnlyHint: true
raisely_list_ordersList orders (ticket/product purchases).Reads text others writeNo findings
Why it is in this group
- The name "raisely_list_orders" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
Description, as the server wrote it List orders (ticket/product purchases). Raisely API: GET /orders. Filter via `params`. Returns { data:[...], pagination }.
Annotations the server declares
- title: List orders
- readOnlyHint: true
raisely_list_postsList posts (campaign/profile updates).Reads text others writeNo findings
Why it is in this group
- The name "raisely_list_posts" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "raisely_list_posts" says "list" and "post": it reads posts, which other people can write.
- untrusted-inputThe description's first sentence says "list" and "post": it reads posts, which other people can write.
Description, as the server wrote it List posts (campaign/profile updates). Raisely API: GET /posts. Filter via `params`. Returns { data:[...], pagination }.
Annotations the server declares
- title: List posts
- readOnlyHint: true
raisely_list_profilesList fundraising profiles (individual/team fundraising pages).No findings
Why it is in this group
- The name "raisely_list_profiles" says "list": a word for reading.
Description, as the server wrote it List fundraising profiles (individual/team fundraising pages). Raisely API: GET /profiles. Filter via `params` (e.g. campaign, type, sort, order). Returns { data:[...], pagination }.
Annotations the server declares
- title: List fundraising profiles
- readOnlyHint: true
raisely_list_segmentsList saved audience segments.No findings
Why it is in this group
- The name "raisely_list_segments" says "list": a word for reading.
Description, as the server wrote it List saved audience segments. Raisely API: GET /segments. Returns { data:[...], pagination }.
Annotations the server declares
- title: List segments
- readOnlyHint: true
raisely_list_subscriptionsList subscriptions (recurring donations).No findings
Why it is in this group
- The name "raisely_list_subscriptions" says "list": a word for reading.
Description, as the server wrote it List subscriptions (recurring donations). Raisely API: GET /subscriptions. Filter via `params`. Returns { data:[...], pagination }.
Annotations the server declares
- title: List subscriptions
- readOnlyHint: true
raisely_list_tagsList tags used to label records.No findings
Why it is in this group
- The name "raisely_list_tags" says "list": a word for reading.
Description, as the server wrote it List tags used to label records. Raisely API: GET /tags. Returns { data:[...], pagination }.
Annotations the server declares
- title: List tags
- readOnlyHint: true
raisely_list_user_donationsConvenience: a donor's giving history.No findings
Why it is in this group
- The name "raisely_list_user_donations" says "list": a word for reading.
Description, as the server wrote it Convenience: a donor's giving history. Raisely API: GET /users/{uuid}/donations. Returns { data:[...], pagination }.
Annotations the server declares
- title: List a user's donations
- readOnlyHint: true
raisely_list_usersList users (donors/supporters/fundraisers).No findings
Why it is in this group
- The name "raisely_list_users" says "list": a word for reading.
Description, as the server wrote it List users (donors/supporters/fundraisers). Raisely API: GET /users. Filter via `params`. Returns { data:[...], pagination }.
Annotations the server declares
- title: List users
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__raisely__raisely_create_post"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://raisely.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://raisely.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
- Warnraisely_request
The server marks "raisely_request" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "raisely_request" says "request": a word for a change.
The description mentions "credentials".
What this check looks forMatched text
description: "Verify credentials and show the currently authenticated us..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://raisely.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://raisely.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Tools22 added, 22 removed.+22 added−22 removedView diff
- Added:raisely_create_donationDeletes or cancels
- Added:raisely_create_postDeletes or cancels
- Added:raisely_get_authenticated_userOnly reads
- Added:raisely_get_campaignOnly reads
- Added:raisely_get_donationOnly reads
- Added:raisely_get_profileOnly reads
- Added:raisely_get_subscriptionOnly reads
- Added:raisely_get_userOnly reads
- Added:raisely_list_campaign_donationsOnly reads
- Added:raisely_list_campaign_profilesOnly reads
- Added:raisely_list_campaignsOnly reads
- Added:raisely_list_donationsOnly reads
- Added:raisely_list_ordersOnly reads
- Added:raisely_list_postsOnly reads
- Added:raisely_list_profilesOnly reads
- Added:raisely_list_segmentsOnly reads
- Added:raisely_list_subscriptionsOnly reads
- Added:raisely_list_tagsOnly reads
- Added:raisely_list_user_donationsOnly reads
- Added:raisely_list_usersOnly reads
- Added:raisely_update_profileDeletes or cancels
- Added:raisely_upsert_userDeletes or cancels
- Removed:create_donation
- Removed:create_post
- Removed:get_authenticated_user
- Removed:get_campaign
- Removed:get_donation
- Removed:get_profile
- Removed:get_subscription
- Removed:get_user
- Removed:list_campaign_donations
- Removed:list_campaign_profiles
- Removed:list_campaigns
- Removed:list_donations
- Removed:list_orders
- Removed:list_posts
- Removed:list_profiles
- Removed:list_segments
- Removed:list_subscriptions
- Removed:list_tags
- Removed:list_user_donations
- Removed:list_users
- Removed:update_profile
- Removed:upsert_user
Install
Pinned to version 1.41.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http raisely https://raisely.usefulapi.io/mcpclaude mcp add --transport http raisely https://raisely.usefulapi.io/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__raisely__raisely_get_authenticated_user",
"mcp__raisely__raisely_list_campaigns",
"mcp__raisely__raisely_get_campaign",
"mcp__raisely__raisely_list_profiles",
"mcp__raisely__raisely_get_profile",
"mcp__raisely__raisely_list_donations",
"mcp__raisely__raisely_get_donation",
"mcp__raisely__raisely_list_users",
"mcp__raisely__raisely_get_user",
"mcp__raisely__raisely_list_subscriptions",
"mcp__raisely__raisely_get_subscription",
"mcp__raisely__raisely_list_posts",
"mcp__raisely__raisely_list_orders",
"mcp__raisely__raisely_list_segments",
"mcp__raisely__raisely_list_tags",
"mcp__raisely__raisely_list_campaign_donations",
"mcp__raisely__raisely_list_campaign_profiles",
"mcp__raisely__raisely_list_user_donations"
],
"ask": [
"mcp__raisely__raisely_request"
],
"deny": [
"mcp__raisely__raisely_create_donation",
"mcp__raisely__raisely_upsert_user",
"mcp__raisely__raisely_update_profile",
"mcp__raisely__raisely_create_post"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as raisely. Review it before you use it.
Capability tags behind 5 rules
- mcp__raisely__raisely_get_authenticated_user private-data
- mcp__raisely__raisely_get_profile untrusted-input
- mcp__raisely__raisely_list_posts untrusted-input
- mcp__raisely__raisely_list_orders untrusted-input
- mcp__raisely__raisely_create_post outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/raisely/verify?hash=a49f556e16d8fa23b06692147f727e45d6f857f532332363d4a4dc80eb3b8eec" | jq -e '.changed == false'Pinned hash a49f556e16d8, from Oct 25, 2026, 23:19 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/raisely/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/raisely)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Raisely MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Raisely MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 23 tools, 5 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Raisely MCP by usefulapi delete data?
- Yes. 4 tools can delete, cancel or revoke something: raisely_create_donation, raisely_upsert_user, raisely_update_profile and raisely_create_post.
Can the Raisely MCP by usefulapi do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Raisely MCP by usefulapi have?
- 23 tools: 4 destructive, 1 write, 18 read. raisely_create_donation, raisely_upsert_user, raisely_update_profile, raisely_create_post, raisely_request, raisely_get_authenticated_user, raisely_list_campaigns, raisely_get_campaign and 15 more.
Does the Raisely MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Raisely MCP by usefulapi send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): raisely_create_post.
Has the Raisely MCP by usefulapi changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 23, 2026. Every change is on this page and in its Atom feed.