Name: PHP Point of Sale MCP by usefulapi
Author: usefulapi

PHP Point of Sale MCP by usefulapi

Read PHP Point of Sale items, sales, customers and 138 reports; manage customers, items, expenses.

Tool-list grade A Remote · Streamable HTTP No auth needed 26 tools v1.17.2 MIT

No reviews yet by usefulapiGitHub The publisher’s own endpoint — this marketplace is not in the path

93/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Read PHP Point of Sale items, sales, customers and 138 reports; manage customers, items, expenses.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http php-point-of-sale-mcp-by-usefulapi https://php-point-of-sale.usefulapi.io/mcp

# 2 — ask your agent for something these tools do
#   phppos_list_locations, phppos_list_items, phppos_get_item and 23 more

PHP Point of Sale 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.

Publishernot claimed

usefulapi598 servers

25 categories

All 598 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

List the store's locations (shops/warehouses) with name, address, phone, email, time zone and default tax rates, plus each location's registers (id and name). Use the location ids to filter sales, expenses, customers and reports. Payment-processor credentials and device settings are never returned. GET /locations.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

List or search inventory items with name, item number, category, supplier, prices and reorder level. Search by text, or by one field (name, item_number, product_id, supplier, tag_name...). GET /items.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
search_field	string	no	Limit the search to one field.
category_id	integer	no	Only items in this category id - see phppos_list_categories.
sort_col	string	no	Column to sort by (a field name of the rows).
sort_dir	string	no	Sort direction.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-1000 (default 20).

One inventory item by id: prices, tax settings, category, supplier, tags, attributes, variations, tier pricing and per-location settings. GET /items/{id}.

Parameter	Type	Required	Notes
item_id	integer	yes	PHP Point of Sale item id (find it with phppos_list_items).

List item categories with their ids. Use the ids to filter items or to file a new item. GET /categories.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

List item kits (bundles of items sold together) with their prices. GET /item_kits.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
category_id	integer	no	Only kits in this category id.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

List or search completed sales, by date range, customer (id or email) or location. verbosity: minimal (headline fields), medium (adds customer, totals, profit, location - the default here) or full (every line item, payment and tax). Suspended sales (layaways, estimates) are fetched with suspended_type. GET /sales.

Parameter	Type	Required	Notes
start_date	string	no	Only sales on or after this date or date-time (yyyy-mm-dd or yyyy-mm-dd hh:mm:ss).
end_date	string	no	Only sales on or before this date or date-time.
customer_id	integer	no	Only this customer's sales.
email_address	string	no	Look the customer up by email address and return their sales.
location_id	integer	no	Only sales at this location id - see phppos_list_locations.
suspended_type	string	no	Fetch suspended sales instead of completed ones: a comma-separated list of layaway, estimate or a sale type name.
verbosity	string	no	minimal, medium (default) or full.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-1000 (default 25).

One sale by id with line items, payments, taxes, customer and employee (verbosity full by default). GET /sales/{id}.

Parameter	Type	Required	Notes
sale_id	integer	yes	PHP Point of Sale sale id (the number on the receipt; find it with phppos_list_sales).
verbosity	string	no	minimal, medium or full (default).

List receivings (stock received from suppliers, purchase orders, transfers) with supplier, totals and items, by date range. GET /receivings.

Parameter	Type	Required	Notes
start_date	string	no	Only receivings on or after this date or date-time.
end_date	string	no	Only receivings on or before this date or date-time.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-1000 (default 25).

One receiving by id: supplier, items, quantities, costs and payments. GET /receivings/{id}.

Parameter	Type	Required	Notes
receiving_id	integer	yes	Receiving id (find it with phppos_list_receivings).

List or search customers with contact details, tier, store-account balance, credit limit and loyalty points. Search by text or by one field (email, phone_number, first_name, last_name, account_number). GET /customers.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
search_field	string	no	Limit the search to one field.
location_id	integer	no	Only customers at this location id.
sort_col	string	no	Column to sort by (a field name of the rows).
sort_dir	string	no	Sort direction.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

One customer by person id: contact details, tier, tax settings, balance, credit limit, points, notes and custom fields. GET /customers/{person_id}.

Parameter	Type	Required	Notes
person_id	integer	yes	Customer person id (find it with phppos_list_customers).

List or search suppliers with contact details, company, account number and balance. GET /suppliers.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
search_field	string	no	Limit the search to one field.
sort_col	string	no	Column to sort by (a field name of the rows).
sort_dir	string	no	Sort direction.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

One supplier by person id. GET /suppliers/{person_id}.

Parameter	Type	Required	Notes
person_id	integer	yes	Supplier person id (find it with phppos_list_suppliers).

List employees with name, contact details, username, hire date, manager, commission and pay rate settings and assigned locations. Passwords and the permission maps are never returned. GET /employees.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
location_id	integer	no	Only employees at this location id.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

List customer invoices (money customers owe) or supplier invoices (money the store owes) with date, due date, status and amount. GET /invoices/customer or /invoices/supplier.

Parameter	Type	Required	Notes
type	string	yes	customer = invoices to customers; supplier = invoices from suppliers.
search	string	no	Free-text search.
sort_col	string	no	Column to sort by (a field name of the rows).
sort_dir	string	no	Sort direction.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

List recorded expenses with type, description, date, amount, tax, payment type, category and location. GET /expenses.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
location_id	integer	no	Only expenses at this location id.
sort_col	string	no	Column to sort by (a field name of the rows).
sort_dir	string	no	Sort direction.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

List gift cards with number, description, remaining value, customer and whether inactive. GET /giftcards.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

One gift card by its card number (or id): remaining value, customer and status. GET /giftcards/{giftcard_number}.

Parameter	Type	Required	Notes
giftcard_number	string	yes	Gift card number or id.

List appointments (bookings) with customer, employee, service, start and end time, optionally within a time window. GET /appointments.

Parameter	Type	Required	Notes
search	string	no	Free-text search.
start_time	string	no	Only appointments starting on or after this date or date-time.
end_time	string	no	Only appointments ending on or before this date or date-time.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-100 (default 20).

The catalog of the store's reports (138 of them: sales summaries, top sellers, inventory low/aging/summary, profit and loss, taxes, payments, employee, customer, supplier and store-account reports) with the inputs each accepts. Without search only the report keys are returned; with search (for example 'inventory' or 'profit') the matching reports are returned with their inputs. GET /reports.

Parameter	Type	Required	Notes
search	string	no	Only reports whose key, description or inputs contain this text.

Run one of the store's reports and return it (title, summary, detail rows); paging.next_offset is set when more detail rows remain. Report keys and their inputs come from phppos_list_reports (for example summary_sales, top_sellers, inventory_low, summary_profit_and_loss, summary_taxes, closeout). Typical inputs go in params: start_date, end_date, sale_type, location_ids (array), category_id, s

Parameter	Type	Required	Notes
report_key	string	yes	Report key from phppos_list_reports (for example summary_sales or inventory_low).
params	object	no	The report's inputs as listed by phppos_list_reports, e.g. {"start_date":"2026-10-01","end_date":"2026-10-31","location_ids":[1]}. Do not put limit/offset here.
offset	integer	no	Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
limit	integer	no	Rows per page, 1-500 (default 100).

WRITE: create a customer in the store. Store-account balance, credit limit and loyalty points cannot be set here. Needs a Read/Write API key. Retrying creates a duplicate (check phppos_list_customers first). The store's 'new customer' webhook, if configured, fires. POST /customers.

Parameter	Type	Required	Notes
first_name	string	yes	First name (required by PHP Point of Sale).
last_name	string	no	Last name.
email	string	no	Email address.
phone_number	string	no	Phone number.
address_1	string	no	Address line 1.
address_2	string	no	Address line 2.
city	string	no	City.
state	string	no	State or region.
zip	string	no	Postal code.
country	string	no	Country.
comments	string	no	Comments.
company_name	string	no	Company name.
account_number	string	no	Customer account number.
taxable	boolean	no	Whether sales to this customer are taxed.
internal_notes	string	no	Internal notes (not shown to the customer).

WRITE: change fields of an existing customer; only the fields you pass are sent. Overwrites the current values. Needs a Read/Write API key. The store's 'edit customer' webhook, if configured, fires. POST /customers/{person_id}.

Parameter	Type	Required	Notes
person_id	integer	yes	Customer person id (find it with phppos_list_customers).
first_name	string	no	First name.
last_name	string	no	Last name.
email	string	no	Email address.
phone_number	string	no	Phone number.
address_1	string	no	Address line 1.
address_2	string	no	Address line 2.
city	string	no	City.
state	string	no	State or region.
zip	string	no	Postal code.
country	string	no	Country.
comments	string	no	Comments.
company_name	string	no	Company name.
account_number	string	no	Customer account number.
taxable	boolean	no	Whether sales to this customer are taxed.
internal_notes	string	no	Internal notes (not shown to the customer).

