Finance · Remote MCP server
PrestaShop MCP Connector
Query a PrestaShop store from an AI assistant: orders, invoices, unpaid orders, customers, stock.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
net.sarmate.studio/prestashop-connector- Version
- 1.5.0
- Status
- Active
- Category
- finance
- Transport
- Streamable HTTP
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- net.sarmate.studio
- Namespace
- Namespace verified by the MCP Registry via the domain studio.sarmate.net or a parent domain of it · how
- Website
- www.studio.sarmate.net/mcp/essai/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://{store_domain}/module/studiomcp/endpoint | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect PrestaShop MCP Connector
PrestaShop MCP Connector is a remote MCP server: there is nothing to install. Its endpoint is https://{store_domain}/module/studiomcp/endpoint, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {store_domain}.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More finance servers
| Server | Runs |
|---|---|
| PreReasonBitcoin and macro market briefings for AI agents: trend signals, regimes, liquidity and ETF flows. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Presidio Hardened X402 MCPPre-payment safety gate for x402 agents: PII screening, spend policy, replay checks before signing. | Local · stdio |
| presign-guardPre-sign, token and approval checks for agents: green/orange/red for signatures, tokens, wallets. | Remote · HTTPLive check: ✓ handshake |
| presign-guard walletA wallet with spending limits for agents: pay x402 APIs, send USDC, phone approval over the limit. | Local · stdio |
| PRG Risk OracleMarket regime, 7-dimension risk vectors and payment hazard grades. Abstains when data is thin. | Remote · HTTPLive check: ✓ handshake |
| Price Data MCPLive market prices and candles for AI agents (200+ coins). Data only, no trading advice. | Local · stdio |
| PriceFeedReal-time & historical crypto and fiat exchange rates, median-aggregated from multiple sources. | Remote · HTTPLive check: ✓ handshake |
| PriorSpend gate agents call before money moves. Buy with Stripe Checkout. Paid only when Stripe says so. | Remote · HTTPLive check: ✓ handshake |