Home / MCP registry index / io.usefulapi/beacon-crm
Beacon CRM MCP by usefulapi
io.usefulapi/beacon-crm in the official MCP registry.
Endpoint https://beacon-crm.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports.
We read its 11 tools on 2026-10-22. 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
beaconcrm_list_record_types beaconcrm_list_users beaconcrm_list_records beaconcrm_get_record beaconcrm_filter_records beaconcrm_create_record beaconcrm_update_record beaconcrm_upsert_record beaconcrm_delete_record beaconcrm_trigger_export beaconcrm_list_exports
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-beacon-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.