Vinotify Logovinotify
Login

Vinotify and MCP: Bring Your Vinted Alerts into AI Tools

← Back to Blog

3 September 2026

Vinotify provides a direct Streamable HTTP MCP server for bringing your Vinted alerts into compatible AI tools. It uses a bearer token and keeps a clear boundary between your Vinotify account and the assistant.

The server exposes read tools for discovering searches and reading new matching listings. A token is read-only by default; if you explicitly create a write-scoped token and write tools are enabled, it can also create, update, pause, resume, or delete searches. Put the secret in your local MCP client configuration—not in an AI chat.

What the Vinotify MCP server can do

With a Pro integration token, the direct server provides:

  • Discover active searches with list_searches and read new items with get_new_items or whats_new.
  • Read matching listings with links, prices, markets, currencies, and available details.
  • Continue each event stream from a saved cursor; events are at-least-once, so clients should deduplicate event IDs.
  • Keep the token scoped to every search your account owns now and any searches you create later; clients can refresh discovery to pick up active searches as they change.

A simple way to think about it

  1. You create and manage searches in Vinotify; tokens are account-scoped, not selected per search.
  2. You create an integration token. It is read-only by default; if needed, you explicitly allow writes, and write tools still require the server feature flag.
  3. You put the token in your local client's Authorization: Bearer configuration for https://vinotify.me/api/v1/mcp. Token-free setup instructions can go to an assistant, but the secret should not be pasted into chat.
  4. The assistant uses the available MCP tools to read matches or, when enabled, create, update, pause, resume, or delete searches; you remain in control.

Read-only by default, with a narrow optional write scope

A standard token can only use the read tools. An optional write-scoped token can use create_search, update_search, pause_search, resume_search, and delete_search when write tools are enabled and Vinotify's plan rules allow it. No token can:

  • Erase a search's item history. A deleted search stops at once, but its past matches are kept.
  • Change your subscription, open billing or payment details, or make purchases.
  • Read your profile or log in as you.
  • Buy an item through Vinotify or control your Vinted account.

Writes still use Vinotify's existing search rules, plan caps, intervals, market restrictions, and rate limits. A token never broadens account ownership: it can act only on searches owned by its account.

Useful ways to use your alert data

  • Ask for a shortlist of matches below a target price.
  • Compare recent listings across your active searches or Vinted markets.
  • Summarise whats_new and surface only the items that fit your priorities.
  • When write scope is deliberately enabled, ask the assistant to create, update, pause, or resume a search within Vinotify's rules.

Built with a small security footprint

  • The MCP server is available to Pro accounts, and bearer tokens are checked against account-owned searches on every request.
  • The full token is shown once. Vinotify stores only a one-way digest, so it cannot reveal the original token later.
  • Tokens cover all current and future searches on the same account. They are read-only by default; write scope is explicit and separate.
  • Keep the secret in local client configuration, never in AI chat, tickets, logs, or URLs; revoke a token any time from Integrations.

Getting started

Vinotify's direct endpoint is https://vinotify.me/api/v1/mcp, a Streamable HTTP, POST-only JSON-RPC server. Use an MCP client that supports bearer headers; Claude Code, Cursor, and Claude Desktop can connect, while Claude.ai web and ChatGPT connectors are not supported yet.

  1. Sign in to a Vinotify Pro account, open Integrations, and create a token. Leave write access off unless you need search writes.
  2. Use the token-free setup instructions with your assistant or client; they can explain the connection without seeing your credential.
  3. Insert the secret yourself into the MCP client's local configuration as Authorization: Bearer <token> for the endpoint. Never paste the secret into an AI chat; it is shown only once.
  4. Connect and try list_searches. Revoke the token from Integrations when it is no longer needed or may have been exposed.

Read tools are available with a default read-only token. Write tools are off by default: create_search, update_search, pause_search, resume_search, and delete_search appear only for a write-scoped token while the server write flag is enabled.

Open Integrations →Create a Vinted alert →

Frequently asked questions

What is the Vinotify MCP endpoint URL?
https://vinotify.me/api/v1/mcp. It is a stateless JSON-RPC endpoint that accepts POST requests and authenticates with a Pro account integration token sent as a bearer token.
Which MCP tools does Vinotify expose?
Three read tools — list_searches, get_new_items and whats_new — plus five write tools, create_search, update_search, pause_search, resume_search and delete_search, which require a write-scoped token and are enabled server-side.
Is the MCP connection read-only?
Yes by default. A token is read-only unless write access is chosen explicitly when it is created, so connecting an assistant cannot change your searches unless you granted that scope.
Can I use it with Claude, ChatGPT or a coding agent?
Any client that speaks MCP over Streamable HTTP can connect. Put the endpoint and your token in that client's local configuration. The token is shown once when created and can be revoked at any time from the Integrations page.