MCP SERVERDiscover a service provider, book a session, prove it was delivered, and settle it — through one open protocol.
LABSCO SUMMARY
Booking is the easy half. What this adds is the rest of the chain — a contract agreed in advance, check-in and check-out to establish the session happened, evidence recorded against the contract's requirements, then documentation and settlement — so an agent can verify a service was delivered rather than merely scheduled.
The reference MCP server for Servicialo, an open protocol for professional services. It covers the whole chain: finding a compatible organisation, checking availability, booking and confirming, moving the session through its lifecycle, recording delivery evidence, then documenting and charging for it.
The npm package @servicialo/mcp-server. Discovery, the public service catalogue and availability checks need no authentication; booking, delivery and payment act against a specific organisation's node. Know what this repository is before you plan around it: the protocol and its reference implementation, not a booking platform — a service business needs a protocol-compatible platform, and Coordinalo is the reference one. Tool descriptions from the booking stage onward are written in Spanish.
One command plus a key — npx -y @servicialo/mcp-server, then supply credentials
USE CASES
Search by vertical and country, resolve the organisation's endpoints, and check its trust score first.
The public catalogue with prices and durations, and free time slots — neither needs authentication.
Resolve or create the client, create the session, then move it to confirmed with both parties notified.
Check in, check out, and record evidence against what the contract required.
Generate the service record, raise the sale against it, and read back the payment status.
Exception flows that apply the organisation's own policy, with the lifecycle state readable at each step.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
a2a_get_agent_cardGet the A2A (Agent-to-Agent) Agent Card for an organization, enabling inter-agent discovery. Use this when your agent needs to communicate with another agent managing this organization — the card declares supported capabilities, endpoints, and authentication requirements. Do NOT use for human-facing discovery (use registry.get_organization) or service listing (use services.list). Returns a JSON-LD Agent Card following the A2A v0.3 specification.
clients_get_or_create[Fase 3 — Comprometer] Busca un cliente por email o teléfono. Si existe, retorna sus datos y resumen de historial. Si no existe, lo crea con los datos proporcionados. Una sola llamada para resolver la identidad del cliente antes de agendar.
contract_get[Fase 2 — Entender] Obtiene el contrato de servicio pre-acordado. Define las reglas bajo las que opera el servicio: evidencia requerida, políticas de cancelación, inasistencia y arbitraje. DEBE llamarse antes de cualquier acción en Fase 3+.
delivery_checkin[Fase 5 — Verificar entrega] Registra el check-in del proveedor o cliente, moviendo la sesión a "En Curso". Captura timestamp y ubicación GPS como evidencia de inicio de servicio.
delivery_checkout[Fase 5 — Verificar entrega] Registra el check-out al finalizar el servicio, moviendo la sesión a "Entregado". Captura timestamp y ubicación GPS. La duración real se calcula automáticamente.
delivery_record_evidence[Fase 5 — Verificar entrega] Registra evidencia de entrega del servicio según los requisitos del contrato. Tipos: GPS, firma, foto, documento, duración, notas. Consultar contract.get para conocer la evidencia requerida por vertical.
docs_quickstartGet the complete 5-step onboarding guide as structured JSON data. Use this when helping a new organization join the Servicialo network — covers installation, signup, credentials, MCP client config, and publishing. Do NOT use for searching services (use registry.search) or checking availability (use scheduling.check_availability). Returns step-by-step instructions, config templates, and links. No parameters required.
documentation_create[Fase 6 — Cerrar] Genera el registro/documentación del servicio entregado (nota clínica, reporte de inspección, acta de clase, etc.). Mueve la sesión a "Documentado".
lifecycle_get_state[Fase 4 — Ciclo de vida] Obtiene el estado actual de una sesión en el ciclo de vida Servicialo, incluyendo las transiciones disponibles desde el estado actual y el historial de transiciones pasadas.
lifecycle_transition[Fase 4 — Ciclo de vida] Ejecuta una transición de estado en el ciclo de vida de una sesión. Transiciones válidas: requested→scheduled, scheduled→confirmed, confirmed→in_progress, in_progress→delivered, delivered→documented, documented→charged, charged→verified, any→cancelled. Cada transición puede requerir evidencia según el contrato del servicio.
market_get_benchmarkGet the bucket distribution for a (event_type, vertical, region) segment over a time window. Returns the share of each bucketed value within the payload (e.g. for booking_created, the share of bookings in each lead_time_bucket). All values are categorical buckets — no raw prices, durations, or names are ever returned. If the segment has fewer than 5 distinct contributing organizations, returns { ok: false, reason: "insufficient_data", contributors }. Use market.list_segments first to know which segments will return data. Example: market.get_benchmark({ event_type: "payment_settled", vertical: "health", region: "CL" }) → distribution of price bands, payment methods, time-to-collect buckets.
market_list_segmentsList every (event_type, vertical, region) segment that has at least 5 distinct contributing organizations over the last 90 days — i.e. every benchmark that the protocol is allowed to publish without violating k-anonymity. Use this to discover what benchmarks exist before issuing market.get_benchmark. Filters are optional; passing none lists all available segments sorted by contributor count. Returns: array of { event_type, vertical, region, sample_size, contributors, first_event, last_event }.
payments_create_sale[Fase 6 — Cerrar] Crea una venta (cargo) asociada a un servicio documentado. Mueve la sesión a "Cobrado". Debe llamarse después de documentation.create.
payments_get_status[Fase 6 — Cerrar] Consulta el estado de pago de una venta específica o el estado de cuenta de un cliente. Provee sale_id para una venta o client_id para el estado de cuenta completo.
payments_record_payment[Fase 6 — Cerrar] Registra un pago recibido contra una venta existente. El pago es independiente del ciclo de vida — billing.status transiciona de charged → invoiced → paid.
registry_get_organizationGet the full public profile of a specific organization: services offered, providers, and booking configuration. Use this after registry.search when you have an org_slug and need detailed info before booking. Do NOT use for searching across organizations (use registry.search). Returns service catalog with prices/durations, provider list, and booking policies.
registry_list_event_typesList the catalog of operational-telemetry event types defined by the Servicialo protocol. Static (changes via RFC), but exposed as a discovery call so agents can know what event names market.get_benchmark accepts and what bucketed fields each event carries — without having to read the JSON Schema. Returns: array of { name, description, payload_fields[] } plus a schema_url for the canonical reference.
registry_list_regionsList every country/region present in the Servicialo network. Combines countries declared by registered nodes with regions observed in operational telemetry over the last 30 days. Use this when an agent needs to know "where is this protocol active?" before issuing a region-scoped query. Returns: array of { code, org_count, event_count_30d } sorted by activity. Codes are ISO 3166-1 alpha-2.
registry_list_verticalsList every vertical present in the Servicialo network. Combines (a) verticals that registered nodes declare and (b) verticals observed in operational telemetry over the last 30 days. Use as the first call when an agent has no prior knowledge of the protocol taxonomy — before issuing market.get_benchmark, registry.search, or any other call that requires a vertical argument. Returns: array of { name, org_count, event_count_30d } sorted by activity. Test fixtures (verticals starting with _) are excluded.
registry_manifestGet the Servicialo server manifest: protocol version, server name, and available capabilities. Use this to verify server identity and protocol compatibility before interacting with tools. Do NOT use for organization discovery (use registry.search) or service details (use services.list). Returns static metadata about this MCP server instance, not about any specific organization.
registry_searchSearch for Servicialo-compatible organizations by vertical, location, and country. Use this as the primary discovery tool when a user needs a service (e.g., "find a physiotherapist in Santiago"). Do NOT use if you already have an org_slug (use registry.get_organization instead). Returns a ranked list of organizations with names, slugs, and service summaries.
resolve_lookupResolve an organization slug to its MCP/REST endpoints and trust level — the DNS of professional services. Use this when you know the org_slug and need its API endpoint before calling any other tool. Do NOT use for searching by vertical or location (use resolve.search or registry.search instead). Returns: endpoint URLs, trust score (0-100), trust level, and last heartbeat timestamp.
resolve_registerRegistra una nueva organización en el resolver Servicialo con un orgSlug único global. Requiere al menos un endpoint (MCP o REST). El slug es portable: si la org migra de plataforma, conserva su slug y solo actualiza los endpoints.
resolve_searchSearch the global Servicialo resolver for registered organizations by country and vertical. Use this for broad discovery when you need to find all organizations in a country/vertical (e.g., "what physiotherapy clinics exist in Chile?"). Do NOT use if you already have an org_slug (use resolve.lookup instead). Unlike registry.search, this queries the DNS-level resolver and returns endpoint URLs + trust levels.
resolve_update_endpointActualiza los endpoints de una organización en el resolver. Esta es la operación de portabilidad: si la org migra de Coordinalo a otro CRM, actualiza sus URLs aquí y todos los agentes la encuentran automáticamente en la nueva ubicación.
resource_create[Gestión de Recursos] Crea un nuevo recurso físico para una organización. El recurso se crea activo por defecto. Valida todos los campos según el schema Resource (Dimensión 3.5b del protocolo).
resource_delete[Gestión de Recursos] Desactiva un recurso físico (soft delete — establece is_active = false). El recurso nunca se elimina físicamente; solo se marca como inactivo y deja de aparecer en búsquedas y disponibilidad.
resource_get[Gestión de Recursos] Obtiene los detalles completos de un recurso físico, incluyendo sus bloques de disponibilidad recurrente (ResourceAvailability).
resource_get_availability[Gestión de Recursos] Consulta la disponibilidad de un recurso físico en un rango de fechas. Retorna los slots disponibles del recurso independiente de cualquier servicio — es una consulta pura al calendario del recurso. Útil para planificación de capacidad y verificación de conflictos.
resource_list[Gestión de Recursos] Lista los recursos físicos de una organización (salas, boxes, sillas, equipamiento). Soporta filtros opcionales por tipo y estado activo.
resource_update[Gestión de Recursos] Actualiza parcialmente un recurso físico existente (patch semantics). Solo se modifican los campos proporcionados; los demás permanecen sin cambio.
scheduling_book[Fase 3 — Comprometer] Agenda una nueva sesión para un cliente con un proveedor. Crea la sesión en estado "Solicitado". Si el servicio tiene location.resource_id, el recurso físico se reserva junto con la sesión (scheduler de 3 variables: profesional ∧ cliente ∧ recurso). Requiere haber llamado contract.get antes para conocer las reglas del servicio.
scheduling_cancel[Fase 4 — Ciclo de vida] Cancela una sesión existente. Flujo de excepción: aplica la política de cancelación definida en el contrato (reembolso total fuera de ventana de penalidad, parcial/nulo dentro). Llama contract.get primero para conocer la política.
scheduling_check_availabilityQuery available time slots for booking at an organization. No authentication required. Use this after services.list when you know the org and need to find open slots before booking. Checks 3-way availability: provider schedule AND client conflicts AND physical resource (room/equipment). Do NOT use for searching organizations (use registry.search) or listing services (use services.list). Returns available slots grouped by date, each with start time, end time, provider, and resource.
scheduling_confirm[Fase 3 — Comprometer] Confirma una sesión agendada, moviéndola a estado "Confirmado". Ambas partes (proveedor y cliente) deben confirmar antes de que el servicio pueda iniciar.
scheduling_reschedule[Fase 4 — Ciclo de vida] Reagenda una sesión existente a una nueva fecha/hora. Flujo de excepción: la sesión vuelve a estado "Scheduled" con nuevo horario. La política de reagendamiento del contrato puede aplicar cargos.
service_get[Fase 2 — Entender] Obtiene las 8 dimensiones de un servicio: qué se entrega, quién lo entrega, quién lo recibe (con pagador separado), cuándo, dónde, ciclo de vida, evidencia requerida y cobro. Llama esto para entender completamente un servicio antes de comprometerse.
services_listList the public service catalog of an organization: names, prices, durations, and modalities. Use this after registry.search to see what services an organization offers before checking availability. Do NOT use for organization discovery (use registry.search) or checking time slots (use scheduling.check_availability). Returns active, publicly bookable services only — internal or draft services are excluded.
telemetry_heartbeatEnvía un heartbeat al resolver Servicialo indicando que el nodo sigue activo. Opcionalmente incluye métricas de uso. Los nodos sin heartbeat por 7+ días se marcan inactivos.
trust_get_scoreGet the trust score of an organization from the Servicialo resolver. Use this to evaluate reliability before booking — returns score (0-100), trust level (unverified → declared → vouched → verified), and last activity timestamp. Do NOT use this to find organizations (use resolve.search). Trust accumulates passively from verified service history; it cannot be purchased or self-declared.
BEFORE YOU INSTALL
40 tools when we connected.
CONTEXT COST
Rated by the size of the 40 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"servicialo": {
"command": "npx",
"args": [
"-y",
"@servicialo/mcp-server"
],
"env": {
"SERVICIALO_API_KEY": "<YOUR_SERVICIALO_API_KEY>",
"SERVICIALO_ORG_ID": "<YOUR_SERVICIALO_ORG_ID>"
}
}
}
}npx -y @servicialo/mcp-serverMCP servers
douglac
fmepm
corpollc