Qgiv MCP by usefulapi
REMOTE · QGIV.USEFULAPI.IO
Read Qgiv (Bloomerang Fundraising) donations, refunds, recurring gifts, P2P registrations, events.
Available components
Last scanned (22 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Finance and Payments
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2365 tokens (~112/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "qgiv_list_refunds_by_date" implies "refund" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 12 Oct 26 60
First indexed and scored.
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 16 Oct 2026 · Probed https://qgiv.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 qgiv.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://qgiv.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://qgiv.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://qgiv.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://qgiv.usefulapi.io/mcp |
| Authorisation server | https://qgiv.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qgiv.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/qgiv/ |
| http (plaintext) | http://qgiv.usefulapi.io/mcp | Inconclusive | 302 | http://qgiv.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 →
qgiv_get_latest_statements Get latest statements ~42
The latest statement(s) for the organization or form, with summary totals (per-transaction rows left out). POST /reporting/statements/latest.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
qgiv_get_pledge Get pledge option ~48
One pledge option by id. POST /pledges/{id} (no package is sent, so nothing is changed).
| Name | Type | Req | Description |
|---|---|---|---|
| pledge_id | integer | yes | Numeric Qgiv id. |
No output schema declared.
No examples provided.
qgiv_get_recurring_schedule Get recurring gift schedule ~80
One recurring donation schedule by id (read-only; schedules cannot be changed here). POST /reporting/recurring/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| recurring_id | integer | yes | Numeric Qgiv id. |
No output schema declared.
No examples provided.
qgiv_get_refund Get refund ~78
One refund in full by id (read-only; this server never issues refunds). POST /reporting/refunds/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| refund_id | integer | yes | Numeric Qgiv id. |
No output schema declared.
No examples provided.
qgiv_get_registration Get P2P registration ~87
One peer-to-peer registration in full (purchase history, team, totals, child registrations). Contact details only with include_contact. POST /reporting/registrations/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| registration_id | integer | yes | Numeric Qgiv id. |
No output schema declared.
No examples provided.
qgiv_get_report_mapping Get report mapping ~38
One report mapping by id. POST /reporting/mappings/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| mapping_id | integer | yes | Numeric Qgiv id. |
No output schema declared.
No examples provided.
qgiv_get_statement Get statement ~49
One statement by id with its transaction rows (first 100 shown; donor names only). POST /reporting/statements/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| statement_id | integer | yes | Numeric Qgiv id. |
No output schema declared.
No examples provided.
qgiv_get_transaction Get transaction ~104
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| transaction_id | integer | yes | Numeric Qgiv id. |
No output schema declared.
No examples provided.
qgiv_list_custom_fields List custom fields ~87
Custom (additional-question) fields configured on the form(s): id, reference, title, input type, required flags, display flags. POST /customFields/list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
qgiv_list_events List events ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_details | boolean | – | Include nested packages, fields and promo codes (large). |
| limit | integer | – | Events to return (1-50, default 20). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
qgiv_list_pledges List pledge options ~90
Pledge options configured on the form(s) (title, value, frequency, begin date, iterations, state), not donors' pledge records. POST /pledges/list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
qgiv_list_recent_refunds List recent refunds ~100
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
No output schema declared.
No examples provided.
qgiv_list_recent_registrations List recent P2P registrations ~111
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
No output schema declared.
No examples provided.
qgiv_list_recent_transactions List recent transactions ~138
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
No output schema declared.
No examples provided.
qgiv_list_recurring_schedules List recurring gift schedules ~176
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
| status | string | – | Only schedules in this state (default: all). |
No output schema declared.
No examples provided.
qgiv_list_refunds_by_date List refunds by date range ~150
Refunds between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/refunds/dates/{begin}:{end}.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_date | string | yes | First day (yyyy-mm-dd). |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
qgiv_list_registrations_by_date List P2P registrations by date range ~154
Peer-to-peer registrations between two dates (inclusive), at most 31 days per call, paged with offset/limit. POST /reporting/registrations/dates/{begin}:{end}.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_date | string | yes | First day (yyyy-mm-dd). |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
qgiv_list_report_mappings List report mappings ~88
Report mappings (accounting export mappings) on the form(s): id, identifier, mapping data, export service, type. POST /reporting/mappings/list.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
qgiv_list_statements List statements ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
qgiv_list_transactions_after_id List transactions after an id ~130
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| after_id | integer | yes | Return transactions with an id greater than this. |
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
No output schema declared.
No examples provided.
qgiv_list_transactions_by_date List transactions by date range ~185
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| begin_date | string | yes | First day (yyyy-mm-dd). |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| include_contact | boolean | – | Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only. |
| limit | integer | – | Records to return (1-100, default 25). |
| offset | integer | – | Records to skip, for paging through a larger result (use next_offset from the previous reply). |
No output schema declared.
No examples provided.
How do I install the Qgiv MCP by usefulapi server?
Qgiv MCP by usefulapi is a hosted endpoint at https://qgiv.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 · qgiv.usefulapi.io
claude mcp add --transport http io-usefulapi-qgiv 'https://qgiv.usefulapi.io/mcp'
What is the Qgiv MCP by usefulapi server?
Qgiv MCP by usefulapi is listed in the public MCP registry as io.usefulapi/qgiv. Read Qgiv (Bloomerang Fundraising) donations, refunds, recurring gifts, P2P registrations, events. This page covers its hosted endpoint (https://qgiv.usefulapi.io/mcp).
Is the Qgiv MCP by usefulapi server safe to use?
Qgiv MCP by usefulapi scores 63 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 Qgiv MCP by usefulapi server expose?
Qgiv MCP by usefulapi exposes 21 tools: qgiv_list_recent_transactions, qgiv_list_transactions_by_date, qgiv_list_transactions_after_id, qgiv_get_transaction, qgiv_list_recent_refunds, and 16 more. Their descriptions and schemas cost roughly 2,164 tokens of context every time the server is loaded.
Does the Qgiv MCP by usefulapi server require authentication?
Yes. Qgiv MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Qgiv MCP by usefulapi server still maintained?
Qgiv MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.