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.
Available components
Last scanned (2 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 25 Oct 2026.
Category E-commerce
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 26 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.2.2 → 1.2.3 functional
- Server version: 1.2.0 → 1.2.2 functional
- 24 Oct 26 62
First indexed and scored.
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 25 Oct 2026 · Probed https://php-point-of-sale.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 php-point-of-sale.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://php-point-of-sale.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://php-point-of-sale.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://php-point-of-sale.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://php-point-of-sale.usefulapi.io/mcp |
| Authorisation server | https://php-point-of-sale.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://php-point-of-sale.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/php-point-of-sale/ |
| http (plaintext) | http://php-point-of-sale.usefulapi.io/mcp | Inconclusive | 302 | http://php-point-of-sale.usefulapi.io/mcp |
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 →
phppos_create_customer Create customer ~241
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| string | – | Email address. | |
| first_name | string | yes | 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. |
No output schema declared.
No examples provided.
phppos_create_expense Create expense ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category_id | integer | – | Expense category id. |
| expense_amount | number | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
phppos_create_item Create item ~248
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
phppos_get_customer Get customer ~65
One customer by person id: contact details, tier, tax settings, balance, credit limit, points, notes and custom fields. GET /customers/{person_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | integer | yes | Customer person id (find it with phppos_list_customers). |
No output schema declared.
No examples provided.
phppos_get_gift_card Get gift card ~54
One gift card by its card number (or id): remaining value, customer and status. GET /giftcards/{giftcard_number}.
| Name | Type | Req | Description |
|---|---|---|---|
| giftcard_number | string | yes | Gift card number or id. |
No output schema declared.
No examples provided.
phppos_get_item Get item ~68
One inventory item by id: prices, tax settings, category, supplier, tags, attributes, variations, tier pricing and per-location settings. GET /items/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | integer | yes | PHP Point of Sale item id (find it with phppos_list_items). |
No output schema declared.
No examples provided.
phppos_get_receiving Get receiving ~56
One receiving by id: supplier, items, quantities, costs and payments. GET /receivings/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| receiving_id | integer | yes | Receiving id (find it with phppos_list_receivings). |
No output schema declared.
No examples provided.
phppos_get_sale Get sale ~81
One sale by id with line items, payments, taxes, customer and employee (verbosity full by default). GET /sales/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| sale_id | integer | yes | PHP Point of Sale sale id (the number on the receipt; find it with phppos_list_sales). |
| verbosity | string | – | minimal, medium or full (default). |
No output schema declared.
No examples provided.
phppos_get_supplier Get supplier ~46
One supplier by person id. GET /suppliers/{person_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| person_id | integer | yes | Supplier person id (find it with phppos_list_suppliers). |
No output schema declared.
No examples provided.
phppos_list_appointments List appointments ~136
List appointments (bookings) with customer, employee, service, start and end time, optionally within a time window. GET /appointments.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_categories List categories ~93
List item categories with their ids. Use the ids to filter items or to file a new item. GET /categories.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_customers List customers ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_employees List employees ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_expenses List expenses ~138
List recorded expenses with type, description, date, amount, tax, payment type, category and location. GET /expenses.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_gift_cards List gift cards ~92
List gift cards with number, description, remaining value, customer and whether inactive. GET /giftcards.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_invoices List invoices ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | customer = invoices to customers; supplier = invoices from suppliers. |
No output schema declared.
No examples provided.
phppos_list_item_kits List item kits ~106
List item kits (bundles of items sold together) with their prices. GET /item_kits.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_items List items ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_locations List locations ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_receivings List receivings ~134
List receivings (stock received from suppliers, purchase orders, transfers) with supplier, totals and items, by date range. GET /receivings.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_reports List reports ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Only reports whose key, description or inputs contain this text. |
No output schema declared.
No examples provided.
phppos_list_sales List sales ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_list_suppliers List suppliers ~133
List or search suppliers with contact details, company, account number and balance. GET /suppliers.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
phppos_run_report Run report ~262
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Report key from phppos_list_reports (for example summary_sales or inventory_low). |
No output schema declared.
No examples provided.
phppos_update_customer Update customer ~243
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| 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 | yes | 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. |
No output schema declared.
No examples provided.
phppos_update_item Update item ~283
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · php-point-of-sale.usefulapi.io
claude mcp add --transport http io-usefulapi-php-point-of-sale 'https://php-point-of-sale.usefulapi.io/mcp'
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.