Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Qgiv MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
21
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Qgiv (Bloomerang Fundraising) donations, refunds, recurring gifts, P2P registrations, events.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http qgiv-mcp-by-usefulapi https://qgiv.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# qgiv_list_recent_transactions, qgiv_list_transactions_by_date, qgiv_list_transactions_after_id and 18 more
Qgiv MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http qgiv-mcp-by-usefulapi https://qgiv.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records to return (1-100, default 25). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| begin_date | string | yes | First day (yyyy-mm-dd). |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| after_id | integer | yes | Return transactions with an id greater than this. |
| limit | integer | no | Records to return (1-100, default 25). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transaction_id | integer | yes | Numeric Qgiv id. |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records to return (1-100, default 25). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
Refunds between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/refunds/dates/{begin}:{end}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| begin_date | string | yes | First day (yyyy-mm-dd). |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
One refund in full by id (read-only; this server never issues refunds). POST /reporting/refunds/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| refund_id | integer | yes | Numeric Qgiv id. |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | Only schedules in this state (default: all). |
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
One recurring donation schedule by id (read-only; schedules cannot be changed here). POST /reporting/recurring/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recurring_id | integer | yes | Numeric Qgiv id. |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
The latest statement(s) for the organization or form, with summary totals (per-transaction rows left out). POST /reporting/statements/latest.
No parameter schema on file.
One statement by id with its transaction rows (first 100 shown; donor names only). POST /reporting/statements/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| statement_id | integer | yes | Numeric Qgiv id. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records to return (1-100, default 25). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
Peer-to-peer registrations between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/registrations/dates/{begin}:{end}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| begin_date | string | yes | First day (yyyy-mm-dd). |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
One peer-to-peer registration in full (purchase history, team, totals, child registrations). Contact details only with include_contact. POST /reporting/registrations/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| registration_id | integer | yes | Numeric Qgiv id. |
| include_contact | boolean | no | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_details | boolean | no | Include nested packages, fields and promo codes (large). |
| limit | integer | no | Events to return (1-50, default 20). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
Pledge options configured on the form(s) (title, value, frequency, begin date, iterations, state), not donors' pledge records. POST /pledges/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
One pledge option by id. POST /pledges/{id} (no package is sent, so nothing is changed).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| pledge_id | integer | yes | Numeric Qgiv id. |
Custom (additional-question) fields configured on the form(s): id, reference, title, input type, required flags, display flags. POST /customFields/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
Report mappings (accounting export mappings) on the form(s): id, identifier, mapping data, export service, type. POST /reporting/mappings/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records to return (1-100, default 25). |
| offset | integer | no | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
One report mapping by id. POST /reporting/mappings/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mapping_id | integer | yes | Numeric Qgiv id. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Qgiv MCP by usefulapi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Qgiv MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.