# Beacon CRM MCP by usefulapi (remote · beacon-crm.usefulapi.io)

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

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `beacon-crm.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-beacon-crm/beacon-crm.md), [page](https://verifymcp.io/servers/io-usefulapi-beacon-crm/beacon-crm)

## Channel facts

- Endpoint: `https://beacon-crm.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2014 tokens (~183/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Beacon CRM MCP by usefulapi server?

Beacon CRM MCP by usefulapi is a hosted endpoint at https://beacon-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.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-beacon-crm": {
      "url": "https://beacon-crm.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-beacon-crm": {
      "type": "http",
      "url": "https://beacon-crm.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-beacon-crm]
url = "https://beacon-crm.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-beacon-crm": {
      "type": "remote",
      "url": "https://beacon-crm.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-beacon-crm --url 'https://beacon-crm.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-beacon-crm:
    url: "https://beacon-crm.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-beacon-crm": {
      "Transport": "http",
      "Url": "https://beacon-crm.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-beacon-crm -t streamable-http -u 'https://beacon-crm.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-beacon-crm": {
      "type": "http",
      "url": "https://beacon-crm.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 64, +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.

### 2026-10-14 (score 63, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (11)

### `beaconcrm_list_record_types` (~66 tokens)

List record types and fields

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.

### `beaconcrm_list_users` (~89 tokens)

List account users

List the users of the Beacon account (id, role, name, email). Use the inner user.id for 'link to a user' fields. GET /users.

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).

### `beaconcrm_list_records` (~208 tokens)

List records

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}.

Input parameters:

- `archived` (boolean): true = list deleted (archived) records instead of active ones.
- `entity` (string, required): Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `populate` (boolean): Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted.
- `sort_by` (string): Field key to sort by, e.g. created_at.
- `sort_direction` (string): Sort direction (default: Beacon's default order).

### `beaconcrm_get_record` (~99 tokens)

Get record

One record by type and id, with all its fields. GET /entity/{entity}/{id}.

Input parameters:

- `entity` (string, required): Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types.
- `id` (integer, required): Record id.
- `populate` (boolean): Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted.

### `beaconcrm_filter_records` (~420 tokens)

Filter records

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.

Input parameters:

- `archived` (boolean): true = list deleted (archived) records instead of active ones.
- `entity` (string, required): Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types.
- `filter_conditions` (array, required): Filter conditions (see the description). An empty list matches every record.
- `filter_strictness` (string): "all" = AND (default), "any" = OR.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Results per page, 1-100 (default 25).
- `populate` (boolean): Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted.
- `sort_by` (string): Field key to sort by, e.g. created_at.
- `sort_direction` (string): Sort direction (default: Beacon's default order).

### `beaconcrm_create_record` (~186 tokens)

Create record

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}.

Input parameters:

- `entity` (string, required): Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types.
- `fields` (object, required): Field values keyed by field key, in Beacon's field formats (see beaconcrm_list_record_types for keys). Select and point-to-record fields are ARRAYS (e.g. {"type": ["Donation"], "customer": [1725]});…

### `beaconcrm_update_record` (~195 tokens)

Update record

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}.

Input parameters:

- `entity` (string, required): Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types.
- `fields` (object, required): Field values keyed by field key, in Beacon's field formats (see beaconcrm_list_record_types for keys). Select and point-to-record fields are ARRAYS (e.g. {"type": ["Donation"], "customer": [1725]});…
- `id` (integer, required): Record id.

### `beaconcrm_upsert_record` (~251 tokens)

Create or update record by key field

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.

Input parameters:

- `entity` (string, required): Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types.
- `fields` (object, required): Field values keyed by field key, in Beacon's field formats (see beaconcrm_list_record_types for keys). Select and point-to-record fields are ARRAYS (e.g. {"type": ["Donation"], "customer": [1725]});…
- `primary_field_key` (string, required): Field key used to match an existing record, e.g. emails or external_id.

### `beaconcrm_delete_record` (~126 tokens)

Delete record

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}.

Input parameters:

- `entity` (string, required): Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types.
- `id` (integer, required): Id of the record to delete.

### `beaconcrm_trigger_export` (~97 tokens)

Start an export

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.

Input parameters:

- `entity_export_template_id` (integer, required): Id of the export template (shown in the Beacon URL when you view the template).

### `beaconcrm_list_exports` (~72 tokens)

List exports

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.

Input parameters:

- `entity_export_id`: Only this export (the id returned by beaconcrm_trigger_export).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-beacon-crm/beacon-crm#diagnostics

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 60
- 2026-10-12: 60

## Common questions

### What is the Beacon CRM MCP by usefulapi server?

Beacon CRM MCP by usefulapi is listed in the public MCP registry as io.usefulapi/beacon-crm. Read and filter Beacon CRM records of any type; create, update, upsert, delete records; run exports. This page covers its hosted endpoint (https://beacon-crm.usefulapi.io/mcp).

### Is the Beacon CRM MCP by usefulapi server safe to use?

Beacon CRM MCP by usefulapi scores 64 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 Beacon CRM MCP by usefulapi server expose?

Beacon CRM MCP by usefulapi exposes 11 tools: beaconcrm_list_record_types, beaconcrm_list_users, beaconcrm_list_records, beaconcrm_get_record, beaconcrm_filter_records, and 6 more. Their descriptions and schemas cost roughly 1,809 tokens of context every time the server is loaded.

### Does the Beacon CRM MCP by usefulapi server require authentication?

Yes. Beacon CRM MCP by usefulapi 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 Beacon CRM MCP by usefulapi server still maintained?

Beacon CRM MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://beacon-crm.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/beacon-crm/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-beacon-crm/beacon-crm.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-beacon-crm/beacon-crm.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-beacon-crm/beacon-crm