# Relm CRM (remote · api.relmcrm.com)

API-first CRM for LLMs - contacts, companies, deals and activities over a native MCP server.

- Trust score: 75/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.relmcrm.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-relmcrm-relm/api.md), [page](https://verifymcp.io/servers/com-relmcrm-relm/api)

## Channel facts

- Endpoint: `https://api.relmcrm.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.10.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-08-03.

- **Endpoint Security**: 89/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 is enforced; there's no plaintext access path.
  - 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**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 2857 tokens (~69/item across 41 items; 41 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 70/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 9% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-relmcrm-relm https://api.relmcrm.com/mcp
```

### Codex

```toml
[mcp_servers.com-relmcrm-relm]
url = "https://api.relmcrm.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-relmcrm-relm": {
      "type": "remote",
      "url": "https://api.relmcrm.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-relmcrm-relm --url https://api.relmcrm.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-relmcrm-relm:
    url: "https://api.relmcrm.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-relmcrm-relm": {
      "type": "http",
      "url": "https://api.relmcrm.com/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-08-03 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 73, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 68, 0)

- [functional] Server version: 0.16.0 → 0.17.1

### 2026-07-27 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 67)

First indexed and scored.

## MCP tools (41)

### `relm_describe_schema` (~67 tokens)

Return the live schema: every object, its fields (built-in + custom), and all enum groups with their current values (contact types, activity types, etc). ALWAYS call this before guessing a type, stage, or field - it is the source of truth for what exists.

### `relm_search` (~38 tokens)

Cross-entity search over contacts, companies and deals by name/email/title.

Input parameters:

- `limit` (number)
- `query` (string, required)

### `relm_list` (~86 tokens)

List records of an object with keyset pagination. Optional filters vary by object (e.g. contact: email/company_id/type; deal: pipeline/stage/company_id; activity: contact_id/deal_id/type).

Input parameters:

- `cursor` (string)
- `filter` (object): object-specific filters
- `limit` (number)
- `object` (string, required): Which core object.

### `relm_get` (~32 tokens)

Fetch one record by id.

Input parameters:

- `id` (string, required)
- `object` (string, required): Which core object.

### `relm_create` (~99 tokens)

Create a record. `data` is the object's fields (see relm_describe_schema). Custom fields must be registered first (relm_create_field). A contact needs at least one of: a name, an identifier (email/phone/linkedin_url), a company, or a custom field (email is unique per workspace) - don't invent a placeholder email.

Input parameters:

- `data` (object, required)
- `object` (string, required): Which core object.

### `relm_update` (~68 tokens)

Patch a record. Pass if_match (the record's current version) for optimistic concurrency; a 412 means re-fetch and retry.

Input parameters:

- `id` (string, required)
- `if_match` (number)
- `object` (string, required): Which core object.
- `patch` (object, required)

### `relm_delete` (~45 tokens)

Soft-delete a record (recoverable via relm_restore). Never hard-destroys data.

Input parameters:

- `id` (string, required)
- `object` (string, required): Which core object.

### `relm_restore` (~33 tokens)

Restore a soft-deleted record.

Input parameters:

- `id` (string, required)
- `object` (string, required): Which core object.

### `relm_log_activity` (~65 tokens)

Log an activity (note/call/email/meeting/task) on a contact and/or deal. Convenience wrapper over create activity.

Input parameters:

- `body` (string)
- `contact_id` (string)
- `deal_id` (string)
- `type` (string)

### `relm_list_pipelines` (~18 tokens)

List pipelines with their ordered stages.

### `relm_create_pipeline` (~68 tokens)

Create a pipeline. Optionally provide stages [{key,label}] (defaults to lead/qualified/proposal/won/lost) and is_default.

Input parameters:

- `is_default` (boolean)
- `key` (string)
- `name` (string)
- `stages` (array)

### `relm_manage_stage` (~210 tokens)

Add, rename/retype, delete, or reorder stages in a pipeline. action=add: `key` (+optional label, ordinal, type). action=rename: `key` (existing) + any of new_key / label / type - keys are slugified and deals follow automatically (fixes a typo'd key). action=delete: `key` (a stage in use by deals cannot be deleted). action=reorder: `order` = every existing stage key exactly once, in the new order. `type` is the semantic stage type: open | won | lost - so 'is this deal won?' is a flag (stage_type on every deal), not per-pipeline string matching.

Input parameters:

- `action` (string, required)
- `key` (string)
- `label` (string)
- `new_key` (string)
- `order` (array)
- `ordinal` (number)
- `pipeline` (string, required)
- `type` (string)

### `relm_create_type` (~47 tokens)

Register a new object type in the schema (registry). Idempotent on key; returns the full type set.

Input parameters:

- `key` (string, required)
- `label` (string)

### `relm_create_field` (~105 tokens)

Register a new custom field on an object (contact/company/deal/activity). data_type: text|number|boolean|date|select|multiselect|currency|reference|email|url. Must be created before it can be written to a record.

Input parameters:

- `data_type` (string)
- `enum_group` (string)
- `key` (string, required)
- `label` (string)
- `object` (string, required)
- `required` (boolean)

### `relm_create_enum_value` (~78 tokens)

Add a value to an enum group (e.g. group 'contact.type' value 'partner'). Idempotent; returns the full value set. Use this when relm_create rejects an unknown type with a valid_options list.

Input parameters:

- `group` (string, required)
- `label` (string)
- `value` (string, required)

### `relm_batch` (~89 tokens)

Run up to 100 record writes in ONE call (contact/company/deal/activity) - the fast path for imports/migrations. operations: [{object, method:create|update|delete, data|patch, id?}]. Returns a per-op result array (partial success). Every op still counts against your quota (batch saves round-trips, not quota).

Input parameters:

- `operations` (array, required)

### `relm_automations_capabilities` (~51 tokens)

Discover the automation building blocks: valid trigger_events, condition ops, action types, channels/providers, and the shapes of automations/sequences/connections. Call before building a rule or sequence.

### `relm_connect_channel` (~100 tokens)

Connect a BYO messaging channel so automations can send. channel='email', provider='resend', api_key=<your Resend key>, from='Team <hi@you.com>' (must be a verified Resend sender). The key is encrypted at rest.

Input parameters:

- `api_key` (string, required)
- `channel` (string)
- `from` (string)
- `name` (string)
- `provider` (string)

### `relm_list_connections` (~21 tokens)

List connected messaging channels (never returns the secret key).

### `relm_create_automation` (~135 tokens)

Create a single-step rule: when <trigger_event> [if <conditions>] then <actions>. conditions=[{field,op,value}] (ANDed), actions=[{type,...}]. Example: trigger_event='deal.stage_changed', conditions=[{field:'stage',op:'eq',value:'won'}], actions=[{type:'create_activity',body:'Deal won!'}]. See relm_automations_capabilities.

Input parameters:

- `actions` (array, required)
- `conditions` (array)
- `enabled` (boolean)
- `name` (string, required)
- `trigger_event` (string, required)

### `relm_list_automations` (~19 tokens)

List reactive rules (automations).

### `relm_create_template` (~102 tokens)

Create a reusable email template. name, html (full HTML, {{field}} placeholders ok), optional subject + text (plaintext alt; auto-derived if omitted). Reference it from a rule/sequence step via {"type":"send_email","template":"<key or tmpl_id>"}.

Input parameters:

- `html` (string, required)
- `key` (string)
- `name` (string, required)
- `subject` (string)
- `text` (string)

### `relm_list_templates` (~15 tokens)

List reusable email templates.

### `relm_create_sequence` (~170 tokens)

Create a multi-step drip sequence. trigger={event,filter:[{field,op,value}]} auto-enrolls the matching entity's contact; exit_when=[{field,op,value}] stops it (re-checked before every send); steps=[{wait_days,subject,body}] (first step wait_days:0 sends now). enroll_existing:true also enrolls everything that currently matches. Example: 3 emails to contacts of deals entering stage 'lead', stop if the deal leaves 'lead'.

Input parameters:

- `channel` (string)
- `connection` (string)
- `enabled` (boolean)
- `enroll_existing` (boolean)
- `exit_when` (array)
- `name` (string, required)
- `steps` (array, required)
- `trigger` (object)

### `relm_list_sequences` (~20 tokens)

List drip sequences with their steps and enrollment counts.

### `relm_preview_sequence` (~37 tokens)

Dry-run a sequence: how many contacts would enroll now + the send schedule. No side effects.

Input parameters:

- `id` (string, required)

### `relm_enroll` (~68 tokens)

Manually enroll a contact into a sequence (idempotent per contact+sequence). Optional source={object,id} records what drove the enrollment (e.g. a deal).

Input parameters:

- `contact_id` (string, required)
- `sequence_id` (string, required)
- `source` (object)

### `relm_create_webhook` (~128 tokens)

Subscribe an https endpoint to CRM events. events=['*'] for all, or a subset of ['contact.created','contact.updated','deal.created','deal.updated','deal.stage_changed']. Returns a `secret` ONCE - the subscriber verifies the `Relm-Signature` header (t=<unix>,v1=<hmac-sha256 of "t.body">). Deliveries retry with backoff and dead-letter after 6 attempts.

Input parameters:

- `description` (string)
- `enabled` (boolean)
- `events` (array)
- `url` (string, required)

### `relm_list_webhooks` (~20 tokens)

List webhook subscriptions in this workspace/mode.

### `relm_delete_webhook` (~25 tokens)

Delete a webhook subscription by id.

Input parameters:

- `id` (string, required)

### `relm_get_automation` (~32 tokens)

Read one automation by id, with its trigger, conditions and actions.

Input parameters:

- `id` (string, required)

### `relm_get_sequence` (~55 tokens)

Read one drip sequence by id. view=sequence (default) returns it with its steps; view=enrollments lists who is enrolled and their state.

Input parameters:

- `id` (string, required)
- `view` (string)

### `relm_get_pipeline` (~42 tokens)

Read one pipeline by key or pl_ id, with its ordered stages and their semantic types (open/won/lost).

Input parameters:

- `pipeline` (string, required)

### `relm_get_webhook` (~67 tokens)

Read one webhook by id. view=webhook (default) returns the subscription; view=deliveries returns recent delivery attempts (status, retries, dead-letter) to debug why an endpoint isn't receiving events.

Input parameters:

- `id` (string, required)
- `view` (string)

### `relm_manage_automation` (~87 tokens)

Change an existing automation by id. action=disable stops it firing (use this to turn off a misbehaving rule); action=enable resumes it; action=delete removes it. To read one, use relm_get_automation. To change a rule's trigger/conditions/actions, delete and recreate.

Input parameters:

- `action` (string, required)
- `id` (string, required)

### `relm_manage_sequence` (~73 tokens)

Change an existing drip sequence by id. action=disable stops further sends (use this to halt a bad sequence); action=enable resumes; action=delete removes it. To read one or list its enrollments, use relm_get_sequence.

Input parameters:

- `action` (string, required)
- `id` (string, required)

### `relm_manage_pipeline` (~133 tokens)

Change an existing pipeline by key or pl_ id. action=rename changes its display `name` and/or its key (pass `new_key`) - deals link by internal id, so they follow a re-key automatically; action=set_default makes it the workspace default; action=delete removes it (fails if deals still use it - move them first). To read one, use relm_get_pipeline.

Input parameters:

- `action` (string, required)
- `name` (string): New display name
- `new_key` (string): New pipeline key (slugified); deals follow automatically
- `pipeline` (string, required)

### `relm_manage_webhook` (~69 tokens)

Pause or resume delivery for an existing webhook by id. action=enable/disable. To read one or inspect its delivery attempts, use relm_get_webhook. To remove it, use relm_delete_webhook.

Input parameters:

- `action` (string, required)
- `id` (string, required)

### `relm_delete_connection` (~38 tokens)

Delete a connected messaging channel by id (e.g. to remove a rotated/wrong Resend key).

Input parameters:

- `id` (string, required)

### `relm_get_usage` (~49 tokens)

Read this workspace's current billing period: requests used, plan, monthly limit, and any metered overage. Call this to see how close you are to the quota before a big import.

### `relm_set_spend_cap` (~87 tokens)

Set (or clear) the hard monthly overage spend cap in USD. overage_cap_usd: a number caps paid overage (requests 429 with spend_cap_reached past it), 0 = never any overage, null = unlimited. This is the recovery for a spend_cap_reached error.

Input parameters:

- `overage_cap_usd` (number|null, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-relmcrm-relm/api#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 74
- 2026-08-01: 74
- 2026-07-31: 73
- 2026-07-30: 67
- 2026-07-29: 69
- 2026-07-28: 68
- 2026-07-27: 68
- 2026-07-26: 67

## Links

- Remote endpoint: https://api.relmcrm.com/mcp
- Website: https://relmcrm.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-relmcrm-relm/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-relmcrm-relm/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-relmcrm-relm/api