KH Merch Graph (kh-merch-graph.fandex.workers.dev)
MCP server · kh-merch-graph.fandex.workers.dev · found in a public list · checked since 2026-10-24
Live, handshake completed · latest check
https://kh-merch-graph.fandex.workers.dev/mcp MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-10-24 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-10-24 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-10-24 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
discoverestimate_landed_costexplain_productreport_correctionresolve_listingresolve_listings_batch
- Tools
- 6
- This list since
- 2026-10-24
- First listed to us
- 2026-10-24
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- tools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
What it says about itself
- Where it works
- Japanfrom its listing's description, read 2026-10-25
From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/4): its claims, not checked by us. Anything not listed, it does not state. Definitions
Calls it declares
resolve_listing title* description price_jpy platform url srcresolve_listings_batch listings*explain_product sku_id querydiscover ip* character budget_jpy purpose limit termsestimate_landed_cost price_jpy* sku_id weight_g dest_country* proxyreport_correction sku_id field* proposed_value* source_url note
From the tool list it returned to our check (request-shape/1). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Listing
In the capability tree: Other (not placed in a branch yet) (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-25. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/6): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 73 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_56a97215a457d85d