# Qgiv MCP by usefulapi (remote · qgiv.usefulapi.io)

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

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- remote · `qgiv.usefulapi.io`: 63/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-qgiv/qgiv.md), [page](https://verifymcp.io/servers/io-usefulapi-qgiv/qgiv)

## Channel facts

- Endpoint: `https://qgiv.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-qgiv": {
      "type": "remote",
      "url": "https://qgiv.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-qgiv --url 'https://qgiv.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-qgiv:
    url: "https://qgiv.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-qgiv": {
      "Transport": "http",
      "Url": "https://qgiv.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-qgiv -t streamable-http -u 'https://qgiv.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-qgiv": {
      "type": "http",
      "url": "https://qgiv.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 63, +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.

### 2026-10-13 (score 62, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] 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

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (21)

### `qgiv_list_recent_transactions` (~138 tokens)

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}.

Input parameters:

- `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).

### `qgiv_list_transactions_by_date` (~185 tokens)

List transactions by date range

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}.

Input parameters:

- `begin_date` (string, required): First day (yyyy-mm-dd).
- `end_date` (string, required): 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).

### `qgiv_list_transactions_after_id` (~130 tokens)

List transactions after an 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}.

Input parameters:

- `after_id` (integer, required): 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).

### `qgiv_get_transaction` (~104 tokens)

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}.

Input parameters:

- `include_contact` (boolean): Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only.
- `transaction_id` (integer, required): Numeric Qgiv id.

### `qgiv_list_recent_refunds` (~100 tokens)

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}.

Input parameters:

- `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).

### `qgiv_list_refunds_by_date` (~150 tokens)

List refunds by date range

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

Input parameters:

- `begin_date` (string, required): First day (yyyy-mm-dd).
- `end_date` (string, required): 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).

### `qgiv_get_refund` (~78 tokens)

Get refund

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

Input parameters:

- `include_contact` (boolean): Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only.
- `refund_id` (integer, required): Numeric Qgiv id.

### `qgiv_list_recurring_schedules` (~176 tokens)

List recurring gift 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}.

Input parameters:

- `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).

### `qgiv_get_recurring_schedule` (~80 tokens)

Get recurring gift schedule

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

Input parameters:

- `include_contact` (boolean): Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only.
- `recurring_id` (integer, required): Numeric Qgiv id.

### `qgiv_list_statements` (~110 tokens)

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.

Input parameters:

- `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).

### `qgiv_get_latest_statements` (~42 tokens)

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_statement` (~49 tokens)

Get statement

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

Input parameters:

- `statement_id` (integer, required): Numeric Qgiv id.

### `qgiv_list_recent_registrations` (~111 tokens)

List recent P2P 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}.

Input parameters:

- `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).

### `qgiv_list_registrations_by_date` (~154 tokens)

List P2P registrations by date range

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

Input parameters:

- `begin_date` (string, required): First day (yyyy-mm-dd).
- `end_date` (string, required): 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).

### `qgiv_get_registration` (~87 tokens)

Get P2P registration

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

Input parameters:

- `include_contact` (boolean): Include donor contact details (email, phone, postal address). Off by default: names, ids and amounts only.
- `registration_id` (integer, required): Numeric Qgiv id.

### `qgiv_list_events` (~119 tokens)

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.

Input parameters:

- `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).

### `qgiv_list_pledges` (~90 tokens)

List pledge options

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

Input parameters:

- `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).

### `qgiv_get_pledge` (~48 tokens)

Get pledge option

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

Input parameters:

- `pledge_id` (integer, required): Numeric Qgiv id.

### `qgiv_list_custom_fields` (~87 tokens)

List custom fields

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

Input parameters:

- `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).

### `qgiv_list_report_mappings` (~88 tokens)

List report mappings

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

Input parameters:

- `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).

### `qgiv_get_report_mapping` (~38 tokens)

Get report mapping

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

Input parameters:

- `mapping_id` (integer, required): Numeric Qgiv id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-qgiv/qgiv#diagnostics

## Score history

- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 62
- 2026-10-13: 62
- 2026-10-12: 60

## Common questions

### 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.

## Links

- Remote endpoint: https://qgiv.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/qgiv/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-qgiv/qgiv.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-qgiv/qgiv.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-qgiv/qgiv