# PHP Point of Sale MCP by usefulapi (remote · php-point-of-sale.usefulapi.io)

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

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `php-point-of-sale.usefulapi.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-php-point-of-sale/php-point-of-sale.md), [page](https://verifymcp.io/servers/io-usefulapi-php-point-of-sale/php-point-of-sale)

## Channel facts

- Endpoint: `https://php-point-of-sale.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.3`

## 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-10-25.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4116 tokens (~158/item across 26 items; 26 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the PHP Point of Sale MCP by usefulapi server?

PHP Point of Sale MCP by usefulapi is a hosted endpoint at https://php-point-of-sale.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-php-point-of-sale 'https://php-point-of-sale.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-php-point-of-sale": {
      "url": "https://php-point-of-sale.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-php-point-of-sale": {
      "type": "http",
      "url": "https://php-point-of-sale.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-php-point-of-sale]
url = "https://php-point-of-sale.usefulapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usefulapi-php-point-of-sale --url 'https://php-point-of-sale.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-php-point-of-sale:
    url: "https://php-point-of-sale.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-php-point-of-sale": {
      "Transport": "http",
      "Url": "https://php-point-of-sale.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-php-point-of-sale -t streamable-http -u 'https://php-point-of-sale.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-php-point-of-sale": {
      "type": "http",
      "url": "https://php-point-of-sale.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-10-25 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.2.2 → 1.2.3
- [functional] Server version: 1.2.0 → 1.2.2

### 2026-10-24 (score 62)

First indexed and scored.

## MCP tools (26)

### `phppos_list_locations` (~135 tokens)

List locations

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.

Input parameters:

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

### `phppos_list_items` (~180 tokens)

List items

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.

Input parameters:

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

### `phppos_get_item` (~68 tokens)

Get item

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

Input parameters:

- `item_id` (integer, required): PHP Point of Sale item id (find it with phppos_list_items).

### `phppos_list_categories` (~93 tokens)

List categories

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

Input parameters:

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

### `phppos_list_item_kits` (~106 tokens)

List item kits

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

Input parameters:

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

### `phppos_list_sales` (~275 tokens)

List sales

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.

Input parameters:

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

### `phppos_get_sale` (~81 tokens)

Get sale

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

Input parameters:

- `sale_id` (integer, required): PHP Point of Sale sale id (the number on the receipt; find it with phppos_list_sales).
- `verbosity` (string): minimal, medium or full (default).

### `phppos_list_receivings` (~134 tokens)

List receivings

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

Input parameters:

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

### `phppos_get_receiving` (~56 tokens)

Get receiving

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

Input parameters:

- `receiving_id` (integer, required): Receiving id (find it with phppos_list_receivings).

### `phppos_list_customers` (~173 tokens)

List customers

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.

Input parameters:

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

### `phppos_get_customer` (~65 tokens)

Get customer

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

Input parameters:

- `person_id` (integer, required): Customer person id (find it with phppos_list_customers).

### `phppos_list_suppliers` (~133 tokens)

List suppliers

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

Input parameters:

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

### `phppos_get_supplier` (~46 tokens)

Get supplier

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

Input parameters:

- `person_id` (integer, required): Supplier person id (find it with phppos_list_suppliers).

### `phppos_list_employees` (~122 tokens)

List employees

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.

Input parameters:

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

### `phppos_list_invoices` (~156 tokens)

List invoices

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.

Input parameters:

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

### `phppos_list_expenses` (~138 tokens)

List expenses

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

Input parameters:

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

### `phppos_list_gift_cards` (~92 tokens)

List gift cards

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

Input parameters:

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

### `phppos_get_gift_card` (~54 tokens)

Get gift card

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

Input parameters:

- `giftcard_number` (string, required): Gift card number or id.

### `phppos_list_appointments` (~136 tokens)

List appointments

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

Input parameters:

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

### `phppos_list_reports` (~116 tokens)

List reports

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.

Input parameters:

- `search` (string): Only reports whose key, description or inputs contain this text.

### `phppos_run_report` (~262 tokens)

Run report

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, supplier_id, customer_id, employee_id. A scoped key needs the Reports module plus that report's view permission. GET /reports/{report_key}.

Input parameters:

- `limit` (integer): Rows per page, 1-500 (default 100).
- `offset` (integer): Rows to skip (default 0). Pass the previous reply's next_offset (paging.next_offset for a report).
- `params` (object): 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.
- `report_key` (string, required): Report key from phppos_list_reports (for example summary_sales or inventory_low).

### `phppos_create_customer` (~241 tokens)

Create customer

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.

Input parameters:

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

### `phppos_update_customer` (~243 tokens)

Update 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}.

Input parameters:

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

### `phppos_create_item` (~248 tokens)

Create item

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.

Input parameters:

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

### `phppos_update_item` (~283 tokens)

Update item

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}.

Input parameters:

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

### `phppos_create_expense` (~211 tokens)

Create expense

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.

Input parameters:

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

## Diagnostics

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

## Score history

- 2026-10-25: 62
- 2026-10-24: 62

## Common questions

### What is the PHP Point of Sale MCP by usefulapi server?

PHP Point of Sale MCP by usefulapi is listed in the public MCP registry as io.usefulapi/php-point-of-sale. Read PHP Point of Sale items, sales, customers and 138 reports; manage customers, items, expenses. This page covers its hosted endpoint (https://php-point-of-sale.usefulapi.io/mcp).

### Is the PHP Point of Sale MCP by usefulapi server safe to use?

PHP Point of Sale MCP by usefulapi scores 62 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 PHP Point of Sale MCP by usefulapi server expose?

PHP Point of Sale MCP by usefulapi exposes 26 tools: phppos_list_locations, phppos_list_items, phppos_get_item, phppos_list_categories, phppos_list_item_kits, and 21 more. Their descriptions and schemas cost roughly 3,847 tokens of context every time the server is loaded.

### Does the PHP Point of Sale MCP by usefulapi server require authentication?

Yes. PHP Point of Sale MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the PHP Point of Sale MCP by usefulapi server still maintained?

PHP Point of Sale MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 25 October 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://php-point-of-sale.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/php-point-of-sale/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-php-point-of-sale/php-point-of-sale.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-php-point-of-sale/php-point-of-sale.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-php-point-of-sale/php-point-of-sale