DataDive vs PoloPan Fashion MCP Server
A side-by-side look at the DataDive and PoloPan Fashion MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose DataDive for e-commerce work as a local process; choose PoloPan Fashion MCP Server for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose DataDive when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
DATADIVE_API_KEY. - You want tools like
list_niches, get_niche_keywords, list_keyword_exclusions.
Choose PoloPan Fashion MCP Server when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You want tools like
region.get_current, region.set_current, region.list_supported.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 63/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | DATADIVE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 43 | 19 |
| Full listing | View DataDive | View PoloPan Fashion MCP Server |
Tools & capabilities
DataDive tools 43
list_nichesUse this first when the user asks about their niches, or to find a `nicheId` for use with `get_niche_keywords`, `get_niche_competitors`, or `get_ranking_juice`. Retrieves a paginated list of Niches, newest dive first. Each Niche represents a market segment or product category being tracked. Returns nicheId, heroKeyword, nicheLabel, marketplace (com/uk/de/...), and latestResearchDate per niche, plus pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev). Narrow with `searchText` (label/keyword) or `searchAsin` (a competitor ASIN) instead of scanning pages; a page holds at most 50 niches, so the full list of a large account needs several calls.get_niche_keywordsUse this when the user asks about keywords, search terms, or search volume for a niche. Retrieves the master keyword list for the specified Niche — the relevant search terms monitored for ranking and performance metrics. For each keyword, returns search volume, relevancy (numeric score or "Outlier"), and competitor ASIN organic ranks (asinRanks: { ASIN -> rank | null }), plus `origin`: `mkl` (found by the dive), `manual` (added by hand with `add_niche_keywords`), `outlier` / `residue` (moved in from those lists). Only `manual`, `outlier` and `residue` keywords can be taken out with `remove_niche_keywords`. Keywords hidden by the niche's keyword exclusions are not listed; see `list_keyword_exclusions`. Also returns the latestResearchDate.list_keyword_exclusionsUse this to see which keywords are hidden from a niche's Master Keyword List, e.g. when a keyword the user expects is missing from `get_niche_keywords`. Returns the same lists the DataDive web app shows, oldest first: `exact` — each entry hides the one keyword that matches it exactly, with that keyword's `searchVolume` (0 when the niche has no such keyword); `phrase` — each entry hides every keyword that contains the phrase, with `excludedKeywordsCount` and the total `searchVolume` of the keywords it hides (not counting ones already excluded exactly). Exclusions hide keywords wherever they come from: the dive, the Outliers and Residue lists, and hand-added ones. Change them with `add_keyword_exclusions` and `remove_keyword_exclusions`.get_niche_rootsUse this when the user wants to find the highest-impact words across a niche's keywords, asks about 'keyword roots', or wants to prioritize terms for a listing. Retrieves the keyword lexical roots for the Niche — individual words or word-combinations extracted from the Master Keyword List (e.g. 'bluetooth headphones' yields roots 'bluetooth', 'headphones', 'bluetooth headphones'). Returns `roots` and `normalizedRoots` tables, each item with root, frequency (how many keywords contain it), broadSearchVolume (summed search volume of those keywords), and broadSearchVolumeRatio (0-1, relative to the top root), plus the per-keyword breakdowns and latestResearchDate.get_niche_competitorsUse this for competitor ASINs, product titles, BSR, sales/revenue benchmarks, or niche opportunity scoring. Retrieves the list of Competitors within the specified Niche along with Niche statistics. For the Niche: keyword statistics, opportunity evaluation, benchmark median values, and overall competitor strength assessment. For each Competitor: ASIN, product title, BSR, category and full category tree, sales, revenue, ratings, reviews, price, number of variations, image URL, total Ranking Juice, and ranking data. BSR supports ranking Competitors by sales position within mentioned category. For the Ranking Juice breakdown by title, bullets and description, use `get_ranking_juice`.get_ranking_juiceUse this when the user asks 'how do I rank higher', 'what's my ranking juice', or wants listing-optimization guidance. Retrieves the Ranking Juices for each Competitor within the specified Niche. Ranking Juice is DataDive's proprietary metric identifying the key factors driving search-ranking success for each Competitor's listing. Returns currentListing and optimizedListing breakdowns (rankingJuice + per-property contributions: title, bullets, description) plus per-competitor listing scores and the latestResearchDate.list_rank_radarsUse this to find a `rankRadarId` before calling `get_rank_radar_data`. Filter by `nicheId` if the user has already identified a niche. Retrieves a paginated list of Rank Radars — keyword-rank trackers monitoring organic and sponsored positions for specific ASINs over time. Each item includes id, status (ACTIVE, PAUSED or ARCHIVED), asin, marketplace, keywordCount, title, imageUrl, and summary metrics: top10KW, top10SV, top50KW, top50SV. Supports pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev); a page holds at most 50 Rank Radars, so a large account needs several calls.get_rank_radar_dataUse this to analyze keyword ranking trends over time. Requires startDate and endDate (yyyy-mm-dd), at most 90 days apart. Retrieves historical keyword ranking data for the specified Rank Radar within the date range. Without `currentPage` and `pageSize` it returns every active keyword in one result. To read one page instead — faster for large Rank Radars — pass `currentPage` and/or `pageSize` (max 100) and continue with `currentPage` + 1 while `hasNext` is true. The response carries currentPage, pageSize, total, lastPage, hasNext and hasPrev; `total` is the Rank Radar's active keyword count. Paused keywords are not included. Each keyword has id, keyword, searchVolume, relevancy, ranks (per-day { date, organicRank, sponsoredRank, impressionRank }), and `highlights` — the user tags on this keyword. Each `highlights` entry is the same object `list_rank_radar_tags` returns (id, title, color, description, startAt, endAt, type, krtId, krtKeywordId); its `id` is the `tagId` the tag-management tools take. A rank of 101 means the product was not in the top 100 results that day. For PPC metrics use `get_rank_radar_ppc_data`; for Search Query Performance use `get_rank_radar_sqp_data`. Use after `list_rank_radars` to discover a `rankRadarId`.get_rank_radar_sqp_dataUse this when the user asks how shoppers search, click, add to cart and buy for the keywords of a Rank Radar — Amazon's Search Query Performance (SQP) data, from Brand Analytics. Requires startDate and endDate (yyyy-mm-dd), at most 90 days apart; 30 days or less keeps it fast. Each keyword's metrics are aggregated over the range: searchQueryVolume and searchQueryScore; impressions, clicks, cart adds and purchases, each as the total across all sellers (`*TotalCount`), this ASIN family's count (`*AsinCount`) and its share (`*AsinShare`); click, cart-add and purchase rates; and ctr/cvr for the market (`*Total`) and for this ASIN family (`*Asin`). `numberOfDaysWithData` says how many days of the range had SQP data; metrics are null when there is none, which is normal for low-volume keywords, recent dates (Amazon publishes SQP with a delay) and sellers without Brand Analytics. Results are paged by keyword: `data` holds one page, and the response carries currentPage, pageSize, total, lastPage, hasNext and hasPrev. `total` is the Rank Radar's active keyword count; to read every keyword, call again with `currentPage` + 1 while `hasNext` is true, using `pageSize` 100 for large Rank Radars. Paused keywords are not included. Each call counts toward API usage and is rate limited (about 60 requests/minute). Use after `list_rank_radars` to discover a `rankRadarId`.get_rank_radar_ppc_dataUse this when the user asks about advertising (Sponsored Products) performance for the keywords of a Rank Radar. Requires startDate and endDate (yyyy-mm-dd), at most 90 days apart; 30 days or less keeps it fast. Each keyword's metrics are aggregated over the range: sponsoredRank (median; 101 means not in the top 100 sponsored results), impressionRank and impressionRankShare; how many exact, phrase, broad and auto campaigns target it; organicSales, ppcSales, ppcSpend, costPerClicks, clickThroughRate, conversionRate, totalClicks, totalImpressions, totalOrders and acos. Metrics are null or 0 when the seller runs no ads on a keyword. Set `includeCampaigns` for the per-campaign breakdown. Results are paged by keyword: `data` holds one page, and the response carries currentPage, pageSize, total, lastPage, hasNext and hasPrev. `total` is the Rank Radar's active keyword count; to read every keyword, call again with `currentPage` + 1 while `hasNext` is true, using `pageSize` 100 for large Rank Radars. Paused keywords are not included. Each call counts toward API usage and is rate limited (about 60 requests/minute). For the seller's campaigns as a whole, use `list_ppc_campaigns`. Use after `list_rank_radars` to discover a `rankRadarId`.list_rank_radar_tagsUse this to find a `tagId` before calling `update_rank_radar_tag`, `delete_rank_radar_tag`, `add_rank_radar_tag_search_terms` or `remove_rank_radar_tag_search_terms`. Returns the user tags ("highlights") on the specified Rank Radar, ordered by title (case-insensitive, ascending). Each row carries `id`, `title`, `color`, `description`, `startAt`, `endAt`, `createdAt`, and `keywordCount` — the number of Rank Radar keywords this tag is applied to. The system "paused" tag (the one the quota pauser writes with a reserved colour) is not listed and cannot be addressed from these tools. Supports pagination metadata (currentPage, pageSize, total, lastPage, hasNext, hasPrev); a page holds at most 50 tags.create_rank_radarUse this to start tracking organic and sponsored keyword rankings for an ASIN within a niche. ⚠️ Spends Search Term tokens (cost scales with `numberOfKeywords`) and cannot be undone — set `confirm: true` only after the user approves the cost. Not safe to retry: each call spends tokens again and creates a separate Rank Radar — if a call errors or times out, check `list_rank_radars` instead of re-calling. The first call previews the creation and may return `warnings` alongside the cost note — for example that this product family is already tracked by another Rank Radar. Show every warning `message` to the user verbatim, before asking them to confirm; do not summarise it or decide on their behalf. A warning never blocks creation. Returns the new `rankRadarId`; read its data later with `get_rank_radar_data`. Requires `asin`, `numberOfKeywords` (min 1), and a `nicheId` from `list_niches`.- +31 more on the listing page
PoloPan Fashion MCP Server tools 19
region.get_currentGet the currently active shopping destination country, currency code, symbol, phone code, and catalog scope mode from persistent local configuration (~/.polopan/region.json).region.set_currentSet the active shopping country/region using any natural country name, city (e.g. 'Dubai', 'London', 'California', 'Paris'), 2-letter ISO code ('US', 'GB', 'IN', 'AE', 'CA'), or currency ('USD', 'AED', 'GBP', 'EUR'). Saves to persistent local JSON (~/.polopan/region.json) so the user never needs to be asked again across turns and sessions.region.list_supportedSearch the 240+ supported destination countries with localized currency codes, symbols, flags, phone codes, and price groups from live platform settings.address.get_currentGet the default delivery/shipping address saved for the currently active region from local configuration (~/.polopan/region.json). WHEN TO USE (CRITICAL ANTI-SHORTCIRCUIT RULE): - ALWAYS call this BEFORE generating 1-click checkout links to check if the user already has a saved delivery address for their destination country. - If 'has_address' is false, DO NOT emit a naked checkout link. Prompt the user naturally for their shipping address (First Name, Street Address, City, Postal Code, Phone & Email) and save it using 'address.save'. - If 'has_address' is true, inform the user you are prefilling their saved address and proceed with checkout.address.saveSave a customer delivery shipping address mapped to the active region in ~/.polopan/region.json. Matches Flutter app (newapp) address schema: firstName, lastName, address1, address2, city, province, zip, country, phone, email, type.address.list_savedList all saved customer delivery addresses stored in ~/.polopan/region.json, optionally filtered by country.address.set_defaultSet an existing address as the default shipping address for its country in ~/.polopan/region.json.address.deleteDelete a saved delivery address by ID from ~/.polopan/region.json.products.search.textSearch PoloPan catalog products using a text keyword query with optional multi-attribute filters. Returns matching fashion items with available in-stock sizes, product specifications, shipping/return policies, discounted pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}). Automatically localized to active country / 240+ destination regions. PURPOSE & DISAMBIGUATION: - Primary text-based catalog search tool for fashion discovery across apparel, footwear, and accessories. - Distinct from 'products.search.image_url' / 'products.search.image_upload': Use this tool for textual queries and keyword filters, NOT for visual image search. - Distinct from 'products.search.alternatives': Use this tool for open discovery queries, NOT for finding direct visual substitutes of a known product handle. - Distinct from 'looks.curation.by_occasion': Use this tool to search individual products, NOT complete multi-piece outfit looks. WHEN TO USE: - When a user searches for clothing or fashion styles using keywords, brand names, colors, or categories (e.g. 'black leather jacket', 'floral summer midi dress', 'men linen shirts'). - When refining catalog searches with structured filters like price ranges, gender, sizes, country regions, or vendor brands. WHEN NOT TO USE: - Do NOT use when the user provides an image URL or image file (use 'products.search.image_url' or 'products.search.image_upload'). - Do NOT use when searching for cheaper/higher-end substitutes of a specific known product (use 'products.search.alternatives'). - Do NOT use to find curated complete occasion outfits (use 'looks.curation.by_occasion'). BEHAVIOR & SAFETY: - Read-only and idempotent with no persistent state modifications. - Automatically sanitizes and enriches product records with verified PoloPan short permalinks (https://s.polopan.com/p/{handle}), computed in-stock size lists, and human-readable shipping and return policy strings. - Handles pagination and multi-attribute filtering deterministically. PARAMETERS & CONSTRAINTS: - 'query' (string, required): Free-text search query or style keyword (e.g. 'black linen shirt', 'oversized hoodie'). - 'country' (string, optional): Target country name, city, currency, or ISO-2 code (e.g. 'US', 'United States', 'UK', 'Dubai', 'CA', 'IN'). Defaults to active saved region. - 'mode' (enum, optional): Catalog mode: 'global' (ships to country) or 'local' (domestic only). - 'page' (integer >= 1, default 1): Pagination page number. - 'page_size' (integer 1-100, default 20): Number of products returned per page. - 'sort_by' (enum, default 'relevance'): Ranking criterion ('relevance', 'price', 'title'). - 'sort_order' (enum, default 'desc'): Sort direction ('asc' for ascending, 'desc' for descending). - 'gender' (string, optional): Target demographic filter ('men', 'women', or 'unisex'). - 'size' (array of strings, optional): Size filter array (e.g. ['S', 'M', 'L', 'XL', '32', '40']). - 'price_min' (number, optional): Minimum price threshold in local currency. - 'price_max' (number, optional): Maximum price threshold in local currency. - 'vendor' (array of strings, optional): List of brand or vendor names to filter by. MANDATORY AGENT INSTRUCTIONS: 1. Always communicate available in-stock sizes, fast dispatch SLA, and return policy for each product (Negative return days = 'Exchange only |X| days'). 2. When presenting or shortlisting products, display the product specifications table (Fabric, Pattern, Collar, Sleeves, Fit, Care). 3. Return the clean base link (https://s.polopan.com/p/{handle}) during browsing. Provide direct checkout link (https://s.polopan.com/p/{handle}/{size_index}) ONLY after the user's size is finalized.products.search.image_urlSearch PoloPan catalog products using visual image similarity from a publicly accessible image URL with optional multi-attribute filters. Returns visually similar products with available sizes, pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}). Automatically localized to active country / 240+ destination regions. PURPOSE & DISAMBIGUATION: - Performs reverse visual search using computer-vision embeddings for a remote image URL. - Distinct from 'products.search.text': Use this tool when you have an image URL, NOT for textual keyword queries. - Distinct from 'products.search.image_upload': Use this tool for publicly hosted HTTP(S) image URLs, NOT for local file paths or base64 data. - Distinct from 'vision.outfit.detect_pieces': Use this tool to search catalog items matching an entire single-garment image, NOT for segmenting multi-garment influencer photos into bounding boxes. WHEN TO USE: - When the user shares a web link to an image (e.g. Pinterest, Instagram, blog post) and wants to find visually matching products in the PoloPan catalog. WHEN NOT TO USE: - Do NOT use when the image is stored on local disk or as base64 data (use 'products.search.image_upload'). - Do NOT use when searching by text descriptions (use 'products.search.text'). - Do NOT use when you need to crop/isolate individual outfit pieces from a full-body model photo (use 'vision.outfit.detect_pieces'). BEHAVIOR & SAFETY: - Read-only and idempotent with no persistent state modifications. - Downloads the image, generates visual embeddings, and retrieves ranked catalog matches. - Enriches all returned items with verified PoloPan purchase links and stock metadata. PARAMETERS & CONSTRAINTS: - 'image_url' (string, required): Publicly accessible HTTP(S) URL of the image to search for visual matches. - 'country' (string, optional): Target country name, city, currency, or ISO-2 code (e.g. 'US', 'United States', 'UK', 'Dubai', 'CA', 'IN'). Defaults to active saved region. - 'mode' (enum, optional): Catalog mode: 'global' (ships to country) or 'local' (domestic only). - 'page' (integer >= 1, default 1): Pagination page number. - 'page_size' (integer 1-100, default 20): Number of candidate items returned per page. - 'sort_by' (enum, default 'relevance'): Ranking attribute ('relevance', 'price', 'title'). - 'sort_order' (enum, default 'desc'): Sort order ('asc' or 'desc'). - 'gender' (string, optional): Target gender filter ('men', 'women', or 'unisex'). - 'size' (array of strings, optional): Filter by available size labels. - 'price_min' (number, optional): Minimum price threshold. - 'price_max' (number, optional): Maximum price threshold. - 'vendor' (array of strings, optional): Brand filter array. - 'personalize' (boolean, default false): Whether to apply personalized ranking weights.products.search.image_uploadUpload a local image file (or base64 string) and search PoloPan catalog products using visual image similarity. Returns matching products with available in-stock sizes, pricing, and verified purchase URLs (https://s.polopan.com/p/{handle}). Automatically localized to active country / 240+ destination regions. PURPOSE & DISAMBIGUATION: - Performs reverse visual search by uploading a local or base64-encoded image to secure temporary storage, then querying visual embeddings. - Distinct from 'products.search.image_url': Use this tool when the image file is local on the user's machine or in base64 format, NOT already on a public URL. - Distinct from 'vision.outfit.detect_pieces': Use this tool to search for products matching a single garment, NOT for decomposing full multi-piece outfits into bounding boxes. WHEN TO USE: - When a user uploads a local photo/screenshot or supplies base64 image data to find matching fashion products in the catalog. WHEN NOT TO USE: - Do NOT use when the image is already accessible via a public web URL (use 'products.search.image_url'). - Do NOT use for text-only searches (use 'products.search.text'). BEHAVIOR & SAFETY: - Read-only catalog query with temporary image upload artifact (automatically expires after 'expiry_hours', default 24h). - Resolves MIME types automatically if not explicitly provided. - Enriches all returned items with verified PoloPan purchase links and stock metadata. PARAMETERS & CONSTRAINTS: - 'image_path' (string, optional): Local file system path to the image file (one of image_path or image_base64 is required). - 'image_base64' (string, optional): Base64-encoded image data string. - 'country' (string, optional): Target country name, city, currency, or ISO-2 code (e.g. 'US', 'United States', 'UK', 'Dubai', 'CA', 'IN'). Defaults to active saved region. - 'mode' (enum, optional): Catalog mode: 'global' (ships to country) or 'local' (domestic only). - 'content_type' (string, default 'image/jpeg'): MIME type of the uploaded image (e.g. 'image/jpeg', 'image/png', 'image/webp'). - 'expiry_hours' (integer 1-168, default 24): Temporary upload lifetime in hours before expiration. - 'page' (integer >= 1, default 1): Pagination page number. - 'page_size' (integer 1-100, default 20): Number of items per page. - 'sort_by' (enum, default 'relevance'): Sorting attribute ('relevance', 'price', 'title'). - 'sort_order' (enum, default 'desc'): Sort direction ('asc' or 'desc'). - 'gender' (string, optional): Target gender filter ('men', 'women', or 'unisex'). - 'size' (array of strings, optional): Size filter array. - 'price_min' (number, optional): Minimum price threshold. - 'price_max' (number, optional): Maximum price threshold. - 'vendor' (array of strings, optional): Brand filter array. - 'personalize' (boolean, default false): Whether to personalize search ranking.vision.outfit.detect_piecesDeconstruct an outfit image or influencer photo into individual fashion pieces (e.g. Upper-body garment, Lower-body garment, Dress, Footwear, Bag, Headwear) with normalized bounding box coordinates and detection confidence scores. PURPOSE & DISAMBIGUATION: - Computer-vision object detection tool designed to analyze multi-item outfit photographs and isolate individual garments with their spatial coordinates. - Distinct from 'products.search.image_url' / 'products.search.image_upload': Use this tool to segment a full outfit into pieces before querying, NOT to directly retrieve catalog search results. - Distinct from 'looks.curation.recommend': Use this tool for image-based piece decomposition, NOT text-based styling suggestions. WHEN TO USE: - When the user provides a full-body model photo, street style snapshot, or celebrity outfit and wants to identify each individual clothing piece (jacket, top, pants, shoes, bag) to find matching products for each piece. WHEN NOT TO USE: - Do NOT use when the image contains only a single standalone garment (use 'products.search.image_url' or 'products.search.image_upload' directly). - Do NOT use for text-only searches (use 'products.search.text'). BEHAVIOR & SAFETY: - Read-only and idempotent with no persistent state modifications. - Supports input via local file path ('image_path'), base64 string ('image_base64'), or public URL ('image_url'). Exactly one source must be provided. - Returns an array of detected piece objects with 'label', 'confidence' (0.0 to 1.0), and normalized 'box' coordinates [ymin, xmin, ymax, xmax]. PARAMETERS & CONSTRAINTS: - 'image_path' (string, optional): Local file system path to the outfit image (e.g. '/tmp/outfit.jpg'). - 'image_base64' (string, optional): Base64-encoded image data string. - 'image_url' (string, optional): Public HTTP(S) URL of the image. - 'threshold' (number 0.05-0.95, default 0.22): Detection confidence threshold for bounding box filtering.- +7 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
DataDive
{
"mcpServers": {
"datadive": {
"command": "npx",
"args": [
"-y",
"@datadive-tools/mcp"
],
"env": {
"DATADIVE_API_KEY": "YOUR_DATADIVE_API_KEY_HERE"
}
}
}
}
PoloPan Fashion MCP Server
{
"mcpServers": {
"polopan-fashion-mcp-server": {
"command": "npx",
"args": [
"-y",
"polopan-products-mcp"
]
}
}
}
Frequently asked questions
DataDive is categorized under E-Commerce and uses a local stdio subprocess. PoloPan Fashion MCP Server belongs to E-Commerce and uses a local stdio subprocess. Pick DataDive for e-commerce work and PoloPan Fashion MCP Server for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
DataDive has no declared pricing — check the project's own site. PoloPan Fashion MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add datadive and polopan-fashion-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, DataDive has a quality signal of 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars. PoloPan Fashion MCP Server has 63/100 (Good) with 1 views, 0 installs and 1 GitHub stars.
