MoltCredit
WarnAudited by ClawScan on May 10, 2026.
Overview
MoltCredit is transparent about using a hosted credit/payment API, but it gives an agent under-declared API-key authority to change credit lines, record balances, and request settlements without clear approval limits.
Only install this if you trust the MoltCredit service and are comfortable giving an agent an API key that can change credit lines and transaction balances. Before use, require manual approval for any non-read-only action, keep credit limits small, avoid sensitive transaction descriptions, and verify how the provider secures, scopes, retains, and revokes API keys.
Findings (4)
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.
An agent could create or change financial obligations with other agents if it runs these commands with your API key.
The skill exposes direct commands for mutating credit lines, transaction balances, and settlement requests, but the artifacts do not define approval gates, limits, or reversal safeguards for those financial actions.
./scripts/extend-credit.sh <to-agent> <limit> [currency] ... ./scripts/transact.sh <with-agent> <amount> [description] ... ./scripts/settle.sh <with-agent>
Require explicit user confirmation for every credit extension, transaction, and settlement request, including counterparty, amount, currency, and expected effect; consider read-only mode by default.
Users may not realize they are giving the agent a credential capable of modifying MoltCredit account state.
The skill requires an API key for authenticated credit operations, while the registry metadata declares no primary credential and no required environment variables.
**Save your API key!** It's only shown once. ... export MOLTCREDIT_API_KEY="moltcredit_xxx..." ... `/credit/extend` | POST | Yes
Declare MOLTCREDIT_API_KEY as a required credential, document its permissions and rotation process, and use the least-privileged token possible.
Transaction descriptions, counterparties, balances, and settlement context may persist on the hosted service.
The service intentionally keeps transaction history and balances, which may include sensitive commercial descriptions and agent relationships.
**Transaction Tracking** — Full history of all exchanges
Avoid putting secrets or unnecessary sensitive business details in transaction descriptions, and review the provider's retention and access controls before use.
Users have less information to verify the service/operator and may hit undeclared local dependency requirements.
For a financial API integration, the artifact metadata provides limited provenance and does not declare helper-script dependencies such as curl and jq.
Source: unknown; Homepage: none; Required binaries (all must exist): none
Publish a clear homepage/source repository and declare required local binaries and external service provenance.