furima-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FURIMA_CACHE_TTL | No | Seconds a site's search result is reused for an identical query. 0 disables the cache. | 300 |
| FURIMA_MIN_INTERVAL | No | Minimum seconds between two requests to the same site. Raising it is fine; lowering it is not recommended. | 1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Search Japanese second-hand marketplaces: Mercari (mercari), Yahoo! Auctions (yahoo), Yahoo! Flea Market / PayPay Flea Market (paypay) and Rakuma (rakuma). Prices are in JPY.
Tips:
Search in Japanese. Product names, series names and model numbers work best (e.g. "ポケモンカード ピカチュウ 25th", "PS5 CFI-2000", "ドラクエ3 SFC 箱説").
Results are keyword matches and include accessories, bundles and junk. Use
exclude(e.g. ["ジャンク", "空箱", "ケースのみ"]) and price bounds to keep the comparison fair.Yahoo auction prices with is_auction=true are current bids and may still rise.
Use sold_price_stats or check_price before calling something a good deal.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_listingsA | Search listings that are for sale now on Japanese marketplaces. Returns the merged listings (site, title, price in JPY, url, image, and for auctions the current bid count and end time), the total matches each site reports, and any site that failed. |
| sold_price_statsA | What an item actually sells for: statistics over recently sold listings. Reads the most recent sold listings from Mercari, Yahoo! Auctions (final prices) and Rakuma, and returns count, min, p25, median, p75, max and mean overall and per site, plus a few recent sales as examples. |
| check_priceA | Judge whether a price is cheap or expensive against recent sold prices. Returns the price's percentile among recent sales (0 = cheaper than every sale, 100 = dearer than every sale), a one-line verdict, and the sold-price statistics. |
| get_listingB | Full details of one listing: price, status, condition, description, images and seller. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
The tools are mostly distinct: search_listings finds items, get_listing retrieves details, sold_price_stats provides historical statistics, and check_price evaluates a specific price. The main potential overlap is between sold_price_stats and check_price, since check_price also returns the sold-price statistics, but the descriptions make the intended use cases clear.
All names use consistent snake_case, and three follow a clear verb_noun pattern (search_listings, get_listing, check_price). The exception is sold_price_stats, which is noun-based, but it remains readable and predictable in context.
Four tools is well-scoped for a niche Japanese marketplace price-research server. Each tool maps to a distinct step in the workflow: search, inspect a listing, get sold-price statistics, and judge a price.
The core research workflow is covered: find current listings, retrieve details, analyze recent sold prices, and evaluate a price. Minor gaps exist, such as no seller-focused lookup or category browsing, but agents can reasonably work around these limitations.