LeashIndex Get the report

Index / devtools

UVCS MCP

io-github-proanima-uvcs-mcp declares 45 capabilities across 45 tools, with 2 critical issues.

83/100 exposureHigh exposure

Manifest recorded 2026-10-26 from tools/list answered by the npm package @proanima/uvcs-mcp@1.4.1 (published to npm as @proanima/uvcs-mcp, listed in the official MCP registry as io.github.ProAnima/uvcs-mcp 1.4.1), 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 45 tools

45 of 45 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.

critical · irreversible-uncapped · 4 of 45 tools

4 tools are classified as irreversible and declare no limit.

high · no-expiry · All 45 tools

45 of 45 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 45 tools

45 of 45 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 45 tools

6 tools can modify data and declare no limit.

low · uncapped-read · 35 of 45 tools

35 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
uvcs_doctorread declared
uvcs_policy_statusread declared
uvcs_setup_statusread declared
uvcs_workspace_statusread declared
uvcs_pending_changesread declared
uvcs_branch_inforead declared
uvcs_locksread declared
uvcs_unity_meta_diagnosticsread declared
uvcs_style_rulesread declared
uvcs_style_setup_checkread declared
uvcs_style_init_prepareread declared
uvcs_style_init_confirmwrite assumed
uvcs_name_previewread declared
uvcs_release_planread declared
uvcs_diff_fileread declared
uvcs_changeset_diffread declared
uvcs_revision_diffread declared
uvcs_file_historyread declared
uvcs_annotateread declared
uvcs_branch_listread declared
uvcs_label_listread declared
uvcs_merge_previewread declared
uvcs_update_workspace_prepareread declared
uvcs_update_workspace_confirmdestructive declared
uvcs_changeset_analyticsread declared
uvcs_cleanup_candidatesread declared
uvcs_branch_safety_reportread declared
uvcs_add_prepareread declared
uvcs_add_confirmwrite inferred
uvcs_undo_prepareread declared
uvcs_undo_confirmdestructive declared
uvcs_branch_create_prepareread declared
uvcs_branch_create_confirmwrite inferred
uvcs_label_create_prepareread declared
uvcs_label_create_confirmwrite inferred
uvcs_switch_workspace_prepareread declared
uvcs_switch_workspace_confirmdestructive declared
uvcs_merge_prepareread declared
uvcs_merge_confirmdestructive declared
uvcs_checkout_prepareread declared
uvcs_checkout_confirmread inferred
uvcs_release_checkout_prepareread declared
uvcs_release_checkout_confirmwrite assumed
uvcs_checkin_prepareread declared
uvcs_checkin_confirmwrite assumed
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.