io.usefulapi/virtuous-crm
REMOTE · VIRTUOUS-CRM.USEFULAPI.IO · SCANNED OCT 4
Search donors and contacts, giving history, notes and projects, and log notes, tags and gifts.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2518 tokens (~125/item across 20 items; 20 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 Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
How do I install the io.usefulapi/virtuous-crm MCP server?
io.usefulapi/virtuous-crm is a hosted endpoint at https://virtuous-crm.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 · virtuous-crm.usefulapi.io
claude mcp add --transport http io-usefulapi-virtuous-crm 'https://virtuous-crm.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-virtuous-crm": {
"url": "https://virtuous-crm.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-virtuous-crm": {
"type": "http",
"url": "https://virtuous-crm.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-virtuous-crm] url = "https://virtuous-crm.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-virtuous-crm": {
"type": "remote",
"url": "https://virtuous-crm.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-virtuous-crm --url 'https://virtuous-crm.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-virtuous-crm:
url: "https://virtuous-crm.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-virtuous-crm": {
"Transport": "http",
"Url": "https://virtuous-crm.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-virtuous-crm -t streamable-http -u 'https://virtuous-crm.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-virtuous-crm": {
"type": "http",
"url": "https://virtuous-crm.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +4
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 82 functional
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://virtuous-crm.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 virtuous-crm.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://virtuous-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://virtuous-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://virtuous-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://virtuous-crm.usefulapi.io/mcp |
| Authorisation server | https://virtuous-crm.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://virtuous-crm.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://virtuous-crm.usefulapi.io/mcp | HTTPS enforced | 301 | https://virtuous-crm.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 →
virtuous_add_contact_tag Tag a contact ~65
Apply an existing tag to a contact (find the tagId with virtuous_list_tags). Virtuous: POST /api/ContactTag.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id (integer). |
| tag_id | integer | yes | The tag id (integer). |
No output schema declared.
No examples provided.
virtuous_create_contact_note Log a note on a contact ~143
Add a note to a contact's timeline — a call, meeting, visit or other touchpoint. Writes to the donor record. Virtuous: POST /api/ContactNote.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id (integer). |
| important | boolean | – | Flag the note as important. |
| note | string | yes | The note text. |
| note_date_time | string | – | When it happened, ISO 8601 (defaults to now). |
| private | boolean | – | Make the note private. |
| time_spent | integer | – | Time spent, in minutes. |
| type | string | – | A contact note type configured in the organization. |
No output schema declared.
No examples provided.
virtuous_create_contact_transaction Submit a contact for import ~372
Submit a new or updated contact through Virtuous's import pipeline (the recommended way to add contacts). It is matched against existing contacts by name, email, phone, address and reference, bundled into an import at midnight, and only committed when a user reviews the import and clicks Run — so nothing is created in real time and no duplicates are forced. Virtuous: POST /api/Contact/Transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| address1 | string | – | – |
| address2 | string | – | – |
| city | string | – | – |
| contact_type | string | – | Contact type, e.g. Household or Organization. |
| country | string | – | – |
| custom_fields | object | – | Custom field name -> value. |
| string | – | – | |
| email_lists | array | – | Email list names to subscribe the contact to. |
| email_type | string | – | Email type as configured in Virtuous (see contact method types). |
| first_name | string | – | – |
| last_name | string | – | – |
| middle_name | string | – | – |
| name | string | – | Contact (household/organization) name. |
| origin_segment_code | string | – | Code of the segment that brought this contact in. |
| phone | string | – | – |
| phone_type | string | – | Phone type as configured in Virtuous (see contact method types). |
| postal | string | – | – |
| reference_id | string | – | The contact's id in that system. |
| reference_source | string | – | Your system's name, e.g. "Website" or "Stripe". |
| state | string | – | – |
| suffix | string | – | – |
| tags | string | – | Tag names to apply (Virtuous takes these as one string). |
| title | string | – | Name prefix, e.g. Mr., Dr. |
No output schema declared.
No examples provided.
virtuous_create_gift_transaction Submit a gift for import ~348
Record a gift (donation already received) through Virtuous's gift import pipeline — the method Virtuous recommends. The gift is matched to a contact, recurring gift or pledge, held until the nightly import, and only created when a user reviews the import and clicks Run. This records a gift; it does NOT charge anyone. Identify the donor with contact.id, contact.referenceId, or name/email details. Virtuous: POST /api/v2/Gift/Transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Gift amount, e.g. "100.00". |
| batch | string | – | Batch name. |
| check_number | string | – | – |
| contact | object | yes | The donor. Virtuous matches this against existing contacts. |
| currency_code | string | – | ISO currency code, e.g. USD. |
| custom_fields | object | – | Custom field name -> value. |
| designations | array | – | Split the gift across projects. |
| frequency | string | – | For a recurring gift: its frequency as named in Virtuous. |
| gift_date | string | yes | Gift date, e.g. 2026-09-29. |
| gift_type | string | yes | Gift type as configured in Virtuous, e.g. "Cash". |
| is_private | boolean | – | – |
| is_tax_deductible | boolean | – | – |
| notes | string | – | – |
| receipt_date | string | – | – |
| segment | string | – | Segment code the gift is attributed to. |
| transaction_id | string | – | The gift's id in that source (prevents double import). |
| transaction_source | string | – | Where the gift came from, e.g. "Website". |
No output schema declared.
No examples provided.
virtuous_find_contact Find a contact by email or reference ~116
Look up a single contact by email address, or by an external reference (reference source + id, e.g. Stripe customer id). Give either email, or both reference_source and reference_id; if both are given Virtuous prioritises the reference. Virtuous: GET /api/Contact/Find.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | The email address. | |
| reference_id | string | – | The identifier within that reference source. |
| reference_source | string | – | The reference source, e.g. Stripe, MailChimp, Shopify. |
No output schema declared.
No examples provided.
virtuous_get_contact Get a contact ~74
Fetch one contact (household, organization, foundation ...) with its address, giving summary (life-to-date, year-to-date, last gift), individuals and their contact methods, and custom fields. Virtuous: GET /api/Contact/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id (integer). |
No output schema declared.
No examples provided.
virtuous_get_current_organization Get the current organization ~61
Fetch the Virtuous organization this API key acts in — its name, time zone and culture, and whether the key's user is an administrator. A cheap way to confirm the key works. Virtuous: GET /api/Organization/Current.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
virtuous_get_gift Get a gift ~73
Fetch one gift in full: contact, type, date, amount and currency, batch, segment, grant, tribute, receipt date, designations to projects, premiums and custom fields. Virtuous: GET /api/Gift/{giftId}.
| Name | Type | Req | Description |
|---|---|---|---|
| gift_id | integer | yes | The gift id (integer). |
No output schema declared.
No examples provided.
virtuous_get_project Get a project ~66
Fetch one project: code, type, status, balances, financial need, date range, life-to-date and calendar-year giving and gift/giver counts. Virtuous: GET /api/Project/{projectId}.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | The project id (integer). |
No output schema declared.
No examples provided.
virtuous_get_query_options Get query options ~66
List the parameters, their types, allowed operators and value options that virtuous_query accepts for one record type. Call this BEFORE building a query. Virtuous: GET /api/<Resource>/QueryOptions.
| Name | Type | Req | Description |
|---|---|---|---|
| resource | string | yes | Which Virtuous record type to query. |
No output schema declared.
No examples provided.
virtuous_list_contact_gifts List a contact's gifts ~125
List a contact's giving history: gift id, type, date, amount, segment and batch. Use virtuous_get_gift for designations and full detail. Virtuous: GET /api/Gift/ByContact/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id (integer). |
| descending | boolean | – | Sort descending. |
| skip | integer | – | Records to skip (default 0). |
| sort_by | string | – | Sort field. |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
virtuous_list_contact_individuals List a contact's individuals ~72
List the individuals (people) that belong to a contact/household, with names, birth dates, and their emails and phones (contact methods). Virtuous: GET /api/ContactIndividual/ByContact/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id (integer). |
No output schema declared.
No examples provided.
virtuous_list_contact_notes List a contact's notes ~119
List the notes logged on a contact — calls, meetings, emails and other touchpoints — with type, date, text and author. Virtuous: GET /api/ContactNote/ByContact/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id (integer). |
| descending | boolean | – | Sort descending. |
| skip | integer | – | Records to skip (default 0). |
| sort_by | string | – | Sort field. |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
virtuous_list_contact_tags List a contact's tags ~90
List the tags applied to a contact (contactTagId, tagId, name). Virtuous: GET /api/ContactTag/ByContact/{contactId}.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_id | integer | yes | The contact id (integer). |
| skip | integer | – | Records to skip (default 0). |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
virtuous_list_events List events ~75
List the organization's events: name, type, location, start/end, invite and RSVP counts, attendance and total giving. Virtuous: GET /api/Event.
| Name | Type | Req | Description |
|---|---|---|---|
| skip | integer | – | Records to skip (default 0). |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
virtuous_list_tags List tags ~78
List the organization's tags (id, name, tag group). Use this to find a tagId before virtuous_add_contact_tag. Virtuous: GET /api/Tag.
| Name | Type | Req | Description |
|---|---|---|---|
| skip | integer | – | Records to skip (default 0). |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
virtuous_query Query records ~239
Run a Virtuous query-builder query against one record type (contacts, gifts, campaigns, projects, tasks, grants, pledges, recurring gifts, events ...). Conditions use parameter/operator names from virtuous_get_query_options. Returns { list, total }. For Contact and Gift, full_details returns full records instead of the abbreviated view. Virtuous: POST /api/<Resource>/Query.
| Name | Type | Req | Description |
|---|---|---|---|
| descending | boolean | – | Sort descending. |
| full_details | boolean | – | Contact and Gift only: return full records (Query/FullContact, Query/FullGift). |
| groups | array | – | Condition groups, as in the Virtuous query builder. Omit for all records. |
| include_archived | boolean | – | Contact queries only: include archived contacts. |
| resource | string | yes | Which Virtuous record type to query. |
| skip | integer | – | Records to skip (default 0). |
| sort_by | string | – | Field to sort by (e.g. for gifts: Id, Amount, GiftDate, ReceiptDate, Batch). |
| take | integer | – | Records to return, 1-1000 (default 10). |
No output schema declared.
No examples provided.
virtuous_search Global search ~128
Full-text search across contacts, individuals and entities (campaigns, projects, segments, tags) — the same search as the Virtuous search bar. Returns hits with highlights, grouped by kind. Virtuous: POST /api/Search.
| Name | Type | Req | Description |
|---|---|---|---|
| filter_types | array | – | Restrict to these kinds. Omit to search all. |
| query | string | yes | Free-text search, e.g. a name, email or organization. |
| skip | integer | – | Records to skip (default 0). |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
virtuous_search_contacts Search contacts ~110
Find contacts whose name, email, phone or address fully or partially matches a search string. Returns id, name, contact type, email, phone and address per match. Virtuous: POST /api/Contact/Search.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | yes | Text to match, e.g. "Weyland" or an email address. |
| skip | integer | – | Records to skip (default 0). |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
virtuous_search_projects Search projects ~98
Find projects (funds / designations gifts are given to) by name or code, with their balances, financial need and life-to-date giving. Virtuous: POST /api/Project/Search.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | yes | Text to match against project name or code. |
| skip | integer | – | Records to skip (default 0). |
| take | integer | – | Records to return, 1-100 (default 10). |
No output schema declared.
No examples provided.
What is the io.usefulapi/virtuous-crm MCP server?
io.usefulapi/virtuous-crm is an MCP server listed in the public MCP registry as io.usefulapi/virtuous-crm. Search donors and contacts, giving history, notes and projects, and log notes, tags and gifts. This page covers its hosted endpoint (https://virtuous-crm.usefulapi.io/mcp).
Is the io.usefulapi/virtuous-crm MCP server safe to use?
io.usefulapi/virtuous-crm scores 77 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 io.usefulapi/virtuous-crm MCP server expose?
io.usefulapi/virtuous-crm exposes 20 tools: virtuous_get_current_organization, virtuous_search, virtuous_search_contacts, virtuous_get_contact, virtuous_find_contact, and 15 more. Their descriptions and schemas cost roughly 2,518 tokens of context every time the server is loaded.
Does the io.usefulapi/virtuous-crm MCP server require authentication?
Yes. io.usefulapi/virtuous-crm 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 io.usefulapi/virtuous-crm MCP server still maintained?
io.usefulapi/virtuous-crm is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.