Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Vaper.club 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
Read-only vape industry data: posts, brands, shops, product search, comparison and reviews.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user vaper-club-mcp '--' npx -y vaper-club-mcp
# 2 — ask your agent for something these tools do
# search_brands, get_brand_details, get_product_categories and 7 more
Vaper.club 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. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user vaper-club-mcp '--' npx -y vaper-club-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://api.vaper.club/mcp: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http vaper-club-mcp https://api.vaper.club/mcpNothing is required, but it can take VAPER_CLUB_API_BASE_URL (Vaper.club Public API base URL.), VAPER_CLUB_API_TIMEOUT (API request timeout in seconds (0-300).), VAPER_CLUB_API_KEY (Optional bearer token for the Vaper.club Public API.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
10 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Search vape brands by name keywords or by category name. At least one of query or category_name is required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Brand name keywords. |
| category_name | string | no | Only brands in this category. |
| language | yes | — | |
| page | yes | — | |
| page_size | yes | — |
Get a brand profile: description, official website, aliases, categories and models. Identify the brand by brand_id, slug or brand_name (at least one).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brand_id | integer | no | Numeric brand id from a previous result. |
| slug | string | no | Brand slug. |
| brand_name | string | no | Brand name. |
| language | yes | — |
List the product categories supported by Vaper.club. Use the names as category or category_name filters in other tools.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | yes | — |
Get the latest Vaper.club posts (news, reviews, guides) as summaries.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Number of posts, 1-50. |
| category | string | no | Post category. |
| since | string | no | Only posts published after this date (ISO 8601). |
| language | yes | — |
Keyword search over Vaper.club posts (articles and videos).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search keywords. |
| category | string | no | Post category. |
| type | string | no | Post type. |
| sort_by | string | no | Sort order (default relevance). |
| start_date | string | no | Filter start date; applies to the returned page only. |
| end_date | string | no | Filter end date; applies to the returned page only. |
| language | yes | — | |
| page | yes | — | |
| page_size | yes | — |
Search retail shops by name keywords or country. At least one of query or country is required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Shop name keywords. |
| country | string | no | ISO 3166-1 alpha-2 country code. |
| language | yes | — | |
| page | yes | — | |
| page_size | yes | — |
Get a shop profile: locations, main brands and categories. Identify the shop by shop_id, slug or shop_name (at least one).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| shop_id | integer | no | Numeric shop id from a previous result. |
| slug | string | no | Shop slug. |
| shop_name | string | no | Shop name. |
| language | yes | — |
Search vape product offers from retail shops. Each result is one shop's offer with brand, model, category, price, stock status, variants, ratings and a sourceUrl on Vaper.club. Cite sourceUrl when using the data. Missing fields mean unknown, not zero.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sort_by | string | no | Sort order (default relevance). |
| page | yes | — | |
| page_size | yes | — |
Compare offers of the best-matching product model across shops, cheapest first. Use it for price and stock comparison of one model.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum offers to return, 1-10. |
Get the review summary (all reviews) and the newest or most helpful user reviews of the best-matching product.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum reviews to return, 1-20 (default 10). |
| sort_by | string | no | Review order (default latest). |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- 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 Vaper.club 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 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
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.
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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_brands | no tags | |
| get_brand_details | no tags | |
| get_product_categories | no tags | |
| get_latest_posts | no tags | |
| search_posts | no tags | |
| search_shops | no tags | |
| get_shop_details | no tags | |
| search_products | no tags | |
| compare_products | no tags | |
| get_product_reviews | 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
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.1. Pin a release below and the command asks for exactly that one.
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 Vaper.club 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.