Home / MCP registry index / io.usefulapi/bloomerang
Bloomerang MCP by usefulapi
io.usefulapi/bloomerang in the official MCP registry.
Endpoint https://bloomerang.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Search Bloomerang constituents and donations; log interactions, notes and tasks.
We read its 20 tools on 2026-10-26. 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
bloomerang_get_current_user bloomerang_search_constituents bloomerang_list_constituents bloomerang_get_constituent bloomerang_get_constituent_timeline bloomerang_list_constituent_relationships bloomerang_get_household bloomerang_list_transactions bloomerang_get_transaction bloomerang_list_funds bloomerang_list_campaigns bloomerang_list_appeals bloomerang_list_interactions bloomerang_list_notes bloomerang_list_tasks bloomerang_create_constituent bloomerang_update_constituent bloomerang_create_interaction bloomerang_create_note bloomerang_create_task
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-bloomerang)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.