Skip to content

Beacon CRM MCP by usefulapi

io.usefulapi/beacon-crmusefulapi.iostreamable-httpv1.27.4Scanned

Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports.

11 tools: 3 can delete or cancel things, 2 change things and 6 only read.

Tools: 3 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 11
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

5 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Beacon CRM MCP by usefulapi can do

The Beacon CRM MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (3 tools: beaconcrm_update_record, beaconcrm_upsert_record and beaconcrm_delete_record) and create or change data (2 tools: beaconcrm_create_record and beaconcrm_trigger_export). 6 tools only read.

1 tool reads private data (beaconcrm_list_users); 11 tools bring in text other people can write (beaconcrm_list_record_types, beaconcrm_list_users, beaconcrm_list_records and 8 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.27.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

11 tools

Deletes or cancels 3Claude Code: deny
  • beaconcrm_delete_recordWRITE, DESTRUCTIVE: delete ONE record.Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_delete_record" says "delete": a word for removing or ending something.
    • The description says "irreversible".
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE, DESTRUCTIVE: delete ONE record. Beacon keeps deleted records as 'archived' (listable with archived=true), but this server has no restore tool, so treat the deletion as irreversible. Related data that depends on the record may be affected. It is sent once and never retried. DELETE /entity/{entity}/{id}.

    Annotations the server declares

    • title: Delete record
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • beaconcrm_update_recordWRITE: change fields of ONE existing record.Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_update_record" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: change fields of ONE existing record. Only the fields you pass are changed; a select or reference field passed as an empty array [] is CLEARED, removing its existing values. The previous values are not kept by this tool. Beacon workflows may run as a result. PATCH /entity/{entity}/{id}.

    Annotations the server declares

    • title: Update record
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • beaconcrm_upsert_recordWRITE: create a record, or update the existing one whose key field matches.Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_upsert_record" says "upsert": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: create a record, or update the existing one whose key field matches. `primary_field_key` names the field used to find the match (for example "emails" for a person, or "external_id"); `fields` must contain a value for it. If a record matches it is UPDATED with the given fields (an empty array leaves an existing value untouched on upsert); otherwise a new record is created. Beacon workflows may run as a result. PUT /entity/{entity}/upsert.

    Annotations the server declares

    • title: Create or update record by key field
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 2Claude Code: ask
  • beaconcrm_create_recordWRITE: create ONE new record of the given type in the live Beacon database.Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_create_record" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: create ONE new record of the given type in the live Beacon database. Not idempotent: calling it twice creates two records (use beaconcrm_upsert_record to avoid duplicates). Beacon workflows may run as a result. Invalid field values are rejected with the rule that failed. POST /entity/{entity}.

    Annotations the server declares

    • title: Create record
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • beaconcrm_trigger_exportWRITE: start an export job from an existing export template (created in Beacon).Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_trigger_export" says "trigger": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    WRITE: start an export job from an existing export template (created in Beacon). Returns the new export's id with status in_progress; then poll beaconcrm_list_exports with that id until progress is 100 and it carries a download url. Each call starts another job. POST /entity_export/trigger.

    Annotations the server declares

    • title: Start an export
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • beaconcrm_filter_recordsSearch records of one type with Beacon filter conditions (read-only; it uses POST because the filter is a body).Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "search" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Search records of one type with Beacon filter conditions (read-only; it uses POST because the filter is a body). Each condition is {"field", "operator", "value"}. Operators by field type: text == != starts_with ends_with contains not_contains null not_null; select (value is an array) contains not_contains in not_in null not_null; number == != > < null not_null; date date_on date_after date_before date_between (value e.g. "2026-01-01", "last_month", or ["2026-01-01","2026-06-01"]); checkbox == true; point-to-record (value is an array of ids) contains not_contains. Location parts: address.city etc.; emails: emails.email. Conditions can nest as {"filter_conditions": [...], "filter_strictness": "all"|"any"}. Example: [{"field":"emails.email","operator":"==","value":"a@b.org"}]. POST /entities/{entity}/filter.

    Annotations the server declares

    • title: Filter records
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • beaconcrm_get_recordOne record by type and id, with all its fields.Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_get_record" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    One record by type and id, with all its fields. GET /entity/{entity}/{id}.

    Annotations the server declares

    • title: Get record
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • beaconcrm_list_exportsList recent export jobs with status, progress (100 = complete) and, when complete, a signed download url.Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_list_exports" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List recent export jobs with status, progress (100 = complete) and, when complete, a signed download url. Pass entity_export_id to check one job started by beaconcrm_trigger_export. GET /entity_exports.

    Annotations the server declares

    • title: List exports
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • beaconcrm_list_record_typesList the record types of this Beacon account (people, organisations, payments, custom types, ...) with their fields (keys, types, options).Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_list_record_types" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List the record types of this Beacon account (people, organisations, payments, custom types, ...) with their fields (keys, types, options). Call this first: the keys are what the other tools take as `entity` and as field names. GET /entity_types.

    Annotations the server declares

    • title: List record types and fields
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • beaconcrm_list_recordsList records of one type (for example person, organization, payment), one page at a time.Reads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_list_records" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List records of one type (for example person, organization, payment), one page at a time. Use beaconcrm_filter_records to search by field values. GET /entities/{entity}.

    Annotations the server declares

    • title: List records
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • beaconcrm_list_usersList the users of the Beacon account (id, role, name, email).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "beaconcrm_list_users" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    List the users of the Beacon account (id, role, name, email). Use the inner user.id for 'link to a user' fields. GET /users.

    Annotations the server declares

    • title: List account users
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:32 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://beacon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://beacon-crm.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 5 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://beacon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://beacon-crm.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.27.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http beacon-crm https://beacon-crm.usefulapi.io/mcp
claude mcp add --transport http beacon-crm https://beacon-crm.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__beacon-crm__beaconcrm_list_record_types",
      "mcp__beacon-crm__beaconcrm_list_users",
      "mcp__beacon-crm__beaconcrm_list_records",
      "mcp__beacon-crm__beaconcrm_get_record",
      "mcp__beacon-crm__beaconcrm_filter_records",
      "mcp__beacon-crm__beaconcrm_list_exports"
    ],
    "ask": [
      "mcp__beacon-crm__beaconcrm_create_record",
      "mcp__beacon-crm__beaconcrm_trigger_export"
    ],
    "deny": [
      "mcp__beacon-crm__beaconcrm_update_record",
      "mcp__beacon-crm__beaconcrm_upsert_record",
      "mcp__beacon-crm__beaconcrm_delete_record"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as beacon-crm. Review it before you use it.

Capability tags behind 11 rules
  • mcp__beacon-crm__beaconcrm_list_record_types untrusted-input
  • mcp__beacon-crm__beaconcrm_list_users private-data, untrusted-input
  • mcp__beacon-crm__beaconcrm_list_records untrusted-input
  • mcp__beacon-crm__beaconcrm_get_record untrusted-input
  • mcp__beacon-crm__beaconcrm_filter_records untrusted-input
  • mcp__beacon-crm__beaconcrm_create_record untrusted-input
  • mcp__beacon-crm__beaconcrm_update_record untrusted-input
  • mcp__beacon-crm__beaconcrm_upsert_record untrusted-input
  • mcp__beacon-crm__beaconcrm_delete_record untrusted-input
  • mcp__beacon-crm__beaconcrm_trigger_export untrusted-input
  • mcp__beacon-crm__beaconcrm_list_exports untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/beacon-crm/verify?hash=7fdf763967752c079f04d3fe9311f6ae56c04fb9617fb4c99deb25df1ac81648" | jq -e '.changed == false'

Pinned hash 7fdf76396775, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/beacon-crm/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/beacon-crm
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/beacon-crm.svg)](https://radar.anlyon.com/servers/io.usefulapi/beacon-crm)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

Beacon CRM MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Beacon CRM MCP by usefulapi safe?

No scan can promise that. What its definitions show: 11 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Beacon CRM MCP by usefulapi delete data?

Yes. 3 tools can delete, cancel or revoke something: beaconcrm_update_record, beaconcrm_upsert_record and beaconcrm_delete_record.

Can the Beacon CRM MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Beacon CRM MCP by usefulapi have?

11 tools: 3 destructive, 2 write, 6 read. beaconcrm_update_record, beaconcrm_upsert_record, beaconcrm_delete_record, beaconcrm_create_record, beaconcrm_trigger_export, beaconcrm_list_record_types, beaconcrm_list_users, beaconcrm_list_records and 3 more.

Does the Beacon CRM MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Beacon CRM MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Beacon CRM MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.