WRITE: create an inventory item (name required). Stock quantities are not set here. Needs a Read/Write API key. Retrying creates a duplicate (search with phppos_list_items first). The store's item webhooks, if configured, fire. POST /items.

Parameter	Type	Required	Notes
name	string	yes	Item name.
description	string	no	Short description.
unit_price	number	no	Selling price.
cost_price	number	no	Cost price.
promo_price	number	no	Promotional price.
category_id	integer	no	Category id - see phppos_list_categories.
supplier_id	integer	no	Supplier person id - see phppos_list_suppliers.
item_number	string	no	Barcode / item number (UPC).
product_id	string	no	Product id / SKU.
size	string	no	Size.
is_service	boolean	no	True for a service (no stock tracking).
item_inactive	boolean	no	True to deactivate the item (it can no longer be sold).
reorder_level	number	no	Stock level at which the item shows as low.
tags	array	no	Tag names.

WRITE: change fields of an existing item (for example its price, category or active state); only the fields you pass are sent. Overwrites the current values, and a price change applies to the next sale. Needs a Read/Write API key. The store's 'edit item' webhook, if configured, fires. POST /items/{item_id}.

Parameter	Type	Required	Notes
item_id	integer	yes	Item id (find it with phppos_list_items).
name	string	no	Item name.
description	string	no	Short description.
unit_price	number	no	Selling price.
cost_price	number	no	Cost price.
promo_price	number	no	Promotional price.
category_id	integer	no	Category id - see phppos_list_categories.
supplier_id	integer	no	Supplier person id - see phppos_list_suppliers.
item_number	string	no	Barcode / item number (UPC).
product_id	string	no	Product id / SKU.
size	string	no	Size.
is_service	boolean	no	True for a service (no stock tracking).
item_inactive	boolean	no	True to deactivate the item (it can no longer be sold).
reorder_level	number	no	Stock level at which the item shows as low.
tags	array	no	Tag names.

WRITE: record an expense in the store's books (description, amount and date). It affects expense and profit-and-loss reports. Needs a Read/Write API key. Retrying records it twice (check phppos_list_expenses first). POST /expenses.

Parameter	Type	Required	Notes
expense_description	string	yes	What the expense was for.
expense_amount	number	yes	Amount, in the store's currency, before tax.
expense_date	string	no	When it was incurred (yyyy-mm-dd or yyyy-mm-dd hh:mm:ss); defaults to now in the store.
expense_tax	number	no	Tax amount.
expense_type	string	no	Expense type, for example Utilities.
expense_reason	string	no	Reason.
expense_note	string	no	Note.
expense_payment_type	string	no	Payment type, for example Cash.
category_id	integer	no	Expense category id.
location_id	integer	no	Location id - see phppos_list_locations.

Free

$0 forever

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

Nothing here is billable: mcprush charges nothing to install PHP Point of Sale MCP by usefulapi or to call it, at any volume.

ATool-list grade · score 93 / 100

Release 1.17.2 · scanned 7 Nov 2026

Graded from the tools this server lists, not from its source code.

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.

Threat score100

Client score93

Findings0 threat · 1 capability

Capabilitymoderate

Coveragemanifest

Verificationnot in this report

Surface digeste18b6a6e7491cff5b28ae27051369c092664ade7a0689fe7e6818cf1b7d6b680

Score vectorthreat 100 → client 93

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

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

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.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

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
phppos_list_locations	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_items	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_get_item	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_categories	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_item_kits	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_sales	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_get_sale	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_receivings	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_get_receiving	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_customers	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_get_customer	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_suppliers	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_get_supplier	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_employees	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_invoices	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_expenses	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_gift_cards	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_get_gift_card	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_appointments	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_list_reports	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_run_report	untrusted-input	untrusted-input: declares openWorldHint: true (interacts with entities outside the server)
phppos_create_customer	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
phppos_update_customer	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
phppos_create_item	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
phppos_update_item	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true
phppos_create_expense	external-sink	external-sink: declares readOnlyHint: false, destructiveHint: true, 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.

flow-1

Untrusted input can drive an external action even though no sensitive source is exposed.

Supply chain and provenance

Integrityfirst-seen

Surface digeste18b6a6e7491cff5

Scanned2026-11-07

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.

Where are you running it?

Tool surface

Release history

PHP Point of Sale MCP by usefulapi

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also