PayPay Flea Market Japan Price Checker — Market Stats
One-call price and demand statistics from PayPay Flea Market Japan listings.
What it can do
- Jpmarketdata Paypay Flea Price Checker: This tool calls the Actor "jpmarketdata/paypay-flea-price-checker" and retrieves its output results. Use this tool instead of the "call-actor" if user requests
- Get Actor Run: Get detailed information about a specific Actor run. Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep. - summary describes the past (e.
- Get Dataset Items: Get items (rows) from a dataset — the output/results produced by an Actor run. Not metadata or schema — use get-dataset for counts and the field list, get-dataset-schema for a JSON
What data it sees
Do you need an account
No: the server works without sign-in
One-call price and demand statistics from PayPay Flea Market Japan listings. Runs on Apify, pay-per-event from $0.02/call — connect with your own Apify API token.
How to connect
How to connect PayPay Flea Market Japan Price Checker — Market Stats to Claude
The server address to paste into Claude settings:
https://paypay-flea-price-checker--jpmarketdata.run.tools
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect PayPay Flea Market Japan Price Checker — Market Stats to ChatGPT
The server address to paste into ChatGPT settings:
https://paypay-flea-price-checker--jpmarketdata.run.tools
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect PayPay Flea Market Japan Price Checker — Market Stats to Cursor
The server address to paste into Cursor settings:
https://paypay-flea-price-checker--jpmarketdata.run.tools
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (5)
Raw names from tools/list. Only developers need these.
| jpmarketdata--paypay-flea-price-checker | This tool calls the Actor "jpmarketdata/paypay-flea-price-checker" and retrieves its output results. Use this tool instead of the "call-actor" if user requests this specific Actor. Actor description: Get instant price statistics (median, average, range) plus like-count demand signals from PayPay Flea Market, Japan's #2 flea market app. One call answers: what is this item going for? |
| get-actor-run | Get detailed information about a specific Actor run. Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep. - summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available."). - nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=..."). - waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning. USAGE: - Use to check the status of a run started with call-actor. - Pass waitSecs > 0 to block until terminal (or until the cap elapses). - If `call-actor-widget` or `get-actor-run-widget` rendered a widget for this run, do NOT poll here — the widget self-polls. USAGE EXAMPLES: - user_input: Show details of run y2h7sK3Wc - user_input: Wait for run y2h7sK3Wc to finish |
| get-dataset-items | Get items (rows) from a dataset — the output/results produced by an Actor run. Not metadata or schema — use get-dataset for counts and the field list, get-dataset-schema for a JSON schema from a sample. When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly — do not call get-dataset first. Default limit is 20. Use clean=true to skip empty items and hidden fields. USAGE: - Use when you need to read data from a dataset (all items or only selected fields). USAGE EXAMPLES: - user_input: Retrieve results from dataset abc123 - user_input: Get only metadata.url and title from dataset username~my-dataset |
| get-key-value-store-record | Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys. Use get-key-value-store-keys first if you don't know the key name. The response preserves the original Content-Encoding; most clients handle decompression automatically. USAGE: - Use when you need to retrieve a specific record (JSON, text, or binary) from a store. USAGE EXAMPLES: - user_input: Get record INPUT from store abc123 - user_input: Get record data.json from store username~my-store |
| abort-actor-run | Abort an Actor run that is currently starting or running. For runs with status FINISHED, FAILED, ABORTING, or TIMED-OUT, this call has no effect. The results will include the updated run details after the abort request. USAGE: - Use when you need to stop a run that is taking too long or misconfigured. USAGE EXAMPLES: - user_input: Abort run y2h7sK3Wc - user_input: Gracefully abort run y2h7sK3Wc |