Qgiv MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Qgiv MCP by usefulapi is answering right now. Last checked 14 min ago. It exposes 21 tools. Last commit 1 Nov 2026.

Read Qgiv (Bloomerang Fundraising) donations, refunds, recurring gifts, P2P registrations, events.

Uptime history 21 days of history

21 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

182 ms

Response time

average over 24h

Stars

last commit 1 Nov 2026

What changed 24

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

31 Oct a tool changed version4 times that day

30 Oct a tool changed version2 times that day

29 Oct a tool changed version2 times that day

28 Oct a tool changed version2 times that day

27 Oct a tool changed version

25 Oct a tool changed version4 times that day

24 Oct a tool changed version3 times that day

23 Oct a tool changed version

22 Oct a tool changed version

20 Oct a tool changed version3 times that day

and 14 more, back to 13 October 2026

Nothing serious here today

Today is the operative word: we check Qgiv MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add qgiv --transport http https://qgiv.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://qgiv.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.qgiv]
url = "https://qgiv.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "qgiv": {
      "url": "https://qgiv.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "qgiv": {
      "type": "http",
      "url": "https://qgiv.usefulapi.io/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

qgiv

qgiv_get_latest_statements

The latest statement(s) for the organization or form, with summary totals (per-transaction rows left out). POST /reporting/statements/latest.

qgiv_get_pledge

One pledge option by id. POST /pledges/{id} (no package is sent, so nothing is changed).

qgiv_get_recurring_schedule

One recurring donation schedule by id (read-only; schedules cannot be changed here). POST /reporting/recurring/{id}.

qgiv_get_refund

One refund in full by id (read-only; this server never issues refunds). POST /reporting/refunds/{id}.

qgiv_get_registration

One peer-to-peer registration in full (purchase history, team, totals, child registrations). Contact details only with include_contact. POST /reporting/registrations/{id}.

qgiv_get_report_mapping

One report mapping by id. POST /reporting/mappings/{id}.

qgiv_get_statement

One statement by id with its transaction rows (first 100 shown; donor names only). POST /reporting/statements/{id}.

qgiv_get_transaction

One transaction in full: donation lines, fund/restriction, dedication, custom-field answers, event packages, registrations, refunds. Contact details only with include_contact; card data is reduced to the last four digits. POST /reporting/transactions/{id}.

qgiv_list_custom_fields

Custom (additional-question) fields configured on the form(s): id, reference, title, input type, required flags, display flags. POST /customFields/list.

qgiv_list_events

Events (ticketed/auction events) on the forms the token covers: id, dates and the top-level settings. Set include_details for packages, questions and promo codes. Notification e-mail addresses are never returned. POST /events/list.

qgiv_list_pledges

Pledge options configured on the form(s) (title, value, frequency, begin date, iterations, state), not donors' pledge records. POST /pledges/list.

qgiv_list_recent_refunds

The most recent refunds (read-only): id, original transaction, refund and settle dates, amount, payment type, last four digits, fund. POST /reporting/refunds/last/{limit}.

qgiv_list_recent_registrations

The most recent peer-to-peer (Hobnob) event registrations: id, category, registrant name, team, fundraising goal and amount raised. Contact details only with include_contact. POST /reporting/registrations/last/{limit}.

qgiv_list_recent_transactions

The most recent donations/transactions (newest first as Qgiv returns them): id, status, date, amount, fee, net, donor name and id, form, recurring link, payment type and last four card digits, fund. Donor contact details are left out unless include_contact is set; full card numbers are never returned. POST /reporting/transactions/last/{limit}.

qgiv_list_recurring_schedules

Recurring donation schedules (read-only): id, start/end date, next billing date, frequency, amount, state, donor name and id, plus Qgiv's 12-month forecast. Filter by status active, paused, expired or deleted. Paged with offset/limit. POST /reporting/recurring/list or /reporting/recurring/{status}.

qgiv_list_refunds_by_date

Refunds between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/refunds/dates/{begin}:{end}.

qgiv_list_registrations_by_date

Peer-to-peer registrations between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/registrations/dates/{begin}:{end}.

qgiv_list_report_mappings

Report mappings (accounting export mappings) on the form(s): id, identifier, mapping data, export service, type. POST /reporting/mappings/list.

qgiv_list_statements

Monthly fee/payout statements: id, date, amount contributed, fees, refunded, debited, credited and the summary totals (without the per-transaction rows; use qgiv_get_statement for those). Paged with offset/limit. POST /reporting/statements/list.

qgiv_list_transactions_after_id

Transactions with an id greater than the given one, sorted by id ascending and paged with limit; next_after_id is the cursor for the next call (use it as after_id). Handy for syncing new gifts. POST /reporting/transactions/after/{id}.

qgiv_list_transactions_by_date

Transactions between two dates (inclusive), at most 31 days per call, paged with offset/limit. Same fields as qgiv_list_recent_transactions. Qgiv has no server-side paging, so a busy range is fetched whole and sliced; use a shorter range if it is too large. POST /reporting/transactions/dates/{begin}:{end}.

Endpoints

URL	Transport	State	Latency	Checked
https://qgiv.usefulapi.io/mcp	streamable-http	answering	150 ms	14 min ago

Alternatives to Qgiv MCP by usefulapi

same job, measured the same way

Givecloud MCP by usefulapi

by usefulapi

Read supporters, contributions, recurring donations, fundraising products and feed posts.

10 tools answering

Funraise MCP by usefulapi

by usefulapi

Read Funraise supporters, donations, recurring gifts and forms; add notes, tasks and supporters.

28 tools answering

GivingFuel MCP by usefulapi

by usefulapi

Read GivingFuel forms, donations, transactions, recurring gifts and donors; manage coupons.

15 tools answering

Corsizio MCP by usefulapi

by usefulapi

Read Corsizio events, attendees and registrations, including payment status. Read-only.

6 tools answering

Tito MCP by usefulapi

by usefulapi

Look up events, releases, tickets, registrations and discount codes, and edit tickets and codes.

20 tools answering

Bloomerang MCP by usefulapi

by usefulapi

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

20 tools answering

Glue Up MCP by usefulapi

by usefulapi

Read Glue Up events, memberships, contacts, organizations and finance records.

13 tools answering

Feegow MCP by usefulapi

by usefulapi

Read clinic appointments, patients and finances; manage bookings and patient registration.

26 tools answering

Qgiv MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Qgiv MCP by usefulapi do?

It exposes 21 tools, read directly from the server on our last check. Among them: qgiv_get_latest_statements, qgiv_get_pledge, qgiv_get_recurring_schedule, qgiv_get_refund, qgiv_get_registration, qgiv_get_report_mapping and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Qgiv MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 182 ms. The bar chart above shows every period we have measured.

How do I connect Qgiv MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Qgiv MCP by usefulapi need an API key?

No. Qgiv MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Qgiv MCP by usefulapi?

It answers our handshake in 182 ms on average, which is faster than 76% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Qgiv MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at qgiv.usefulapi.io, which runs on its operator's own terms.