Should my agent depend on the MCP server com.relmcrm/relm?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Relm CRM

com.relmcrm/relm

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

— the operator's own registry description reported

Publisher com.relmcrm · first seen 2026-08-12 · endpoint https://api.relmcrm.com/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.535 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency503 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools41

vs populationhigh

capabilities1

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_0b2dc627718bf357a0e1db8f · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

relm_automations_capabilities relm_batch relm_connect_channel relm_create relm_create_automation relm_create_enum_value relm_create_field relm_create_pipeline relm_create_sequence relm_create_template relm_create_type relm_create_webhook relm_delete relm_delete_connection relm_delete_webhook relm_describe_schema relm_enroll relm_get relm_get_automation relm_get_pipeline relm_get_sequence relm_get_usage relm_get_webhook relm_list relm_list_automations relm_list_connections relm_list_pipelines relm_list_sequences relm_list_templates relm_list_webhooks relm_log_activity relm_manage_automation relm_manage_pipeline relm_manage_sequence relm_manage_stage relm_manage_webhook relm_preview_sequence relm_restore relm_search relm_set_spend_cap relm_update

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	41/41	✓
has a description	41/41	✓
description is substantive	36/41	36/41
parameters are typed	41/41	✓
parameters are described	9/41	9/41

41 of 41 tools graded · 41 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.17.1

server version relm

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:26Z	ok_tools	200	503	2025-06-18
2026-08-12T05:33:41Z	ok_tools	200	581	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/com.relmcrm/relm.svg)](https://robinsaige.com/s/com.relmcrm/relm)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview