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

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

Coordinalo — Service Business Operations

com.coordinalo/mcp-server

Scheduling, availability, clients, billing and CRM for appointment-based services.

— the operator's own registry description reported

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

allow

verdict

rich-solo

cluster

ok_tools

answers

111

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

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

latency256 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools111

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_e73bebffeff0a50c89dcb3d8 · 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

admin_create_service admin_list_providers admin_set_availability admin_toggle_discoverable agendas_create agendas_delete agendas_get agendas_list agendas_update availability_get_provider_schedule availability_get_slots booking_cancel booking_create booking_create_recurring booking_get booking_list booking_list_requests booking_reschedule booking_resolve_request booking_update_status cierre_cerrar_org cierre_crear_cliente cierre_distribuir_utilidades cierre_eliminar_cliente cierre_evaluar_org cierre_listar_clientes cierre_listar_utilidades cierre_preview_cliente client_create client_get client_list client_update comms_create_campaign comms_get_campaign comms_get_preferences comms_list_audiences comms_list_campaigns comms_render_message comms_send_campaign comms_send_message comms_update_preferences delivery_confirmations_list disputes_list dunning_configure dunning_get_config email_domain_delete email_domain_get email_domain_register email_domain_verify finance_aging finance_client_balance finance_create_cobro finance_create_venta finance_get_cobro finance_list_cobros finance_list_confirmations finance_list_gastos finance_list_invoices finance_list_payments finance_list_ventas finance_register_payment finance_send_confirmations lifecycle_get_state lifecycle_history lifecycle_transition members_invite members_list org_summary org_update payroll_get_summary payroll_list_records portal_cancel_reschedule_request portal_confirm_delivery portal_propose_reschedule portal_report_session portal_session_cancel portal_session_confirm provider_create provider_get provider_get_stats provider_update public_availability_get_slots public_booking_cancel public_booking_confirm public_booking_create public_booking_get public_booking_reschedule public_service_list reminders_get_config reminders_update_config report_dashboard report_deuda_real report_no_shows report_occupancy report_revenue report_sc_summary resources_list scheduling_book scheduling_cancel scheduling_confirm scheduling_reschedule service_assign_provider service_create service_list service_update session_note_get session_note_upsert settings_get settings_update treatment_plans_get treatment_plans_list

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	111/111	✓
has a description	111/111	✓
description is substantive	111/111	✓
parameters are typed	110/111	110/111
parameters are described	0/111	0/111

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

4.1.0

server version coordinalo

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:01Z	ok_tools	200	256	2025-06-18
2026-08-12T05:33:17Z	ok_tools	200	410	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.coordinalo/mcp-server.svg)](https://robinsaige.com/s/com.coordinalo/mcp-server)

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