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.

io.github.danioni/servicialo

NPM · @SERVICIALO/MCP-SERVER · SCANNED SEP 20

Open protocol for professional service delivery via AI agents

0 this week 84 Trust /100

Deprecated

This server is marked deprecated in the MCP registry.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 27 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1940 tokens (~97/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 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 io.github.danioni/servicialo MCP server?

io.github.danioni/servicialo runs locally as an npm package, launched with npx -y @servicialo/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @servicialo/mcp-server

# add to Claude Code
claude mcp add danioni-servicialo -- npx -y @servicialo/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "danioni-servicialo": {
      "command": "npx",
      "args": [
        "-y",
        "@servicialo/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "danioni-servicialo": {
      "command": "npx",
      "args": [
        "-y",
        "@servicialo/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add danioni-servicialo -- npx -y @servicialo/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "danioni-servicialo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@servicialo/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add danioni-servicialo --command npx --arg -y --arg @servicialo/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  danioni-servicialo:
    command: "npx"
    args: ["-y", "@servicialo/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "danioni-servicialo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@servicialo/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add danioni-servicialo -t stdio -c npx -a -y @servicialo/mcp-server
// mcp.json
{
  "mcpServers": {
    "danioni-servicialo": {
      "command": "npx",
      "args": [
        "-y",
        "@servicialo/mcp-server"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 −3
    • Stability: pass → 0.80 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 20 Sept 2026 · Analysed npm/@servicialo/mcp-server@0.5.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,940 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
clients.get_or_create ~146

[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.

NameTypeReqDescription
actorobjectyesQuién realiza la acción
emailstringEmail del cliente (buscará primero por email)
last_namestringApellido — requerido solo si el cliente no existe
namestringNombre — requerido solo si el cliente no existe
phonestringTeléfono del cliente (buscará si no se provee email)

No output schema declared.

No examples provided.

contract.get ~91

[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+.

NameTypeReqDescription
org_idstringyesID de la organización
service_idstringyesID del servicio

No output schema declared.

No examples provided.

delivery.checkin ~110

[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.

NameTypeReqDescription
actorobjectyesQuién hace check-in (provider o client)
locationobjectUbicación GPS al momento del check-in
session_idstringyesID de la sesión
timestampstringISO datetime del check-in (default: ahora)

No output schema declared.

No examples provided.

delivery.checkout ~110

[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.

NameTypeReqDescription
actorobjectyesQuién hace check-out (provider o client)
locationobjectUbicación GPS al momento del check-out
session_idstringyesID de la sesión
timestampstringISO datetime del check-out (default: ahora)

No output schema declared.

No examples provided.

delivery.record_evidence ~112

[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.

NameTypeReqDescription
actorobjectyesQuién registra la evidencia
dataobjectyesPayload de la evidencia (estructura varía por tipo)
evidence_typestringyesTipo de evidencia
session_idstringyesID de la sesión

No output schema declared.

No examples provided.

documentation.create ~111

[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".

NameTypeReqDescription
actorobjectyesQuién genera la documentación (típicamente el proveedor)
contentstringyesContenido del registro/documentación
session_idstringyesID de la sesión
template_idstringID de plantilla de documentación (si aplica)

No output schema declared.

No examples provided.

lifecycle.get_state ~67

[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.

NameTypeReqDescription
session_idstringyesID de la sesión

No output schema declared.

No examples provided.

lifecycle.transition ~160

[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.

NameTypeReqDescription
actorobjectyesQuién ejecuta la transición
evidenceobjectEvidencia requerida por el contrato para esta transición
reasonstringMotivo de la transición (requerido para cancelled)
session_idstringyesID de la sesión
to_statestringyesEstado destino de la transición

No output schema declared.

No examples provided.

payments.create_sale ~106

[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.

NameTypeReqDescription
client_idstringyesID del cliente
provider_idstringyesID del proveedor
quantitynumberCantidad de sesiones
service_idstringyesID del servicio
unit_pricenumberyesPrecio unitario

No output schema declared.

No examples provided.

payments.get_status ~88

[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.

NameTypeReqDescription
client_idstringID del cliente (para consultar estado de cuenta)
sale_idstringID de la venta (para consultar una venta específica)

No output schema declared.

No examples provided.

payments.record_payment ~97

[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.

NameTypeReqDescription
amountnumberyesMonto cobrado
methodstringyesMétodo de pago
referencestringReferencia o número de transacción
venta_idstringyesID de la venta

No output schema declared.

No examples provided.

registry.get_organization ~48

Obtiene el detalle público de una organización: servicios, profesionales y configuración de booking

NameTypeReqDescription
org_slugstringyesSlug de la organización (ej: clinica-dental-sur)

No output schema declared.

No examples provided.

registry.search ~68

Busca organizaciones Servicialo-compatible por vertical, ubicación u otros criterios

NameTypeReqDescription
limitnumberCantidad máxima de resultados
locationstringCiudad o comuna para filtrar
verticalstringyesVertical del servicio (ej: kinesiologia, psicologia, dental)

No output schema declared.

No examples provided.

scheduling.book ~114

[Fase 3 — Comprometer] Agenda una nueva sesión para un cliente con un proveedor. Crea la sesión en estado "Solicitado". Requiere haber llamado contract.get antes para conocer las reglas del servicio.

NameTypeReqDescription
actorobjectyesQuién realiza la acción
client_idstringyesID del cliente
provider_idstringyesID del proveedor
service_idstringyesID del servicio
starts_atstringyesFecha y hora de inicio (ISO datetime)

No output schema declared.

No examples provided.

scheduling.cancel ~105

[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.

NameTypeReqDescription
actorobjectyesQuién realiza la acción
reasonstringMotivo de la cancelación
session_idstringyesID de la sesión a cancelar

No output schema declared.

No examples provided.

scheduling.check_availability ~107

Consulta horarios disponibles de una organización sin autenticación

NameTypeReqDescription
date_fromstringyesFecha inicio (ISO date, ej: 2025-03-01)
date_tostringyesFecha fin (ISO date, ej: 2025-03-07)
org_slugstringyesSlug de la organización
provider_idstringID del proveedor (opcional)
service_idstringID del servicio (opcional)

No output schema declared.

No examples provided.

scheduling.confirm ~83

[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.

NameTypeReqDescription
actorobjectyesQuién confirma (client, provider, organization o agent)
session_idstringyesID de la sesión a confirmar

No output schema declared.

No examples provided.

scheduling.reschedule ~103

[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.

NameTypeReqDescription
actorobjectyesQuién realiza la acción
new_datetimestringyesNueva fecha y hora (ISO datetime)
session_idstringyesID de la sesión a reagendar

No output schema declared.

No examples provided.

service.get ~83

[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.

NameTypeReqDescription
service_idstringyesID del servicio

No output schema declared.

No examples provided.

services.list ~31

Lista el catálogo público de servicios de una organización

NameTypeReqDescription
org_slugstringyesSlug de la organización

No output schema declared.

No examples provided.

Common questions

What is the io.github.danioni/servicialo MCP server?

io.github.danioni/servicialo is an MCP server listed in the public MCP registry as io.github.danioni/servicialo. Open protocol for professional service delivery via AI agents. This page covers its npm package (@servicialo/mcp-server).

Is the io.github.danioni/servicialo MCP server safe to use?

io.github.danioni/servicialo scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.danioni/servicialo MCP server expose?

io.github.danioni/servicialo exposes 20 tools: registry.search, registry.get_organization, scheduling.check_availability, services.list, service.get, and 15 more. Their descriptions and schemas cost roughly 1,940 tokens of context every time the server is loaded.

Is the io.github.danioni/servicialo MCP server still maintained?

io.github.danioni/servicialo is marked deprecated in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.danioni/servicialo MCP server under?

io.github.danioni/servicialo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.