Ekwo OS MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Ekwo accounting operations under installation row-level security: Do invoice posting and payment matching preserve the signed-in user's database policy and audit scope?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

AI-assisted bookkeeping on the user's own Postgres/Supabase under row-level security.

What we know

MCP server for Ekwo OS. It can read and write accounting books, raise/post invoices, match payments, register bank accounts and prepare VAT/FEC outputs while acting as the authenticated user under RLS; the hosted MCP holds no books itself.

Maintenance / activity evidence

@ekwo-ai/mcp 0.10.0 published 2026-10-02T08:39:29.943Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
User-equivalent bookkeeping authority constrained by database RLS. Writes: Create/post invoices; Register bank account; Record/match payments; Import opening balances; Close accounting year.
OAuth/user session/access token.
Sensitive access: Accounting records, Customer/vendor data, Bank/payment records, Tax data

Real accounting writes can affect books and filings; RLS and immutable-posting constraints reduce but do not remove risk.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do invoice posting and payment matching preserve the signed-in user's database policy and audit scope?

The bounded review of the publisher's documented Ekwo accounting operations under installation row-level security and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Real accounting writes can affect books and filings; RLS and immutable-posting constraints reduce but do not remove risk.
User-equivalent bookkeeping authority constrained by database RLS.
OAuth/user session/access token.
Hosted server connects to the user's named instance and does not retain the books; accounting data stays in the user's Postgres account except normal request processing.
Reviewed write actions: Create/post invoices; Register bank account; Record/match payments; Import opening balances; Close accounting year
Sensitive access: Accounting records, Customer/vendor data, Bank/payment records, Tax data
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Accounting writes are financially consequential.
The server cannot bypass RLS and intentionally does not use service_role.
Nothing can unpost an entry through this server.
Country-pack support varies by jurisdiction.

Original activity observations

@ekwo-ai/mcp 0.10.0 published 2026-10-02T08:39:29.943Z

Technical identity

npm/@ekwo-ai/mcp

Exact implementation source: https://www.npmjs.com/package/@ekwo-ai/mcp ↗
Reviewed resource type: MCP Server
Repository identity: ekwo-ai/ekwo
Package identity: npm:@ekwo-ai/mcp
Service endpoint: https://mcp.ekwo.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@ekwo-ai/mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
ekwo.ai/docs/mcp/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
ekwo.ai/docs/overview/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
ekwo.ai/docs/agents/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Recommended hosted https://mcp.ekwo.ai/mcp with OAuth; local stdio needs user context (EKWO_ACCESS_TOKEN or appropriately scoped credentials); direct DB mode needs EKWO_ACT_AS_USER_ID for RLS context.
publisher install or stdio launch · Publisher instructions
npx -y @ekwo-ai/mcp@latest
Configure / authenticate
MCP100 setup guide
Publisher `npx -y @ekwo-ai/mcp@latest` is stdio. OAuth remote setup is distinct; EKWO_ACCESS_TOKEN is an alternative credential.
Previously reviewed client configuration / prerequisites: Do not treat both as consecutive mandatory installation steps. Ledger/invoice writes should never be a connectivity probe.
Check connection
Suggested check
Inspect client tools and use read-only account/status listing, not invoice posting.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `ekwo-ai-mcp`, run `claude mcp remove ekwo-ai-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove ekwo-ai-mcp

Official Documentation & Sources

What it does

MCP server for Ekwo OS. It can read and write accounting books, raise/post invoices, match payments, register bank accounts and prepare VAT/FEC outputs while acting as the authenticated user under RLS; the hosted MCP holds no books itself.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing, Legal & Compliance
Best fit: AI-assisted bookkeeping on the user's own Postgres/Supabase under row-level security.

Representative uses

Read ledger/chart/accounts
Create and post invoices
Record/match payments
Prepare VAT return
Generate French FEC/accounting reports

Limitations

Accounting writes are financially consequential.
The server cannot bypass RLS and intentionally does not use service_role.
Nothing can unpost an entry through this server.
Country-pack support varies by jurisdiction.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth/user session/access token.
Permissions: User-equivalent bookkeeping authority constrained by database RLS.
Data handling: Hosted server connects to the user's named instance and does not retain the books; accounting data stays in the user's Postgres account except normal request processing.
Cost: self_hosted_plus_service
Risk and cautions: Real accounting writes can affect books and filings; RLS and immutable-posting constraints reduce but do not remove risk.

Access scope and cautions

Write actions: Create/post invoices Register bank account Record/match payments Import opening balances Close accounting year
Sensitive access: Accounting records Customer/vendor data Bank/payment records Tax data
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Read ledger/chart/accounts; Create and post invoices; Record/match payments; Prepare VAT return; Generate French FEC/accounting reports.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @ekwo-ai/mcp@latest. Recorded endpoint: https://mcp.ekwo.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: Ekwo/Supabase instance and user auth variables for local mode; exact names are documented in package README. No configuration values are supplied here. Prerequisites: Ekwo OS instance/Supabase project; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Hosted mode uses OAuth with `books` scope and browser approval; local mode signs in as user or accepts user access token.

Can it modify data or perform write operations?

Documented write actions include: Create/post invoices; Register bank account; Record/match payments; Import opening balances; Close accounting year. Recorded permission boundary: User-equivalent bookkeeping authority constrained by database RLS.

What data-handling boundary should I consider?

Hosted server connects to the user's named instance and does not retain the books; accounting data stays in the user's Postgres account except normal request processing. Recorded sensitive-access context: Accounting records; Customer/vendor data; Bank/payment records; Tax data.

What limitations and risks should I check before use?

Real accounting writes can affect books and filings; RLS and immutable-posting constraints reduce but do not remove risk. Accounting writes are financially consequential. The server cannot bypass RLS and intentionally does not use service_role. Nothing can unpost an entry through this server. Country-pack support varies by jurisdiction. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.