com.coordinalo/mcp-server

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  warn25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  tool "lifecycle_history" description: bare 'IMPORTANT:' prose in a description (tag form is high-confidence; prose is warn).

• Supply chain

  pass25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  repository linkage verified

• Credential hygiene

  fail15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  tool "dunning_get_config" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "admin_list_providers" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "admin_create_service" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "admin_set_availability" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "admin_toggle_discoverable" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "availability_get_slots" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "availability_get_provider_schedule" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_create" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_cancel" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_reschedule" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_update_status" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_create_recurring" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_list_requests" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "booking_resolve_request" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "client_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "client_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "client_create" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "client_update" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "service_create" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "service_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "service_update" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "service_assign_provider" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "provider_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "provider_create" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "provider_update" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "provider_get_stats" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_list_cobros" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_get_cobro" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_register_payment" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_client_balance" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_list_payments" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_list_ventas" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_create_venta" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_create_cobro" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_aging" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_list_confirmations" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_send_confirmations" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_list_gastos" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "finance_list_invoices" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_get_preferences" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_update_preferences" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_list_campaigns" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_get_campaign" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_send_message" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_render_message" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_create_campaign" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_send_campaign" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "comms_list_audiences" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "org_summary" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "report_occupancy" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "report_revenue" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "report_sc_summary" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "report_no_shows" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "report_deuda_real" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "report_dashboard" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "agendas_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "agendas_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "agendas_create" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "agendas_update" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "agendas_delete" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "disputes_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "delivery_confirmations_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "members_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "members_invite" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "org_update" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "email_domain_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "email_domain_register" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "email_domain_verify" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "email_domain_delete" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_preview_cliente" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_crear_cliente" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_listar_clientes" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_eliminar_cliente" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_evaluar_org" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_cerrar_org" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_distribuir_utilidades" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cierre_listar_utilidades" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "payroll_list_records" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "payroll_get_summary" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "nps_get_summary" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "settings_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "settings_update" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "reminders_get_config" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "reminders_update_config" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portal_session_confirm" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portal_session_cancel" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portal_propose_reschedule" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portal_report_session" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portal_confirm_delivery" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "portal_cancel_reschedule_request" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "session_note_upsert" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "session_note_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "resources_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "treatment_plans_list" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "treatment_plans_get" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lifecycle_get_state" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lifecycle_history" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lifecycle_transition" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "scheduling_confirm" has a secret-shaped input parameter "credential" — secrets must never be tool parameters (the model would supply/handle the credential). tool "scheduling_confirm" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "scheduling_cancel" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "scheduling_reschedule" has a secret-shaped input parameter "apiKey" — secrets must never be tool parameters (the model would supply/handle the credential). tool "public_booking_confirm" has a secret-shaped input parameter "confirmationToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "public_booking_get" has a secret-shaped input parameter "bookingToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "public_booking_cancel" has a secret-shaped input parameter "bookingToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "public_booking_reschedule" has a secret-shaped input parameter "bookingToken" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  unscannable15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No source files, package.json, or pyproject were fetched; cannot infer capability scope.

• Version behavior

  unscannable10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  no prior version to diff (first sight of com.coordinalo/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

• Transport config

  fail10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class)