Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bsale MCP by usefulapi

REMOTE · BSALE.USEFULAPI.IO

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

18 Trust /100

Last scanned (9 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

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.

Changelog

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.

  • 2 Nov 26 −46
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 26 +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.

  • 31 Oct 26 +3
    • Authorization: partial → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • 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 functional
  • 30 Oct 26 60

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://bsale.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 d9be3287b0fde9630e825ba1f79bff3f
SANs: usefulapi.io, *.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bsale.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 302

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bsale.usefulapi.io/mcp Redirected 302 https://usefulapi.io/bsale/
http (plaintext) http://bsale.usefulapi.io/mcp Inconclusive 302 http://bsale.usefulapi.io/mcp
MCP tools · 25 exposed · ~3,325 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bsale_client_unpaid_documents ~95

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.

NameTypeReqDescription
as_ofstring–Date that splits overdue from upcoming (default: today).
client_codestring–Client tax id (RUT/RUC/RFC).
client_idinteger––

No output schema declared.

No examples provided.

bsale_create_client ~230

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.

NameTypeReqDescription
activitystring–Giro / business activity.
addressstring––
citystring––
codestring–Tax id (RUT in Chile, RUC in Peru, RFC in Mexico). Validate it first.
companystring––
districtstring–Colonia / district (Mexico). Chile and Peru: use municipality.
emailstring––
first_namestring––
is_foreignerboolean–true for a foreign client (Bsale assigns tax id 55555555-5 unless you also pass code).
last_namestring––
municipalitystring–Comuna (Chile) or municipality (Peru). Mexican accounts: use district.
notestring––
phonestring––

No output schema declared.

No examples provided.

bsale_create_payment ~119

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.

NameTypeReqDescription
amountnumberyes–
document_idintegeryes–
paid_onstring–Payment date (default: today, UTC).
payment_type_idintegeryes–

No output schema declared.

No examples provided.

bsale_create_stock_reception ~157

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.

NameTypeReqDescription
detailsarrayyes–
documentstring–Kind of incoming document, e.g. "Guia", "Factura", "Otro" (default "Otro").
document_numberinteger–Number of the incoming document.
notestring––
office_idintegeryesOffice (sucursal) receiving the stock.

No output schema declared.

No examples provided.

bsale_get_client ~57

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

NameTypeReqDescription
client_idintegeryes–
expandarray––

No output schema declared.

No examples provided.

bsale_get_document ~83

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.

NameTypeReqDescription
document_idintegeryesBsale document id.
expandarray––

No output schema declared.

No examples provided.

bsale_get_product ~49

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

NameTypeReqDescription
expandarray––
product_idintegeryes–

No output schema declared.

No examples provided.

bsale_get_variant ~52

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

NameTypeReqDescription
expandarray––
variant_idintegeryes–

No output schema declared.

No examples provided.

bsale_list_clients ~163

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.

NameTypeReqDescription
codestring–Client tax id (RUT/RUC/RFC) exactly as stored.
emailstring––
expandarray––
first_namestring––
last_namestring––
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_list_document_types ~121

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.

NameTypeReqDescription
code_sii–––
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_list_documents ~360

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.

NameTypeReqDescription
client_codestring–Client tax id (RUT/RUC/RFC) as stored in Bsale.
client_idinteger––
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_idinteger–Document type id (see bsale_list_document_types).
emitted_fromstring–A date, yyyy-mm-dd.
emitted_tostring–A date, yyyy-mm-dd.
expandarray––
informed_siiinteger–Tax authority declaration status (SII, SUNAT or SAT): 0 accepted, 1 sent, 2 rejected.
limitinteger–Results per page, 1-50 (default 25).
numberinteger–Document folio number.
office_idinteger–Branch (sucursal) id.
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_list_offices ~104

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

NameTypeReqDescription
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_list_payment_types ~104

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

NameTypeReqDescription
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_list_payments ~154

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.

NameTypeReqDescription
code_sii––Document tax code; combine with number.
document_idinteger––
expandarray––
limitinteger–Results per page, 1-50 (default 25).
numberinteger–Document folio number; combine with code_sii.
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
paid_onstring–Only payments recorded on this date.

No output schema declared.

No examples provided.

bsale_list_price_list_details ~146

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.

NameTypeReqDescription
barcodestring––
codestring–SKU code.
expandarray––
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
price_list_idintegeryes–
variant_idinteger––

No output schema declared.

No examples provided.

bsale_list_price_lists ~97

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

NameTypeReqDescription
coin_idinteger––
expandarray––
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.

No output schema declared.

No examples provided.

bsale_list_products ~142

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

NameTypeReqDescription
classificationinteger–0 product, 1 service, 3 pack/promotion.
expandarray––
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
product_type_idinteger––
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_list_returns ~99

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.

NameTypeReqDescription
expandarray––
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.

No output schema declared.

No examples provided.

bsale_list_stocks ~143

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.

NameTypeReqDescription
barcodestring––
codestring–SKU code.
expandarray––
limitinteger–Results per page, 1-50 (default 25).
office_idinteger––
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
variant_idinteger––

No output schema declared.

No examples provided.

bsale_list_users ~108

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

NameTypeReqDescription
expandarray––
limitinteger–Results per page, 1-50 (default 25).
office_idinteger––
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_list_variants ~154

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.

NameTypeReqDescription
barcodestring––
codestring–SKU code.
descriptionstring–Variant name.
expandarray––
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
product_idinteger––
state––0 = active records (Bsale default), 1 = inactive.

No output schema declared.

No examples provided.

bsale_sales_summary ~192

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.

NameTypeReqDescription
code_siiarray–Only these document type tax codes, e.g. [33, 39] (Chile) or ["01", "03"] (Peru).
emitted_fromstring–A date, yyyy-mm-dd.
emitted_tostring–A date, yyyy-mm-dd.
limitinteger–Results per page, 1-50 (default 25).
offsetinteger–Items to skip (default 0). Pass the previous reply's next_offset.
per_documentboolean–true = one row per document instead of grouped totals.

No output schema declared.

No examples provided.

bsale_update_client ~192

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

NameTypeReqDescription
activitystring–Giro / business activity.
addressstring––
citystring––
client_idintegeryes–
codestring–Tax id (RUT in Chile, RUC in Peru, RFC in Mexico). Validate it first.
companystring––
districtstring–Colonia / district (Mexico). Chile and Peru: use municipality.
emailstring––
first_namestring––
last_namestring––
municipalitystring–Comuna (Chile) or municipality (Peru). Mexican accounts: use district.
notestring––
phonestring––

No output schema declared.

No examples provided.

bsale_update_price ~127

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.

NameTypeReqDescription
detail_idintegeryesPrice list detail id (the id of the row in bsale_list_price_list_details).
net_pricenumberyesNew net price (before taxes) in the price list's currency.
price_list_idintegeryes–

No output schema declared.

No examples provided.

bsale_user_sales_summary ~77

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

NameTypeReqDescription
fromstring–A date, yyyy-mm-dd.
tostring–A date, yyyy-mm-dd.
user_idinteger––

No output schema declared.

No examples provided.

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.

remote · bsale.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-bsale 'https://bsale.usefulapi.io/mcp'
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.