Bazos MCP Server

Created By
progresaka year ago
A TypeScript-based MCP server for scraping graphics card listings from Bazos.cz marketplace
Overview

what is Bazos MCP Server?

Bazos MCP Server is a TypeScript-based Model Context Protocol (MCP) server designed for scraping real-time graphics card listings from the Bazos.cz marketplace.

how to use Bazos MCP Server?

To use the Bazos MCP Server, clone the repository, install the dependencies, and start the server. You can then integrate it with MCP-compatible AI assistants to search for graphics card listings.

key features of Bazos MCP Server?

  • Real-time scraping of graphics card listings from Bazos.cz
  • Returns structured data including title, price, location, URL, image URL, and description
  • Integration with Claude and other MCP-compatible AI assistants
  • Clean TypeScript implementation

use cases of Bazos MCP Server?

  1. Searching for the latest graphics card deals on Bazos.cz
  2. Integrating with AI assistants to provide users with real-time graphics card information
  3. Automating the retrieval of graphics card listings for market analysis

FAQ from Bazos MCP Server?

  • Can I use this server with any AI assistant?

Yes! The server is compatible with any MCP-compatible AI assistant.

  • Is the Bazos MCP Server free to use?

Yes! The server is open-source and free to use under the MIT License.

  • What programming language is used for this project?

The server is implemented in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
progresak
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
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)

2 days ago