Skip to main content
Glama
figurophobia

vinted-mcp

by figurophobia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vinted-mcp

No user-submitted related servers found.

    Related Servers

    • vinted-mcp-server

      Rbillon59
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search, browse, and discover second-hand items on Vinted via a Model Context Protocol server.
      5
      4 npm
      MIT

    • vinted-search-mcp

      marcocot
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables searching Vinted marketplaces for second-hand listings and reading detailed item information, read-only, without buying or contacting sellers.
      1
      MIT

    • marktplaats-mcp

      jasp-nerd
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to search and monitor Dutch and Belgian classifieds (Marktplaats and 2dehands) for listings, seller profiles, and categories.
      8
      52 PyPI
      4
      MIT

    • marktplaats-2dehands-mcp

      RT-codes
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to search and retrieve classified listings from marktplaats.nl and 2dehands.be, including details, seller info, categories, and saved searches, with optional authenticated access to messages, listings, favorites, and bids.
      14
      1
      MIT

    • Jiji MCP

      atomicman57
      A
      license
      A
      quality
      A
      maintenance
      Enables extension-free sign-in to a marketplace and gives AI agents tools for searching and paginating listings, comparing sellers and asking prices, reading inbox conversations, and preparing owner-approved seller messages with a WhatsApp handoff. It can be shared across local agents over a Unix socket or remote agents through an authenticated OAuth relay, without ever exposing passwords or cookies.
      21
      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

    C2.6/5.0

    Scored across 29 tools

    Disambiguation3/5

    Most tools target distinct resources, but several clusters overlap: item_stats already reports 'who favourited it' alongside list_item_likers, suggest vs suggest_category vs search all answer 'find the right thing', and find_brand / search_filters / listing_options all expose attribute metadata. Descriptions do help sort these out, but an agent must read carefully before choosing.

    Naming Consistency3/5

    Everything is snake_case, which is good, but the verb style is mixed: prefixed verbs (find_city, list_favorites, get_item, search_filters) sit next to bare nouns (wallet, whoami, search, suggest, item_stats, seller_items, my_items, unread_count, session_status). It stays readable, but there is no single predictable pattern to infer a new tool's name from.

    Tool Count2/5

    At 29 tools this is heavy for a read-only marketplace client, and the surface is spread thin across search metadata, profile, wallet, messaging, offers, and selling. Several lookup helpers (find_city, find_brand, listing_options) exist purely to feed write tools that are not present, so they do not earn their place in this set.

    Completeness2/5

    Multiple descriptions reference tools that do not exist in this set — respond_offer/send_offer (from get_offer_status), publish_item (from listing_options and find_brand), and update_profile (from find_city) — creating hard dead ends for any agent that follows them. Reading is broadly covered (search, item, seller, inbox, transactions, wallet), but the offer/listing lifecycle has no completion path.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources