QuickBooks
AdvisoryAudited by Static analysis on May 3, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If misused, the skill could create, modify, or delete accounting records such as invoices, payments, bills, or customer records.
The skill can perform high-impact financial write actions, but it clearly discloses this and instructs the agent to require specific approval before changes.
This integration can mutate accounting records — approve only specific write actions after checking the exact endpoint, account, resource ID, amounts, and consequence.
Use read-only requests first, verify the exact QuickBooks company and record IDs, and approve only specific write actions you understand.
Anyone or any agent workflow with the Maton API key may be able to access the connected QuickBooks resources permitted by the OAuth connection.
The skill requires a bearer API key and delegated QuickBooks OAuth access, which is expected for the integration but grants access to financial account data and actions.
All requests require the Maton API key in the Authorization header: Authorization: Bearer $MATON_API_KEY
Use a least-privileged QuickBooks account, protect the Maton API key, avoid sharing logs containing headers, and revoke unused connections promptly.
Sensitive financial data may transit through Maton's API gateway as part of normal operation.
QuickBooks requests and responses pass through the Maton gateway. This is disclosed and purpose-aligned, but users should understand the third-party data path.
The gateway proxies requests to `quickbooks.api.intuit.com` and the `:realmId` placeholder is automatically replaced with your company's realm ID from connection config.
Install only if you trust the Maton service for QuickBooks data, review its privacy/security posture, and use the `Maton-Connection` header to avoid sending actions to the wrong company.
It may be harder to independently verify the publisher, implementation, or support channel before connecting accounting data.
The registry does not provide source or homepage provenance. There is no code package to install, so this is not a direct execution risk, but it matters for a financial integration.
Source: unknown; Homepage: none
Verify the owner and Maton service out-of-band before connecting a real QuickBooks company, especially for production accounting data.