LeashIndex Get the report

Index / payments

io.github.codespar/mcp-omie

io-github-codespar-mcp-omie declares 30 capabilities across 30 tools, with 3 critical issues.

77/100 exposureHigh exposure

Manifest recorded 2026-10-15 from tools/list answered by the npm package @codespar/mcp-omie@0.2.2 (published to npm as @codespar/mcp-omie, listed in the official MCP registry as io.github.codespar/mcp-omie 0.2.2), 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 30 tools

30 of 30 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 · 2 of 30 tools

2 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 2 of 30 tools

2 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 30 tools

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

30 of 30 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 · 10 of 30 tools

10 tools can modify data and declare no limit.

low · uncapped-read · 18 of 30 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
list_customersread inferred
create_customerwrite inferred
list_productsread inferred
create_productwrite inferred
create_orderwrite inferred
list_ordersread inferred
list_invoicesread inferred
get_financialread inferred
create_invoicewrite inferred
get_company_inforead inferred
create_service_orderwrite inferred
list_service_ordersread inferred
create_purchase_orderpay inferred
list_purchase_ordersread inferred
get_bank_accountsread inferred
create_account_payablewrite inferred
list_accounts_payableread inferred
pay_account_payablepay inferred
list_dreread inferred
get_bank_statementread inferred
list_categoriesread inferred
list_departmentsread inferred
list_projectsread inferred
create_cash_entrywrite inferred
list_financial_movementsread inferred
create_stock_adjustmentwrite inferred
get_stock_positionread inferred
update_sales_orderwrite inferred
get_sales_orderread inferred
invoice_sales_orderwrite 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.