Home / MCP registry index / io.usefulapi/virtuous-crm
Virtuous MCP by usefulapi
io.usefulapi/virtuous-crm in the official MCP registry.
Endpoint https://virtuous-crm.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Search donors and contacts, giving history, notes and projects, and log notes, tags and gifts.
We read its 20 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
virtuous_get_current_organization virtuous_search virtuous_search_contacts virtuous_get_contact virtuous_find_contact virtuous_list_contact_individuals virtuous_list_contact_notes virtuous_list_contact_tags virtuous_list_contact_gifts virtuous_get_gift virtuous_list_tags virtuous_search_projects virtuous_get_project virtuous_list_events virtuous_get_query_options virtuous_query virtuous_create_contact_note virtuous_add_contact_tag virtuous_create_contact_transaction virtuous_create_gift_transaction
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-virtuous-crm)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.