Skip to main content
Glama
op-enny

Fake Store API MCP Server

by op-enny
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Fake Store API MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Dynamics 365 Commerce

      jiantmo
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Dynamics 365 Commerce systems through 125+ tools covering customer management, sales orders, cart operations, product searches, inventory tracking, and store operations. Provides comprehensive mock data for development and testing purposes.
      3
      -

    • MockMCP

      K-Cupples
      A
      license
      Not graded
      quality
      D
      maintenance
      Hosted MCP endpoint that returns realistic fake data for prototyping agents. Paste one URL into Claude Code, Cursor, or Claude Desktop — 12 pre-built tools covering users, products, orders, events, email, and knowledge base search. No signup, no config, no auth. Built for developers who want to prototype agent workflows before wiring up a real backend.
      MIT

    • Commerce-MCP

      sinmb79
      A
      license
      D
      quality
      D
      maintenance
      Enables natural-language control of e-commerce operations including product management, order processing, inventory tracking, customer service, content generation, and advertising analytics through 15 integrated MCP tools. Provides a local-first commerce automation solution with SQLite storage and extensible channel adapters for end-to-end online store workflows.
      15
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 18 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific resources (cart, product, user) and actions (add, delete, get, update), with no overlap or ambiguity. For example, fakestore_get_products and fakestore_get_products_by_category are clearly differentiated by scope.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with the prefix 'fakestore_' and snake_case throughout, such as fakestore_add_product and fakestore_get_user_carts. There are no deviations in naming conventions.

    Tool Count4/5

    With 18 tools, the count is slightly high but reasonable for a store API covering three main resources (cart, product, user) with full CRUD operations and additional query tools. It feels comprehensive without being overly bloated.

    Completeness5/5

    The tool set provides complete CRUD coverage for carts, products, and users, along with additional query tools like get_categories and get_products_by_category. There are no obvious gaps, enabling agents to handle all core store operations effectively.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources