io.github.codespar/mcp-flow-cl
NPM · @CODESPAR/MCP-FLOW-CL · SCANNED AUG 4
MCP server for Flow.cl — Chilean PSP: hosted payment orders, Webpay, refunds, HMAC-signed API
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 919 tokens (~114/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @codespar/mcp-flow-cl
claude mcp add codespar-mcp-flow-cl -- npx -y @codespar/mcp-flow-cl
codex mcp add codespar-mcp-flow-cl -- npx -y @codespar/mcp-flow-cl
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"codespar-mcp-flow-cl": {
"type": "local",
"command": [
"npx",
"-y",
"@codespar/mcp-flow-cl"
],
"enabled": true
}
}
} openclaw mcp add codespar-mcp-flow-cl --command npx --arg -y --arg @codespar/mcp-flow-cl
mcp_servers:
codespar-mcp-flow-cl:
command: "npx"
args: ["-y", "@codespar/mcp-flow-cl"] {
"mcpServers": {
"codespar-mcp-flow-cl": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-flow-cl"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Aug 26 +4
- Stability: unverified → 0.27 ▲ functional
- 2 Aug 26 +40
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
- 1 Aug 26 +3
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- 31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Aug 2026 · Analysed npm/@codespar/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
create_payment ~238
Create a hosted payment order (POST /payment/create). Returns url + token + flowOrder; the customer pays at url + '?token=' + token. paymentMethod 9 offers every method Flow has enabled for the merchant (Webpay, ETpay bank transfer, cash, international cards).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to charge (integer for CLP) |
| commerceOrder | string | yes | Your unique order id |
| currency | string | — | Currency (CLP or UF). Default CLP |
| string | yes | Customer email | |
| optional | object | — | Optional JSON of extra fields echoed back in getStatus |
| paymentMethod | number | — | 1 Webpay, 3 all cards, 5 Onepay, 8 ETpay, 9 all enabled methods. Default 9 |
| subject | string | yes | Payment description shown to the customer |
| timeout | number | — | Seconds the payment order stays valid (omit = no expiry) |
| urlConfirmation | string | yes | Server-to-server confirmation callback URL (POST, receives token) |
| urlReturn | string | yes | URL the customer returns to after paying |
No output schema declared.
No examples provided.
create_payment_by_email ~190
Create a collection order Flow emails to the customer (POST /payment/createEmail). Same shape as create_payment but Flow delivers the payment link by email — no checkout redirect needed.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to charge (integer for CLP) |
| commerceOrder | string | yes | Your unique order id |
| currency | string | — | Currency (CLP or UF). Default CLP |
| string | yes | Customer email that receives the collection link | |
| forward_days_after | number | — | Resend the email N days after the first send |
| forward_times | number | — | How many times to resend |
| subject | string | yes | Payment description shown to the customer |
| timeout | number | — | Seconds the payment order stays valid |
| urlConfirmation | string | yes | Server-to-server confirmation callback URL |
| urlReturn | string | yes | URL the customer returns to after paying |
No output schema declared.
No examples provided.
create_refund ~134
Create a refund order (POST /refund/create). Refund a received payment fully or partially; Flow notifies urlCallBack when the refund resolves.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to refund |
| commerceTrxId | string | — | Original commerceOrder (alternative to flowTrxId) |
| flowTrxId | number | — | Original Flow order number (alternative to commerceTrxId) |
| receiverEmail | string | yes | Email of the refund receiver |
| refundCommerceOrder | string | yes | Your unique refund order id |
| urlCallBack | string | yes | Callback URL Flow notifies when the refund resolves |
No output schema declared.
No examples provided.
get_payment_status ~61
Get a payment order's status by Flow token (GET /payment/getStatus). status: 1 pending, 2 paid, 3 rejected, 4 canceled.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Flow payment token (from create_payment or the confirmation callback) |
No output schema declared.
No examples provided.
get_payment_status_by_commerce_id ~49
Get a payment order's status by your commerceOrder id (GET /payment/getStatusByCommerceId).
| Name | Type | Req | Description |
|---|---|---|---|
| commerceId | string | yes | The commerceOrder you sent on create |
No output schema declared.
No examples provided.
get_payment_status_by_flow_order ~48
Get a payment order's status by Flow order number (GET /payment/getStatusByFlowOrder).
| Name | Type | Req | Description |
|---|---|---|---|
| flowOrder | number | yes | Flow order number (returned by create_payment) |
No output schema declared.
No examples provided.
get_refund_status ~53
Get a refund order's status by refund token (GET /refund/getStatus). status: created, accepted, rejected, refunded, canceled.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Refund token (returned by create_refund) |
No output schema declared.
No examples provided.
list_payments ~79
List payments received on a given date (GET /payment/getPayments). Paged; date is the merchant's local day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date to list, format YYYY-MM-DD |
| limit | number | — | Page size, max 100 (default 10) |
| start | number | — | Pagination offset (default 0) |
No output schema declared.
No examples provided.