Home / MCP registry index / io.usefulapi/myonlinestore

MyOnlineStore MCP by usefulapi

io.usefulapi/myonlinestore in the official MCP registry. Endpoint https://myonlinestore.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read orders, articles, customers, discount codes and newsletter subscribers in MyOnlineStore.

We read its 20 tools on 2026-11-05. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http myonlinestore https://myonlinestore.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "myonlinestore": {
      "url": "https://myonlinestore.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"myonlinestore","type":"http","url":"https://myonlinestore.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

myonlinestore_get_store myonlinestore_list_shipping_methods myonlinestore_list_articles myonlinestore_get_article myonlinestore_count_articles myonlinestore_list_categories myonlinestore_get_category myonlinestore_list_category_articles myonlinestore_list_customers myonlinestore_get_customer myonlinestore_list_customer_addresses myonlinestore_list_orders myonlinestore_get_order myonlinestore_count_orders myonlinestore_list_order_payments myonlinestore_list_discount_codes myonlinestore_get_discount_code myonlinestore_list_newsletter_subscribers myonlinestore_get_newsletter_subscriber myonlinestore_count_newsletter_subscribers

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-05): c8dd29097cb3d903. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-myonlinestore/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-myonlinestore)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.