Should my agent depend on the MCP server com.obriym-crm/mcp?

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

Obriym CRM

com.obriym-crm/mcp

Operate Obriym CRM from your AI assistant: leads, deals, orders, products, dashboard, reports.

— the operator's own registry description reported

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

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.561 (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

latency188 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools42

vs populationhigh

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_658867f6e37d4f6ef6b951c7 · 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

add_order_item assign_lead complete_activity configure_pipeline convert_lead create_activity create_company create_contact create_deal create_lead create_order get_activity get_company get_contact get_customer get_dashboard_overview get_deal get_lead get_order get_product get_report get_workspace_info list_activities list_customers list_lead_sources list_orders list_pipeline_stages list_workspaces remove_order_item search_companies search_contacts search_deals search_leads search_products select_workspace set_lead_sources transition_deal update_company update_contact update_lead update_order_item update_order_status

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 A — an agent can pick and call these reliably.

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

42 of 42 tools graded · 42 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

1.3.5

server version obriym-crm

Capabilities: prompts resources 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:21Z	ok_tools	200	188	2025-06-18
2026-08-12T05:33:36Z	ok_tools	200	232	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.obriym-crm/mcp.svg)](https://robinsaige.com/s/com.obriym-crm/mcp)

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