com.insightfulpipe/magento
Magento MCP by InsightfulPipe
Is the Magento MCP by InsightfulPipe MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Hosted Magento MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error": "invalid_token", "error_description": "Authentication failed. The provided bearer token is invalid, - Endpoint
- https://magento.insightfulmcp.com/ (streamable-http)
- Host
- magento.insightfulmcp.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://magento.insightfulmcp.com/ registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server magento.insightfulmcp.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp_connection.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/Insightful-Pipe/magento-mcp-server
- Website
- https://insightfulpipe.com/mcp-servers/magento
- Registry
- active, updated 2026-10-21 · registry entry
Compare this server with others.
More servers
Servers that mention magento.
- com.expandingweb/agentic-commerce-readiness · alive
- com.expandingweb/nord-trail-store · alive
- com.packagento/mcp · needs auth
- io.github.Servicedsi/123elec-mcp · alive
- magento.watch watch.magento/magento-watch · alive
- io.github.jigarkkarangiya/adobe-commerce-docs-mcp · alive
- Magento Cloud MCP Server io.github.juan-cinto-infracommerce/magento-cloud · alive
- io.github.michalper/mcp-magento-audit · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.