Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Payments & trading
Read items, stock, customers and sales orders; create and update customers in Heartland Retail.
1 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Heartland Retail MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http heartland-retail-mcp-by-usefulapi https://heartland-retail.usefulapi.io/mcpCapabilities
Create a customer. Give a first name or a last name (or both). Returns the new customer id. Heartland Retail: POST /api/customers.
DiscoveredGet one customer by id: name, email, default address ids, custom fields and loyalty points. Heartland Retail: GET /api/customers/{customer_id}.
DiscoveredGet one gift card by its card number: value and status. Heartland Retail: GET /api/gift_cards/{gift_card_number}.
DiscoveredGet one item by id: cost, price, financial class and primary vendor. Heartland Retail: GET /api/items/{item_id}.
DiscoveredGet one sales order by id. Heartland Retail: GET /api/sales/orders/{order_id}.
DiscoveredSearch customers by name, email or a JSON filter. Heartland Retail: GET /api/customers.
DiscoveredShow stock quantities and values, optionally grouped (for example by item_id or location_id) and filtered to one item. Heartland Retail: GET /api/inventory/values.
DiscoveredSearch the store's items (products) by text or JSON filter, with cost, price and vendor ids. Heartland Retail: GET /api/items.
DiscoveredList the store's locations (stores, warehouses) with their ids. Heartland Retail: GET /api/locations.
DiscoveredSearch sales invoices by text or JSON filter. Heartland Retail: GET /api/sales/invoices.
DiscoveredList the lines (items, quantities, prices) of one sales order. Heartland Retail: GET /api/sales/orders/{order_id}/lines.
DiscoveredSearch sales orders by text or JSON filter (for example a status). Shows customer, status, shipping and totals. Heartland Retail: GET /api/sales/orders.
DiscoveredSearch point-of-sale tickets (till sales) by text or JSON filter. Heartland Retail: GET /api/sales/tickets.
DiscoveredSearch purchasing vendors (suppliers) by text or JSON filter. Heartland Retail: GET /api/purchasing/vendors.
DiscoveredChange the name or email of one customer. Only the fields you give change. Heartland Retail: PUT /api/customers/{customer_id}.
DiscoveredShow the Heartland Retail user behind the API token, and confirm the token works. Use it first when a call returns 401 or 403. Heartland Retail: GET /api/system/whoami.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 196 ms | 16 |