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.
Available components
Last scanned (4 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +3
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://beacon-crm.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of beacon-crm.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://beacon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://beacon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://beacon-crm.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://beacon-crm.usefulapi.io/mcp |
| Authorisation server | https://beacon-crm.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://beacon-crm.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/beacon-crm/ |
| http (plaintext) | http://beacon-crm.usefulapi.io/mcp | Inconclusive | 302 | http://beacon-crm.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
beaconcrm_create_record Create record ~186
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| fields | object | yes | 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]});… |
No output schema declared.
No examples provided.
beaconcrm_delete_record Delete record ~126
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| id | integer | yes | Id of the record to delete. |
No output schema declared.
No examples provided.
beaconcrm_filter_records Filter records ~420
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = list deleted (archived) records instead of active ones. |
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| filter_conditions | array | yes | 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). |
No output schema declared.
No examples provided.
beaconcrm_get_record Get record ~99
One record by type and id, with all its fields. GET /entity/{entity}/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| id | integer | yes | Record id. |
| populate | boolean | – | Include data from linked records (point-to-another-record fields). Beacon's default applies when omitted. |
No output schema declared.
No examples provided.
beaconcrm_list_exports List exports ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_export_id | – | – | Only this export (the id returned by beaconcrm_trigger_export). |
No output schema declared.
No examples provided.
beaconcrm_list_record_types List record types and fields ~66
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
beaconcrm_list_records List records ~208
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | true = list deleted (archived) records instead of active ones. |
| entity | string | yes | 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). |
No output schema declared.
No examples provided.
beaconcrm_list_users List account users ~89
List the users of the Beacon account (id, role, name, email). Use the inner user.id for 'link to a user' fields. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
beaconcrm_trigger_export Start an export ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_export_template_id | integer | yes | Id of the export template (shown in the Beacon URL when you view the template). |
No output schema declared.
No examples provided.
beaconcrm_update_record Update record ~195
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| fields | object | yes | 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 | yes | Record id. |
No output schema declared.
No examples provided.
beaconcrm_upsert_record Create or update record by key field ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | yes | Record type key, e.g. person, organization, payment or a custom type such as c_application. See beaconcrm_list_record_types. |
| fields | object | yes | 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 | yes | Field key used to match an existing record, e.g. emails or external_id. |
No output schema declared.
No examples provided.
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.
remote · beacon-crm.usefulapi.io
claude mcp add --transport http io-usefulapi-beacon-crm 'https://beacon-crm.usefulapi.io/mcp'
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.