Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Coordinalo — Service Business Operations

REMOTE · COORDINALO.COM · SCANNED SEP 25

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

Available components

0 this week 75 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 13268 tokens (~118/item across 112 items; 112 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "finance_send_confirmations" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 113 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Coordinalo — Service Business Operations MCP server?

Coordinalo — Service Business Operations is a hosted endpoint at https://coordinalo.com/api/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 · coordinalo.com

# add to Claude Code
claude mcp add --transport http com-coordinalo-mcp-server 'https://coordinalo.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-coordinalo-mcp-server": {
      "url": "https://coordinalo.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-coordinalo-mcp-server": {
      "type": "http",
      "url": "https://coordinalo.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-coordinalo-mcp-server]
url = "https://coordinalo.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-coordinalo-mcp-server": {
      "type": "remote",
      "url": "https://coordinalo.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-coordinalo-mcp-server --url 'https://coordinalo.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-coordinalo-mcp-server:
    url: "https://coordinalo.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-coordinalo-mcp-server": {
      "Transport": "http",
      "Url": "https://coordinalo.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-coordinalo-mcp-server -t streamable-http -u 'https://coordinalo.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-coordinalo-mcp-server": {
      "type": "http",
      "url": "https://coordinalo.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 15 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 5 Sept 26 0
    • Stability: fail → pass ▲ security
  • 27 Aug 26 75
    • New tool “report_evidence_gates” functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Aug 26 0
    • Tool “settings_get” rewrote its description, which is the text the model reads security
    • Tool “settings_update” rewrote its description, which is the text the model reads security
    • “settings_get” added an optional parameter “group” cosmetic
  • 16 Aug 26 0
    • Tool “scheduling_cancel” rewrote its description, which is the text the model reads security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 25 Sept 2026 · Probed https://coordinalo.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=coordinalo.com CN=YR1,O=Let's Encrypt,C=US 6 Sept 2026 5 Dec 2026 RSA 2048 SHA256-RSA 6e976eb74d8cbc6879947648f39e5239206
SANs: coordinalo.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of coordinalo.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
coordinalo.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://coordinalo.com/api/mcp Verified 200
http (plaintext) http://coordinalo.com/api/mcp HTTPS enforced 308 https://coordinalo.com/api/mcp
MCP tools · 112 exposed · ~12,666 tokens

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 →

Tool Tokens
scheduling_confirm ~92

Confirm a booking (Servicialo spec). Dual-mode: (1) with credential — uses the confirmation token from scheduling_book, no API key needed; (2) with booking_id — uses API key to confirm an existing session. Returns confirmed status with timestamp.

NameTypeReqDescription
apiKeystring––
booking_idstring––
credentialstring––
orgSlugstringyes–

No output schema declared.

No examples provided.

scheduling_reschedule ~89

Reschedule a session to a new time (Servicialo spec). Cancels the original session and creates a new one at the specified datetime. Requires confirm: true and X-Org-Api-Key.

NameTypeReqDescription
apiKeystring––
confirmbooleanyes–
new_datetimestringyes–
orgSlugstringyes–
session_idstringyes–

No output schema declared.

No examples provided.

service_assign_provider ~88

Assign or unassign a provider to/from a service. Controls which providers can deliver which services.

NameTypeReqDescription
actionstringyes–
apiKeystring––
commissionnumber––
confirmboolean––
orgSlugstringyes–
pricenumber––
providerIdstringyes–
serviceIdstringyes–

No output schema declared.

No examples provided.

service_create ~243

Create a new bookable service in an existing organization. Use this for day-to-day service management (requires X-Org-Api-Key). For initial org setup, prefer admin_create_service instead. After creating, use service_assign_provider to link providers. A service without providers cannot accept bookings. Optional delivery-verification overrides per service: verificationLevel (none = silent auto-complete, legacy; default_confirm = both can confirm and silence auto-confirms after the org window; dual_confirm = the client must positively confirm, silence does NOT; documented = the provider must attach evidence) and qualityCapture (ask the client for a 1–5 rating on confirmation). Omit both to inherit the organization defaults.

NameTypeReqDescription
apiKeystring––
categorystring––
currencystring––
descriptionstring––
durationintegeryes–
isDiscoverableboolean––
modalidadstring––
namestringyes–
orgSlugstringyes–
pricenumberyes–
providerIdstring––
qualityCapture–––
verificationLevel–––

No output schema declared.

No examples provided.

service_list ~66

List services of an organization. Can filter by active status, discoverability, or category.

NameTypeReqDescription
activeOnlyboolean––
apiKeystring––
categorystring––
discoverableOnlyboolean––
orgSlugstringyes–

No output schema declared.

No examples provided.

service_update ~200

Update an existing service (price, duration, status, etc.). Creates a price history entry if price changes. Delivery-verification overrides can be changed too: verificationLevel (none / default_confirm / dual_confirm / documented — see service_create for semantics) and qualityCapture (1–5 rating on confirmation). Pass null on either to reset that field and inherit the organization default again; omit to leave it unchanged.

NameTypeReqDescription
apiKeystring––
categorystring––
currencystring––
descriptionstring––
durationinteger––
isActiveboolean––
isDiscoverableboolean––
modalidadstring––
namestring––
orgSlugstringyes–
pricenumber––
publicDescriptionstring––
qualityCapture–––
serviceIdstringyes–
verificationLevel–––

No output schema declared.

No examples provided.

session_note_get ~119

Read the clinical note of a session. Non-restricted notes return full content. Notes marked dataSensitivity=restricted return metadata only (type, sensitivity, timestamps, which fields are present) with the clinical text withheld — pass includeRestricted: true to retrieve the full content, which logs an audited restricted-access event and increments the access counter. Returns note: null if the session has no note.

NameTypeReqDescription
apiKeystring––
includeRestrictedboolean––
orgSlugstringyes–
sessionIdstringyes–

No output schema declared.

No examples provided.

session_note_upsert ~186

Create or update the clinical note (ficha) of a session: evolution, treatmentPerformed, nextSessionPlan, type (evaluacion/tratamiento/derivacion/cierre), progressMetrics, etc. One note per session (upsert). Sensitivity is resolved automatically (health-vertical orgs default to restricted). NOTE: unlike the provider's own UI save, this does NOT create the provider-confirmed DeliveryProof nor award practice points — those are provider-bound actions (PDC-SEC-001); use the provider portal / REST for delivery confirmation.

NameTypeReqDescription
apiKeystring––
dataSensitivitystring––
evolution–––
isPrivateboolean––
nextSessionPlan–––
orgSlugstringyes–
sessionIdstringyes–
treatmentPerformed–––
type–––

No output schema declared.

No examples provided.

settings_get ~261

Get organization settings. THIS IS THE ENTRY POINT for anything configurable: call it with no filters first to get the full map. Settings are indexed on two axes — `group` (the sections a human sees in the settings screen: profile, availability, client_fields, communication, reminders, automations, finances, delivery, cancellation, tax) and `chapter` (the onboarding-interview sequence: basics, availability, communication, finances, policies, reminders, client_data). Prefer `group`. Or pass `keys` for specific settings (comma-separated, e.g. "policies.noShowMaxStrikes,finances.clientPaymentTiming"). Covers ~88 keys including cancellation-policy tiers, granular reminder timing, dunning sequence, retention, delivery verification and the SII tax profile. The response also carries `meta` (label, type, valid options and dependencies per key) and `panels` — the configuration surfaces that are NOT scalar settings (bank accounts, payment credentials, API keys, members): each panel names the tools that cover it, or states why none does.

NameTypeReqDescription
apiKeystring––
chapterstring––
groupstring––
keysstring––
orgSlugstringyes–

No output schema declared.

No examples provided.

settings_update ~187

Update organization settings. Partial update — only provided keys are changed. Pass a settings object with key-value pairs (e.g. {"policies.noShowMaxStrikes": 3, "finances.clientPaymentTiming": "BEFORE"}). ALL values are validated before ANY is written: if one key fails, nothing changes — so related keys can be sent together and either all land or none do. That matters for settings with invariants between them (the cancellation tiers, where the partial-charge window must sit closer to the appointment than the no-charge one) and for the SII tax profile, whose legally required fields must arrive in a single call the first time. Returns the full updated settings for the affected chapters. See settings_get for available keys, valid values and dependencies.

NameTypeReqDescription
apiKeystring––
orgSlugstringyes–
settingsobjectyes–

No output schema declared.

No examples provided.

treatment_plans_get ~84

Get the full detail of a single treatment/care plan by id: diagnosis, objectives, notes, status timeline, expiration, the intake session, and all plan items (service, quantity, frequency, priority, sessions booked/completed). Read-only.

NameTypeReqDescription
apiKeystring––
orgSlugstringyes–
planIdstringyes–

No output schema declared.

No examples provided.

treatment_plans_list ~124

List treatment/care plans of an organization with client, provider, status, objectives and their items (services with quantity/frequency/priority). Filter by clientId, status or proveedorId; paginated (page/limit). Read-only — plan creation/editing stays in the UI (requires clinical supervision).

NameTypeReqDescription
apiKeystring––
clientIdstring––
limitinteger––
orgSlugstringyes–
pageinteger––
proveedorIdstring––
statusstring––

No output schema declared.

No examples provided.

Common questions

What is the Coordinalo — Service Business Operations MCP server?

Coordinalo — Service Business Operations is an MCP server listed in the public MCP registry as com.coordinalo/mcp-server. Scheduling, availability, clients, billing and CRM for appointment-based services. This page covers its hosted endpoint (https://coordinalo.com/api/mcp).

Is the Coordinalo — Service Business Operations MCP server safe to use?

Coordinalo — Service Business Operations scores 75 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 Coordinalo — Service Business Operations MCP server expose?

Coordinalo — Service Business Operations exposes 112 tools: dunning_get_config, dunning_configure, admin_list_providers, admin_create_service, admin_set_availability, and 107 more. Their descriptions and schemas cost roughly 12,666 tokens of context every time the server is loaded.

Does the Coordinalo — Service Business Operations MCP server require authentication?

No. We connected to Coordinalo — Service Business Operations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Coordinalo — Service Business Operations MCP server still maintained?

Coordinalo — Service Business Operations is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.