Marketing, email and messaging
raisely
raisely was answering at the last check. Checked on 2026-10-04 (daily check).
Read campaigns, donations, profiles and supporters; record offline donations and upsert users.
Agents use servers like this to send email, messages and campaigns.
19 read-only0 change data4 high risk
https://raisely.usefulapi.io/mcp
Follow (RSS): status changes, tool-list changes, new advisories and owner verification, in any feed reader.
Tools
23 tools: 19 read-only, 0 change data, 4 high risk (delete, pay, send or run code).
1 tool can send messages; they are listed first.
- read-only
- Only reads or looks things up. Safe for an agent to call on its own.
- changes data
- Creates, edits or sends something. Worth a person's approval the first time.
- high risk
- Can delete, pay, send on your behalf or run code. Hard or impossible to undo.
Connecting costs an agent about 5,042 tokens of tool definitions and a 345 ms handshake.
- high risk
create_postsends messagesMUTATES 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, ... - high risk
create_donationMUTATES 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 o... - high risk
upsert_userMUTATES 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, pri... - high risk
update_profileMUTATES 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 overwriteCustomFi... - read-only
get_authenticated_userVerify 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:{...} }. - read-only
list_campaignsList fundraising campaigns. Raisely API: GET /campaigns. Returns the list envelope { data:[...], pagination }. - read-only
get_campaignFetch a single campaign by id or path/slug. Raisely API: GET /campaigns/{campaign}. Returns { data:{...} }. - read-only
list_profilesList fundraising profiles (individual/team fundraising pages). Raisely API: GET /profiles. Filter via `params` (e.g. campaign, type, sort, order). Returns { data:[...], pagination }. - read-only
get_profileFetch a single fundraising profile by path (a URL slug OR the uuid - a string either way). Raisely API: GET /profiles/{path}. Returns { data:{...} }. - read-only
list_donationsList donations. Raisely API: GET /donations. Filter via `params` (e.g. campaign, status, sort, order). Returns { data:[...], pagination }. - read-only
get_donationFetch a single donation by uuid. Raisely API: GET /donations/{uuid}. Returns { data:{...} }. - read-only
list_usersList users (donors/supporters/fundraisers). Raisely API: GET /users. Filter via `params`. Returns { data:[...], pagination }. - read-only
get_userFetch a single user (donor/supporter) by uuid. Raisely API: GET /users/{uuid}. Returns { data:{...} }. - read-only
list_subscriptionsList subscriptions (recurring donations). Raisely API: GET /subscriptions. Filter via `params`. Returns { data:[...], pagination }. - read-only
get_subscriptionFetch a single subscription (recurring donation) by uuid. Raisely API: GET /subscriptions/{uuid}. Returns { data:{...} }. - read-only
list_postsList posts (campaign/profile updates). Raisely API: GET /posts. Filter via `params`. Returns { data:[...], pagination }. - read-only
list_ordersList orders (ticket/product purchases). Raisely API: GET /orders. Filter via `params`. Returns { data:[...], pagination }. - read-only
list_segmentsList saved audience segments. Raisely API: GET /segments. Returns { data:[...], pagination }. - read-only
list_tagsList tags used to label records. Raisely API: GET /tags. Returns { data:[...], pagination }. - read-only
list_campaign_donationsConvenience: list donations for a specific campaign. Raisely API: GET /campaigns/{campaign}/donations. Returns { data:[...], pagination }. - read-only
list_campaign_profilesConvenience: list fundraising profiles for a specific campaign. Raisely API: GET /campaigns/{campaign}/profiles. Returns { data:[...], pagination }. - read-only
list_user_donationsConvenience: a donor's giving history. Raisely API: GET /users/{uuid}/donations. Returns { data:[...], pagination }. - read-only
raisely_requestPower-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.
Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.
Status
Newest check: answered with tools, from the daily check, 2026-10-04, 345 ms.
From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.
Last 30 days
2026-09-052026-10-04
answered with toolssign-in or payment askednot answeringnot checked
Compare: the most reliable servers in Marketing, email and messaging, ranked by days answering.
Trust and supply chain
No owner has verified this server yet.
No tool change since tracking began on 2026-10-04.
What agents looked for
This week agents asked 7Maps for marketing, email and messaging servers 1 time; this server was shown 0 times and picked 0 times.
Owners see the keywords, the servers picked instead, failure reasons and a comparison with similar servers in Owner Insights.
Badge
Live: status, days reachable, the tokens its tool list costs an agent. For a README:
[](https://7it.co.il/7maps/s/raisely.usefulapi.io/mcp)
Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).
Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=raisely.usefulapi.io%2Fmcp (add the same &style= for another style).
Own this server? Verify that it is yours.
Status widget
A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.
Script (renders where it is placed, in its own shadow DOM):
<script src="https://7it.co.il/7maps/widget/raisely.usefulapi.io/mcp.js" async></script>
Or an iframe:
<iframe src="https://7it.co.il/7maps/widget/raisely.usefulapi.io/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>
The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=raisely.usefulapi.io%2Fmcp.
Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.
For AI agents
Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.
7Maps by 7IT maps the MCP servers AI agents use, from public listings. Observations with a date, not a judgement. Methodology · How we collect, and opting out.