Coordinalo — Service Business Operations
REMOTE · COORDINALO.COM · SCANNED AUG 3
Scheduling, availability, clients, billing and CRM for appointment-based services.
Available components
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 →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 112 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 12998 tokens (~116/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · coordinalo.com
claude mcp add --transport http com-coordinalo-mcp-server https://coordinalo.com/api/mcp
[mcp_servers.com-coordinalo-mcp-server] url = "https://coordinalo.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-coordinalo-mcp-server": {
"type": "remote",
"url": "https://coordinalo.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-coordinalo-mcp-server --url https://coordinalo.com/api/mcp --transport streamable-http
mcp_servers:
com-coordinalo-mcp-server:
url: "https://coordinalo.com/api/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +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.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 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
- 26 Jul 26 58
First indexed and scored.
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 3 Aug 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 | 5 Jul 2026 | 3 Oct 2026 | RSA 2048 | SHA256-RSA | 5619be711c8d685b9d102b60e5a04df642b |
| 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 |
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 |
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 |
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.
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| booking_id | string | — | — |
| credential | string | — | — |
| orgSlug | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| confirm | boolean | yes | — |
| new_datetime | string | yes | — |
| orgSlug | string | yes | — |
| session_id | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | — |
| apiKey | string | — | — |
| commission | number | — | — |
| confirm | boolean | — | — |
| orgSlug | string | yes | — |
| price | number | — | — |
| providerId | string | yes | — |
| serviceId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| category | string | — | — |
| currency | string | — | — |
| description | string | — | — |
| duration | integer | yes | — |
| isDiscoverable | boolean | — | — |
| modalidad | string | — | — |
| name | string | yes | — |
| orgSlug | string | yes | — |
| price | number | yes | — |
| providerId | string | — | — |
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| activeOnly | boolean | — | — |
| apiKey | string | — | — |
| category | string | — | — |
| discoverableOnly | boolean | — | — |
| orgSlug | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| category | string | — | — |
| currency | string | — | — |
| description | string | — | — |
| duration | integer | — | — |
| isActive | boolean | — | — |
| isDiscoverable | boolean | — | — |
| modalidad | string | — | — |
| name | string | — | — |
| orgSlug | string | yes | — |
| price | number | — | — |
| publicDescription | string | — | — |
| qualityCapture | — | — | — |
| serviceId | string | yes | — |
| 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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| includeRestricted | boolean | — | — |
| orgSlug | string | yes | — |
| sessionId | string | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| dataSensitivity | string | — | — |
| evolution | — | — | — |
| isPrivate | boolean | — | — |
| nextSessionPlan | — | — | — |
| orgSlug | string | yes | — |
| sessionId | string | yes | — |
| treatmentPerformed | — | — | — |
| type | — | — | — |
No output schema declared.
No examples provided.
settings_get ~174
Get organization settings by chapter or specific keys. Chapters: basics (name, description, vertical, timezone, currency), availability (weekday hours, saturday, assisted assignment), communication (channels, phone required), finances (provider payment type, client payment timing, max balance), policies (no-show strikes, blocking duration, no-show charge, auto-apply), reminders (session 24h, booking, payment, confirmation timeout), client_data (required fields: lastName, rut, email, phone, direccion). Use chapter param for a group, or keys param for specific settings (comma-separated, e.g. "policies.noShowMaxStrikes,finances.clientPaymentTiming").
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| chapter | string | — | — |
| keys | string | — | — |
| orgSlug | string | yes | — |
No output schema declared.
No examples provided.
settings_update ~118
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 writing — if any key fails validation, no changes are applied. Returns the full updated settings for the affected chapters. See settings_get for available keys and valid values.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| orgSlug | string | yes | — |
| settings | object | yes | — |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| orgSlug | string | yes | — |
| planId | string | yes | — |
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).
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | — | — |
| clientId | string | — | — |
| limit | integer | — | — |
| orgSlug | string | yes | — |
| page | integer | — | — |
| proveedorId | string | — | — |
| status | string | — | — |
No output schema declared.
No examples provided.