Market Price Comparison Server (MCP)

Created By
Eneswunbeatena year ago
This tool helps you find the store offering the best price for a specific product among various chain markets in Turkey. The system fetches real-time data from different markets and returns the best price along with the corresponding store name.
Overview

What is Market Price Comparison Server (MCP)?

Market Price Comparison Server (MCP) is a .NET-based application that helps users find the best prices for grocery products across various chain markets in Turkey by fetching real-time data.

How to use Market Price Comparison Server (MCP)?

To use MCP, integrate it with MCP-compatible client applications like Claude or Cursor. Enter the product name in Turkish, and the tool will search for the best price across major Turkish grocery markets.

Key features of Market Price Comparison Server (MCP)?

  • Real-time price tracking for grocery products in Turkish markets.
  • Identification of the most affordable prices with multi-market comparison.
  • Integration capabilities with MCP-compatible clients.

Use cases of Market Price Comparison Server (MCP)?

  1. Finding the best prices for everyday grocery items.
  2. Comparing prices across multiple stores to save money.
  3. Assisting consumers in making informed purchasing decisions.

FAQ from Market Price Comparison Server (MCP)?

  • Can MCP find prices for all grocery products?

Yes! MCP can search for a wide range of grocery products available in Turkish markets.

  • Is there a cost to use MCP?

No! MCP is free to use for everyone.

  • How accurate is the price information provided by MCP?

MCP provides real-time data, ensuring high accuracy, but it may vary based on market updates.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Eneswunbeaten
Star
2
Language
C#
License
-

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago