# Bsale MCP by usefulapi (remote · bsale.usefulapi.io)

Read Bsale products, documents and stock; manage customers, prices, receipts and payments.

- Trust score: 18/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `bsale.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-bsale/bsale.md), [page](https://verifymcp.io/servers/io-usefulapi-bsale/bsale)

## Channel facts

- Endpoint: `https://bsale.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.6.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Bsale MCP by usefulapi server?

Bsale MCP by usefulapi is a hosted endpoint at https://bsale.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-usefulapi-bsale 'https://bsale.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-bsale": {
      "url": "https://bsale.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-bsale": {
      "type": "http",
      "url": "https://bsale.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-bsale]
url = "https://bsale.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-bsale": {
      "type": "remote",
      "url": "https://bsale.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-bsale --url 'https://bsale.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-bsale:
    url: "https://bsale.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-bsale": {
      "Transport": "http",
      "Url": "https://bsale.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-bsale -t streamable-http -u 'https://bsale.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-bsale": {
      "type": "http",
      "url": "https://bsale.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-02 (score 18, −46)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 63, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “check_customer_receivables”
- [functional] New prompt “find_stock_shortages”
- [functional] New prompt “record_a_payment”
- [functional] New prompt “review_sales_by_branch”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.2.0 → 1.4.0
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] Server version: 1.0.1 → 1.1.0

### 2026-10-30 (score 60)

First indexed and scored.

## MCP tools (25)

### `bsale_list_documents` (~360 tokens)

List documents (sales)

List issued documents (boletas, facturas, notas de credito, guias...) newest-first as Bsale returns them, with number, dates, net/tax/total amounts, state, SII status and public PDF link. Filter by emission date range, document type, client, office, folio number or SII code. Use expand (details, payments, client, office, document_type) to embed related data. GET /v1/documents.json.

Input parameters:

- `client_code` (string): Client tax id (RUT/RUC/RFC) as stored in Bsale.
- `client_id` (integer)
- `code_sii`: Tax code of the document type, e.g. 33 factura, 39 boleta, 61 nota de credito (Chile) or "01" (Peru). Not available for Mexico: use document_type_id.
- `document_type_id` (integer): Document type id (see bsale_list_document_types).
- `emitted_from` (string): A date, yyyy-mm-dd.
- `emitted_to` (string): A date, yyyy-mm-dd.
- `expand` (array)
- `informed_sii` (integer): Tax authority declaration status (SII, SUNAT or SAT): 0 accepted, 1 sent, 2 rejected.
- `limit` (integer): Results per page, 1-50 (default 25).
- `number` (integer): Document folio number.
- `office_id` (integer): Branch (sucursal) id.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_get_document` (~83 tokens)

Get document

One document by id with its amounts, dates, state and links. Use expand=[details,payments,client,office,document_type,references,sellers] to include line items, payments and related records. GET /v1/documents/{id}.json.

Input parameters:

- `document_id` (integer, required): Bsale document id.
- `expand` (array)

### `bsale_sales_summary` (~192 tokens)

Sales summary

Totals of sales documents (net, tax, total, count) by month, document type and office for a date range; set per_document to list each document instead. Good for 'how much did we sell in September?'. GET /v1/documents/summary.json.

Input parameters:

- `code_sii` (array): Only these document type tax codes, e.g. [33, 39] (Chile) or ["01", "03"] (Peru).
- `emitted_from` (string): A date, yyyy-mm-dd.
- `emitted_to` (string): A date, yyyy-mm-dd.
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `per_document` (boolean): true = one row per document instead of grouped totals.

### `bsale_list_returns` (~99 tokens)

List returns

List returns (devoluciones) with date, motive, amounts and the credit note issued. Use expand=[reference_document,credit_note,details] for more. GET /v1/returns.json.

Input parameters:

- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.

### `bsale_list_document_types` (~121 tokens)

List document types

List document types (boleta, factura, nota de credito, guia de despacho...) with their id and tax (SII) code. Use the id when filtering documents. GET /v1/document_types.json.

Input parameters:

- `code_sii`
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_list_clients` (~163 tokens)

List clients

List customers with name, tax id (code), email, phone, address, credit limit and loyalty points. Filter by tax id, name, last name or email. GET /v1/clients.json.

Input parameters:

- `code` (string): Client tax id (RUT/RUC/RFC) exactly as stored.
- `email` (string)
- `expand` (array)
- `first_name` (string)
- `last_name` (string)
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_get_client` (~57 tokens)

Get client

One customer by id. Use expand=[contacts,attributes,addresses] to include contacts and extra attributes. GET /v1/clients/{id}.json.

Input parameters:

- `client_id` (integer, required)
- `expand` (array)

### `bsale_client_unpaid_documents` (~95 tokens)

Client unpaid documents

A client's receivables: overdue and upcoming debt, total owed, and the unpaid documents with amounts. Give client_id or client_code. GET /v1/clients/unpaid_documents.json.

Input parameters:

- `as_of` (string): Date that splits overdue from upcoming (default: today).
- `client_code` (string): Client tax id (RUT/RUC/RFC).
- `client_id` (integer)

### `bsale_list_products` (~142 tokens)

List products

List products and services (name, description, class, stock control, state). SKUs live on variants: see bsale_list_variants. GET /v1/products.json.

Input parameters:

- `classification` (integer): 0 product, 1 service, 3 pack/promotion.
- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `product_type_id` (integer)
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_get_product` (~49 tokens)

Get product

One product by id; expand=[product_type] adds the type. GET /v1/products/{id}.json.

Input parameters:

- `expand` (array)
- `product_id` (integer, required)

### `bsale_list_variants` (~154 tokens)

List variants (SKUs)

List product variants, the sellable SKUs: description, SKU code, barcode, stock settings and product link. Search by SKU code, barcode, description or product id. GET /v1/variants.json.

Input parameters:

- `barcode` (string)
- `code` (string): SKU code.
- `description` (string): Variant name.
- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `product_id` (integer)
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_get_variant` (~52 tokens)

Get variant

One variant (SKU) by id; expand=[product] embeds the product. GET /v1/variants/{id}.json.

Input parameters:

- `expand` (array)
- `variant_id` (integer, required)

### `bsale_list_stocks` (~143 tokens)

List stock levels

Stock per variant and office: quantity, reserved and available. Filter by office, variant id, SKU code or barcode (for a pack give a variant filter plus office_id). expand=[variant,office] adds names. GET /v1/stocks.json.

Input parameters:

- `barcode` (string)
- `code` (string): SKU code.
- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `office_id` (integer)
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `variant_id` (integer)

### `bsale_list_price_lists` (~97 tokens)

List price lists

List price lists with name, currency and state. Use the id with bsale_list_price_list_details. GET /v1/price_lists.json.

Input parameters:

- `coin_id` (integer)
- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.

### `bsale_list_price_list_details` (~146 tokens)

List price list prices

Prices in one price list: the net price (variantValue) and price with taxes per variant, plus the detail id needed to change a price. Filter by variant id, SKU code or barcode. GET /v1/price_lists/{id}/details.json.

Input parameters:

- `barcode` (string)
- `code` (string): SKU code.
- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `price_list_id` (integer, required)
- `variant_id` (integer)

### `bsale_list_payments` (~154 tokens)

List payments

List payments received (amount, date, payment type, document, office, user). Filter by payment date, document id, or document tax code plus folio number. GET /v1/payments.json.

Input parameters:

- `code_sii`: Document tax code; combine with number.
- `document_id` (integer)
- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `number` (integer): Document folio number; combine with code_sii.
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `paid_on` (string): Only payments recorded on this date.

### `bsale_list_payment_types` (~104 tokens)

List payment types

List payment methods (cash, card, transfer, credit...) with their id. The id is needed to record a payment. GET /v1/payment_types.json.

Input parameters:

- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_list_offices` (~104 tokens)

List offices (branches)

List branches (sucursales) with name, address and cost center. Use the id for stock and document filters. GET /v1/offices.json.

Input parameters:

- `limit` (integer): Results per page, 1-50 (default 25).
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_list_users` (~108 tokens)

List users (sellers)

List Bsale users (sellers/cashiers) with name and office. GET /v1/users.json.

Input parameters:

- `expand` (array)
- `limit` (integer): Results per page, 1-50 (default 25).
- `office_id` (integer)
- `offset` (integer): Items to skip (default 0). Pass the previous reply's next_offset.
- `state`: 0 = active records (Bsale default), 1 = inactive.

### `bsale_user_sales_summary` (~77 tokens)

Sales by seller

Sales and tax subtotal per seller for a date range (default: today, UTC), or for one user. GET /v1/users/sales_summary.json.

Input parameters:

- `from` (string): A date, yyyy-mm-dd.
- `to` (string): A date, yyyy-mm-dd.
- `user_id` (integer)

### `bsale_create_client` (~230 tokens)

Create client

WRITE: create a new customer in Bsale (it is visible to every user of the instance). Give at least a first name or a company. Bsale rejects a second client with the same tax id. POST /v1/clients.json.

Input parameters:

- `activity` (string): Giro / business activity.
- `address` (string)
- `city` (string)
- `code` (string): Tax id (RUT in Chile, RUC in Peru, RFC in Mexico). Validate it first.
- `company` (string)
- `district` (string): Colonia / district (Mexico). Chile and Peru: use municipality.
- `email` (string)
- `first_name` (string)
- `is_foreigner` (boolean): true for a foreign client (Bsale assigns tax id 55555555-5 unless you also pass code).
- `last_name` (string)
- `municipality` (string): Comuna (Chile) or municipality (Peru). Mexican accounts: use district.
- `note` (string)
- `phone` (string)

### `bsale_update_client` (~192 tokens)

Update client

WRITE: change fields of an existing customer; only the fields you pass are sent. This overwrites the stored values. PUT /v1/clients/{id}.json.

Input parameters:

- `activity` (string): Giro / business activity.
- `address` (string)
- `city` (string)
- `client_id` (integer, required)
- `code` (string): Tax id (RUT in Chile, RUC in Peru, RFC in Mexico). Validate it first.
- `company` (string)
- `district` (string): Colonia / district (Mexico). Chile and Peru: use municipality.
- `email` (string)
- `first_name` (string)
- `last_name` (string)
- `municipality` (string): Comuna (Chile) or municipality (Peru). Mexican accounts: use district.
- `note` (string)
- `phone` (string)

### `bsale_update_price` (~127 tokens)

Update price list price

WRITE: set the net price (variantValue, without taxes) of one variant in a price list. This changes what Bsale charges on new sales using that list. Get detail_id from bsale_list_price_list_details. PUT /v1/price_lists/{id}/details/{detail_id}.json.

Input parameters:

- `detail_id` (integer, required): Price list detail id (the id of the row in bsale_list_price_list_details).
- `net_price` (number, required): New net price (before taxes) in the price list's currency.
- `price_list_id` (integer, required)

### `bsale_create_stock_reception` (~157 tokens)

Receive stock

WRITE: record a stock reception (ingreso de stock) that ADDS quantities to an office's inventory. Each line names the variant by id, SKU code or barcode, with quantity and unit cost. It changes stock levels and cost; Bsale has no undo through this API, so confirm the numbers first. POST /v1/stocks/receptions.json.

Input parameters:

- `details` (array, required)
- `document` (string): Kind of incoming document, e.g. "Guia", "Factura", "Otro" (default "Otro").
- `document_number` (integer): Number of the incoming document.
- `note` (string)
- `office_id` (integer, required): Office (sucursal) receiving the stock.

### `bsale_create_payment` (~119 tokens)

Record payment

WRITE: record a payment against an issued document (normally a credit sale that is still unpaid). It changes the document's receivable balance in the books and cannot be removed through this API. Check the amount with bsale_client_unpaid_documents first and get payment_type_id from bsale_list_payment_types. POST /v1/payments.json.

Input parameters:

- `amount` (number, required)
- `document_id` (integer, required)
- `paid_on` (string): Payment date (default: today, UTC).
- `payment_type_id` (integer, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-bsale/bsale#diagnostics

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 64
- 2026-10-31: 63
- 2026-10-30: 60

## Common questions

### What is the Bsale MCP by usefulapi server?

Bsale MCP by usefulapi is listed in the public MCP registry as io.usefulapi/bsale. Read Bsale products, documents and stock; manage customers, prices, receipts and payments. This page covers its hosted endpoint (https://bsale.usefulapi.io/mcp).

### Is the Bsale MCP by usefulapi server safe to use?

Bsale MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Bsale MCP by usefulapi server expose?

Bsale MCP by usefulapi exposes 25 tools: bsale_list_documents, bsale_get_document, bsale_sales_summary, bsale_list_returns, bsale_list_document_types, and 20 more. Their descriptions and schemas cost roughly 3,325 tokens of context every time the server is loaded.

### Does the Bsale MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Bsale MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Bsale MCP by usefulapi server still maintained?

Bsale MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://bsale.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/bsale/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-bsale/bsale.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-bsale/bsale.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-bsale/bsale