Diff and sync Shopify stores: dry-run plans, cross-store ID remapping, never deletes.
OLTechX is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search Bulgarian tech listings, real used prices per model, GPU FPS estimates and PC build checks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http oltechx-mcp https://www.oltechx.com/mcp
# 2 — ask your agent for something these tools do
# search_listings, get_listing, list_categories and 6 more
OLTechX costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http oltechx-mcp https://www.oltechx.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search open listings (offers) on OLTechX, the Bulgarian tech marketplace. Free-text query in Bulgarian or English (e.g. 'RTX 3060', 'iPhone 13 128GB', 'PS5'), with optional category, condition, city and EUR price range. Returns up to 24 results per page with price, condition, city and URL. When nothing matches it returns similar models that have listings, and always an alert link so the user can b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free text, e.g. 'RTX 4070', 'Ryzen 5 5600', 'MacBook Air M1' |
| category | string | no | Category slug from list_categories, e.g. 'videokarti', 'procesori', 'telefoni' |
| condition | string | no | — |
| city | string | no | Bulgarian city name in Cyrillic, e.g. 'София', 'Пловдив', 'Варна' |
| min_price_eur | number | no | — |
| max_price_eur | number | no | — |
| sort | string | no | 'deal' = best price compared to the usual price for the model |
| page | integer | no | — |
Full public details of one listing by id: description, price, condition, specs, delivery, seller type, photos and URL. Phone numbers and emails stay hidden (they are shown on the site after sign-in).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Listing id from search_listings |
All categories with slugs and current listing counts. Use the slug in search_listings.
No parameter schema on file.
Find catalog models (CPUs, graphics cards, phones, consoles) by name. Returns slugs to use with get_model_prices, estimate_fps and check_build.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | e.g. 'RTX 3060', 'Ryzen 7 5800X3D', 'iPhone 13' |
| kind | string | no | — |
| limit | integer | no | — |
What a model really costs in Bulgaria: used and new price range and median from open listings and real sales in the last 180 days, plus official specs, gaming score and the cheapest open listings. Accepts a slug or a name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| model | string | yes | Slug or name, e.g. 'rtx-3060' or 'GeForce RTX 3060' |
| kind | string | no | — |
Average FPS of a graphics card (optionally with a specific CPU) at 1080p, 1440p and 4K in games measured by published benchmarks (ComputerBase, HWBen) or estimated from official requirements. Also says whether the CPU or GPU limits performance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| gpu | string | yes | Graphics card slug or name, e.g. 'RTX 4060' |
| cpu | string | no | Processor slug or name; defaults to a Ryzen 7 9800X3D reference |
| game | string | no | Game slug or name from list_games; omit for all measured games |
| resolution | string | no | — |
Games with FPS data: measured in published tests or estimated from the publisher's official requirements.
No parameter schema on file.
Get a link that lets the user follow a search on OLTechX: after a free signup (or sign-in) the search is saved and they receive an email and push notification for every new matching listing. Use when nothing fits now, or the user wants to wait for a better price. Does not save anything by itself.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | What to watch for, e.g. 'RTX 4070' |
| category | string | no | — |
| condition | string | no | — |
| city | string | no | — |
| min_price_eur | number | no | — |
| max_price_eur | number | no | — |
Check whether PC parts fit together (socket, chipset, RAM type, case and cooler clearance, power) and get the recommended PSU wattage. CPU and GPU can be catalog model names or slugs; any part can be a listing id from search_listings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| cpu | string | no | — |
| gpu | string | no | — |
| motherboard | string | no | Listing id |
| ram | string | no | Listing id |
| storage | string | no | Listing id |
| psu | string | no | Listing id |
| case | string | no | Listing id |
| cooler | string | no | Listing id |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OLTechX or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_listings | no tags | |
| get_listing | no tags | |
| list_categories | no tags | |
| find_models | no tags | |
| get_model_prices | no tags | |
| estimate_fps | no tags | |
| list_games | no tags | |
| create_search_alert | no tags | |
| check_build | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish OLTechX can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.