Alpaca Trading API integration for Model Context Protocol (MCP)
Laudus MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read Laudus ERP customers, sales, purchases, stock and accounting reports; create customers.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http laudus-mcp-by-usefulapi https://laudus.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# laudus_list_customers, laudus_list_sales_invoices, laudus_list_sales_orders and 35 more
Laudus MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http laudus-mcp-by-usefulapi https://laudus.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
38 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List customers with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example customerId, name, legalName, VATId, email, phone1, city, county, creditLimit, blocked, customerCategory.name, salesman.name. When a page is full, ask for the next one with offset = offset + limit. POST /sales/customers/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List sales invoices and electronic tax documents (facturas, notas de credito) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesInvoiceId, docType.name, docNumber, issuedDate, dueDate, customer.name, customer.VATId, totals.net, totals.total, items.product.sku, items.quantity. When a page is full, ask for
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List sales orders (pedidos de venta) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesOrderId, issuedDate, dueDate, customer.name, items.product.sku, items.quantity. When a page is full, ask for the next one with offset = offset + limit. POST /sales/orders/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List sales quotes (cotizaciones) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesQuoteId, issuedDate, customer.name, items.product.sku, items.quantity. When a page is full, ask for the next one with offset = offset + limit. POST /sales/quotes/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List customer payments received (cobros) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example receiptId, receiptType, issuedDate, dueDate. When a page is full, ask for the next one with offset = offset + limit. POST /sales/receipts/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List products and services (the item master) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example productId, sku, description, productCategory.name, unitOfMeasure, unitPrice, stockable, discontinued. When a page is full, ask for the next one with offset = offset + limit. POST /production/products/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List product categories with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example productCategoryId, name, fullPath. When a page is full, ask for the next one with offset = offset + limit. POST /production/products/categories/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List warehouses (bodegas) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example warehouseId, name, city. When a page is full, ask for the next one with offset = offset + limit. POST /production/warehouses/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List salespeople (vendedores) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example salesmanId, name. When a page is full, ask for the next one with offset = offset + limit. POST /sales/salesmen/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List suppliers (proveedores) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example supplierId, name, legalName, VATId, email, phone, city. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/suppliers/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List purchase invoices (facturas de compra) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example purchaseInvoiceId, docNumber, issuedDate, dueDate, supplier.name, totals.total. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/invoices/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List purchase orders (ordenes de compra) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example purchaseOrderId, issuedDate, supplier.name, status, items.product.sku, items.quantity. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/orders/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List the chart of accounts (plan de cuentas) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example accountId, accountNumber, name. When a page is full, ask for the next one with offset = offset + limit. POST /accounting/accounts/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List accounting journal entries (comprobantes) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example journalEntryId, journalEntryNumber, date, lines.account.accountNumber, lines.debit, lines.credit. When a page is full, ask for the next one with offset = offset + limit. POST /accounting/journal/entries/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
List cost centers (centros de costo) with filters, sorting, field selection and paging (rows 25 by default, at most 200). Field names follow the Laudus data model, for example costCenterId, name, code. When a page is full, ask for the next one with offset = offset + limit. POST /purchases/costcenters/list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fields | array | no | Fields to return (default: all). Nested names work, e.g. customer.name, items.quantity. |
| filter | array | no | Conditions, all of which must hold (AND). |
| order_by | array | no | Sort order. |
| limit | integer | no | Rows to return, 1-200 (default 25). |
| offset | integer | no | Rows to skip (default 0). For the next page pass offset + limit. |
Get a customer (addresses, contact data, credit limit, category, salesman, price list) by id. GET /sales/customers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | — |
Get a sales invoice with its lines, taxes and totals by id. GET /sales/invoices/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sales_invoice_id | yes | — |
Get a sales order with its lines by id. GET /sales/orders/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sales_order_id | integer | yes | — |
Get a sales quote with its lines by id. GET /sales/quotes/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sales_quote_id | integer | yes | — |
Get a product (SKU, description, category, units, prices) by id. GET /production/products/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | integer | yes | — |
Get a supplier by id. GET /purchases/suppliers/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier_id | integer | yes | — |
Get a purchase invoice with its lines by id. GET /purchases/invoices/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_invoice_id | integer | yes | — |
Get a purchase order with its lines by id. GET /purchases/orders/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| purchase_order_id | integer | yes | — |
Get an accounting journal entry (comprobante) with its lines by id. GET /accounting/journal/entries/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| journal_entry_id | integer | yes | — |
Unpaid sales invoices (accounts receivable). Give customer_id for one customer, or leave it out for all customers. GET /sales/customers/{id}/pendingInvoices or /sales/customers/pendingInvoices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | no | Customer id; omit for every customer. |
A customer's credit limit and how much of it is used. GET /sales/customers/{id}/creditLimit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | — |
The contact people of a customer. GET /sales/customers/{id}/contacts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | yes | — |
The customer payments (cobros) applied to one sales invoice. GET /sales/invoices/{id}/receipts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sales_invoice_id | yes | — |
The ids of sales orders not yet delivered, optionally for one customer or a due-date range. GET /sales/orders/pending.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | integer | no | — |
| due_date_from | string | no | Due date from (yyyy-mm-dd). |
| due_date_to | string | no | Due date to (yyyy-mm-dd). |
Invoiced sales totals grouped by day of week, day of month, month, year, salesman, customer, customer category, product, product category, county, state or branch, for a date range and optional filters. GET /reports/sales/invoices/{group}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_by | string | yes | How to group the totals. |
| date_from | string | no | — |
| date_to | string | no | — |
| customer_id | integer | no | — |
| salesman_id | integer | no | — |
| product_id | integer | no | — |
| branch_id | integer | no | — |
Stock of one product, optionally as of a date, in one warehouse or lot; with by_warehouse true, the stock in each warehouse. GET /production/products/{id}/stock or /stockByWarehouses.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | integer | yes | — |
| date_to | string | no | Stock as of this date (default today). |
| warehouse_id | string | no | Only this warehouse (ignored with by_warehouse). |
| lot | string | no | Only this lot (ignored with by_warehouse). |
| by_warehouse | boolean | no | Break the stock down per warehouse. |
Stock of every product, optionally as of a date, for one warehouse or one product category. Can be large: filter by warehouse or category. GET /production/products/stock.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_to | string | no | Stock as of this date (default today). |
| warehouse_id | string | no | — |
| product_category_id | string | no | — |
The stock movements (kardex) of one product, optionally to a date and for one warehouse. GET /production/products/{id}/kardex.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product_id | integer | yes | — |
| date_to | string | no | — |
| warehouse_id | string | no | — |
The balance sheet (balance general) as of a date, either the standard layout or the totals layout. GET /accounting/balanceSheet/standard or /totals.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| layout | string | no | Default standard. |
| date_to | string | no | As of this date (default today). |
| show_accounts_with_zero_balance | boolean | no | — |
| show_only_accounts_with_activity | boolean | no | — |
| show_levels | string | no | Account levels to show, as in Laudus (for example 1,2,3). |
| cost_center_id | string | no | — |
| book_id | string | no | Accounting book id (default: the main book). |
The profit and loss statement (estado de resultados) for a date range. GET /accounting/profitAndLoss.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_from | string | no | — |
| date_to | string | no | — |
| show_accounts_with_zero_balance | boolean | no | — |
| show_only_accounts_with_activity | boolean | no | — |
| show_levels | string | no | Account levels to show, as in Laudus (for example 1,2,3). |
| cost_center_id | string | no | — |
| book_id | string | no | Accounting book id (default: the main book). |
The general ledger (libro mayor) movements of an account or a range of account numbers, for a date range. GET /accounting/ledger.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_number_from | string | yes | First account number (or the only one). |
| account_number_to | string | no | Last account number of a range. |
| date_from | string | no | — |
| date_to | string | no | — |
| cost_center_id | string | no | — |
| book_id | string | no | — |
| limit | integer | no | Rows to return (default 100, at most 1000). |
| offset | integer | no | Rows to skip. |
The purchases ledger (libro de compras) for a year and month. GET /purchases/invoices/ledger.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | no | — |
| month | integer | no | — |
WRITE: creates a new customer in Laudus (the customer id is assigned by Laudus; the customer record is not an invoice and sends nothing). Check laudus_list_customers for the RUT first to avoid duplicates. Laudus may require more fields than given and answers with its validation message. POST /sales/customers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Trade name (max 50 characters). |
| legal_name | string | no | Legal name / razon social (max 80). |
| vat_id | string | no | Customer RUT, e.g. 76123456-7. |
| activity_name | string | no | Business activity (giro). |
| address | string | no | — |
| city | string | no | — |
| county | string | no | Comuna. |
| string | no | — | |
| dte_email | string | no | Email for electronic tax documents. |
| phone | string | no | — |
| notes | string | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Laudus MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| laudus_list_customers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_sales_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_sales_orders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_sales_quotes | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_sales_receipts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_products | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_product_categories | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_warehouses | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_salesmen | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_suppliers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_purchase_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_purchase_orders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_accounts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_journal_entries | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_cost_centers | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_customer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_sales_invoice | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_sales_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_sales_quote | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_product | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_supplier | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_purchase_invoice | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_purchase_order | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_journal_entry | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_customer_pending_invoices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_customer_credit_limit | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_customer_contacts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_sales_invoice_receipts | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_pending_sales_orders | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_sales_report | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_get_product_stock | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_list_stock | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_product_kardex | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_balance_sheet | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_profit_and_loss | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_general_ledger | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_purchase_ledger | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| laudus_create_customer | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.3.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Laudus MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.