LeashIndex Get the report

Index / crm

ConnectWise PSA

io-github-selic-mcp-connectwise-psa declares 24 capabilities across 24 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

51/100 exposureElevated

Manifest recorded 2026-11-04 from tools/list answered by the npm package mcp-connectwise-psa@0.4.0 (published to npm as mcp-connectwise-psa, listed in the official MCP registry as io.github.selic/mcp-connectwise-psa 0.4.0), run in an isolated container with no network access and placeholder credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 24 tools

24 of 24 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

high · no-expiry · All 24 tools

24 of 24 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 24 tools

24 of 24 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 6 of 24 tools

6 tools can modify data and declare no limit.

low · uncapped-read · 18 of 24 tools

18 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
cw_search_ticketsread declared
cw_my_ticketsread declared
cw_get_ticketread declared
cw_create_ticketwrite inferred
cw_update_ticketwrite inferred
cw_add_ticket_notewrite inferred
cw_list_boardsread declared
cw_get_boardread declared
cw_list_prioritiesread declared
cw_list_ticket_timeread declared
cw_list_ticket_tasksread declared
cw_create_time_entrywrite inferred
cw_update_time_entrywrite inferred
cw_list_my_timeread declared
cw_list_work_rolesread declared
cw_list_my_timesheetsread declared
cw_submit_timesheetwrite assumed
cw_search_companiesread declared
cw_get_companyread declared
cw_search_contactsread declared
cw_get_contactread declared
cw_list_company_sitesread declared
cw_list_configurationsread declared
cw_get_configurationread declared
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.