LeashIndex Get the report

Index / crm

io.github.oktopeak/lawmatics-mcp

io-github-oktopeak-lawmatics-mcp declares 37 capabilities across 37 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.

69/100 exposureElevated

Manifest recorded 2026-11-03 from tools/list answered by the npm package @oktopeak/lawmatics-mcp@1.0.0 (published to npm as @oktopeak/lawmatics-mcp, listed in the official MCP registry as io.github.oktopeak/lawmatics-mcp 1.0.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 37 tools

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

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

37 of 37 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 · 11 of 37 tools

11 tools can modify data and declare no limit.

low · uncapped-read · 26 of 37 tools

26 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
list-mattersread inferred
get-matterread inferred
find-matterread inferred
create-matterwrite inferred
update-matterwrite inferred
list-contactsread inferred
get-contactread inferred
find-contactread inferred
create-contactwrite inferred
update-contactwrite inferred
list-companiesread inferred
get-companyread inferred
find-companyread inferred
list-pipelinesread inferred
list-stagesread inferred
list-practice-areasread inferred
list-sourcesread inferred
list-sub-statusesread inferred
list-usersread inferred
get-current-userread inferred
list-tasksread inferred
create-taskwrite inferred
update-taskwrite inferred
list-eventsread inferred
create-eventwrite inferred
list-notesread inferred
create-notewrite inferred
list-activitiesread inferred
list-tagsread inferred
attach-tagswrite assumed
detach-tagswrite assumed
list-custom-fieldsread inferred
list-formsread inferred
get-formread inferred
get-form-entriesread inferred
submit-formwrite assumed
list-invoicesread inferred
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.