Vaper.club
REMOTE · API.VAPER.CLUB · 3 COMPONENTS
Read-only vape industry data: posts, brands, shops, product search, comparison and reviews.
Available components
Last scanned (13 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1652 tokens (~127/item across 13 items; 9 tools + 4 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://api.vaper.club/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.vaper.club | CN=YE2,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 65beda42f1174f88e7b6e2e93bf24903d68 |
| SANs: api.vaper.club | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.vaper.club. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| club. | DS published | 679 | 13 | Verified |
| vaper.club. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.vaper.club/mcp | Verified | 200 | |
| http (plaintext) | http://api.vaper.club/mcp | HTTPS enforced | 301 | https://api.vaper.club/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_products ~230
Compare offers for the same product model. Takes the same filters as search_products, identifies the best-matching standardized model, then returns up to 10 shop products of that model sorted by price so shops, prices, stock and ratings can be compared. Returns a warning and no products when no model can be identified. Provides objective product data and user feedback for adults only; it does not provide guidance on circumventing age verification, purchase restrictions or other legal limits.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_name | string|null | – | Optional brand name. |
| category_name | string|null | – | Optional product category name or code. |
| country | string|null | – | Optional ISO 3166-1 alpha-2 country code of the shop location. |
| language | string|null | – | Optional language code. |
| limit | integer|null | – | Maximum number of products, 1-10. Default 10. |
| model_name | string|null | – | Optional model name. |
| query | string | yes | Product name, brand, model or search keywords. Required. |
| shop | string|null | – | Optional shop name used to find the anchor product. |
No output schema declared.
No examples provided.
get_brand_details ~124
Get a brand profile: description, official website, company, aliases, rating, categories and the product models listed under the brand. Identify the brand with brand_id (from search_brands), slug, or brand_name.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | integer|null | – | Brand id returned by search_brands. |
| brand_name | string|null | – | Brand name, used when no id or slug is known. |
| language | string|null | – | Optional language code. |
| slug | string|null | – | Brand slug in the form {id}-{text}, as used in the source URL. |
No output schema declared.
No examples provided.
get_latest_posts ~144
Get the latest published Vaper.club posts (news, reviews, guides). Returns title, slug, short summary, category, publish/update time and source URL; not the full article text. Use when users ask for recent vape industry news or articles.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | Optional post category code, for example news or review. |
| language | string|null | – | Optional language code such as en or de. Defaults to the site default language. |
| limit | integer|null | – | Number of posts, 1-50. Default 10. |
| since | string|null | – | Optional ISO 8601 date; only posts published on or after it are returned. |
No output schema declared.
No examples provided.
get_product_reviews ~232
Get review statistics and the newest user reviews for the best-matching product. Takes the same filters as search_products. The summary covers all reviews; the review list is only the latest sample (default 10, max 20) and must not be presented as the overall opinion. Provides objective product data and user feedback for adults only; it does not provide guidance on circumventing age verification, purchase restrictions or other legal limits.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_name | string|null | – | Optional brand name. |
| category_name | string|null | – | Optional product category name or code. |
| country | string|null | – | Optional ISO 3166-1 alpha-2 country code of the shop location. |
| language | string|null | – | Optional language code. |
| limit | integer|null | – | Number of reviews, 1-20. Default 10. |
| model_name | string|null | – | Optional model name. |
| query | string | yes | Product name, brand, model or search keywords. Required. |
| shop | string|null | – | Optional shop name. |
| sort_by | string|null | – | latest (default) or helpful. |
No output schema declared.
No examples provided.
get_shop_details ~114
Get a shop profile: description, locations, rating, main brands and categories. Identify the shop with shop_id (from search_shops), slug, or shop_name.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string|null | – | Optional language code. |
| shop_id | integer|null | – | Shop id returned by search_shops. |
| shop_name | string|null | – | Shop name, used when no id or slug is known. |
| slug | string|null | – | Shop slug in the form {id}-{text}, as used in the source URL. |
No output schema declared.
No examples provided.
search_brands ~133
Search vape brands on Vaper.club by name, alias or company name. Returns brand id, name, aliases, logo, official website and product count. At least one of query or category_name is required.
| Name | Type | Req | Description |
|---|---|---|---|
| category_name | string|null | – | Optional product category name or code to restrict brands that sell it. |
| language | string|null | – | Optional language code. |
| page | integer|null | – | Page number, starting at 1. |
| page_size | integer|null | – | Page size, 1-20. Default 10. |
| query | string|null | – | Brand name, alias or company name. |
No output schema declared.
No examples provided.
search_posts ~179
Search published Vaper.club posts by keyword (brand, model, topic). Returns paged post summaries with source URLs. Date filters apply to the returned page only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string|null | – | Optional post category code. |
| end_date | string|null | – | Optional end date (ISO 8601). |
| language | string|null | – | Optional language code such as en or de. |
| page | integer|null | – | Page number, starting at 1. |
| page_size | integer|null | – | Page size, 1-20. Default 10. |
| query | string | yes | Search keywords. Required. |
| sort_by | string|null | – | relevance (default) or latest. |
| start_date | string|null | – | Optional start date (ISO 8601). |
| type | string|null | – | Optional content type: article or video. |
No output schema declared.
No examples provided.
search_products ~266
Search products offered by shops on Vaper.club. Each result is one shop's product record with brand, model, category, shop, price range, stock status, variants, rating and source URL (no internal product ids). Use when users ask to find, identify or research vape products. Provides objective product data and user feedback for adults only; it does not provide guidance on circumventing age verification, purchase restrictions or other legal limits.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_name | string|null | – | Optional brand name; recognized names are applied as a filter. |
| category_name | string|null | – | Optional product category name or code. |
| country | string|null | – | Optional ISO 3166-1 alpha-2 country code of the shop location. |
| language | string|null | – | Optional language code. |
| model_name | string|null | – | Optional model name. |
| page | integer|null | – | Page number, starting at 1. |
| page_size | integer|null | – | Page size, 1-20. Default 10. |
| query | string | yes | Product name, brand, model or search keywords. Required. |
| shop | string|null | – | Optional shop name. |
| sort_by | string|null | – | relevance (default), latest, rating, reviews, price_asc or price_desc. |
No output schema declared.
No examples provided.
search_shops ~134
Search retail shops listed on Vaper.club by name/website and/or country. Returns public shop profile data: website, locations, product count and user rating. At least one of query or country is required.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string|null | – | Optional ISO 3166-1 alpha-2 country code, for example US. |
| language | string|null | – | Optional language code. |
| page | integer|null | – | Page number, starting at 1. |
| page_size | integer|null | – | Page size, 1-20. Default 10. |
| query | string|null | – | Shop name or website keyword. |
No output schema declared.
No examples provided.
How do I install the Vaper.club MCP server?
Vaper.club is a hosted endpoint at https://api.vaper.club/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.vaper.club
claude mcp add --transport http club-vaper-vaper-club 'https://api.vaper.club/mcp'
What is the Vaper.club MCP server?
Vaper.club is an MCP server listed in the public MCP registry as club.vaper/vaper-club. Read-only vape industry data: posts, brands, shops, product search, comparison and reviews. This page covers its hosted endpoint (https://api.vaper.club/mcp).
Is the Vaper.club MCP server safe to use?
Vaper.club scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vaper.club MCP server expose?
Vaper.club exposes 9 tools: get_latest_posts, search_posts, search_brands, get_brand_details, search_shops, and 4 more. Their descriptions and schemas cost roughly 1,556 tokens of context every time the server is loaded.
Does the Vaper.club MCP server require authentication?
No. We connected to Vaper.club without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vaper.club MCP server still maintained?
Vaper.club is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Vaper.club MCP server?
VerifyMCP ran 13 checks on Vaper.club, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.