Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Merchgraph

REMOTE · KH-MERCH-GRAPH.FANDEX.WORKERS.DEV · 2 COMPONENTS

Anime & game merch catalog: identify listings, release prices, official status, how to buy.

+3 this week 68 Trust /100

Last scanned (23 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security63
  • 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1959 tokens (~326/item across 6 items; 6 tools + 0 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 Management27
  • Stability observed for 8 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

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 →

Changelog

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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 64

    First indexed and scored.

Diagnostics

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://kh-merch-graph.fandex.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fandex.workers.dev CN=YE2,O=Let's Encrypt,C=US 16 Nov 2026 14 Feb 2027 ECDSA 256 ECDSA-SHA384 6a2a9564341a448c19b757424190538ece6
SANs: *.fandex.workers.dev, fandex.workers.dev
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 kh-merch-graph.fandex.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kh-merch-graph.fandex.workers.dev/mcp Verified 200
http (plaintext) http://kh-merch-graph.fandex.workers.dev/mcp Inconclusive 406
MCP tools · 6 exposed · ~1,757 tokens

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 →

Tool Tokens
discover ~462

Browse the merchandise catalog (Kingdom Hearts, Demon Slayer and One Piece) by series, character, budget and purpose. Use it to answer "what merch exists for X?" or "gift ideas under ¥5,000". Example: {ip: "kingdom-hearts", character: "Sora", budget_jpy: 5000, purpose: "display"}. Omit ip to search every series. Returns items[] (sku_id, name_en/name_ja, official, original price msrp_jpy plus price_local/currency, price_basis, price_note_en for per-draw prices, region, availability_hint, typical_channels, source_url, page_url = the item's page on merchgraph.app) and total_matches. For a series that is not covered, items is empty and supported_series lists the covered ones. If a character has no solo merch (e.g. Xigbar), the result also has suggested_character_group and suggested_items for their group (e.g. Organization XIII). Lists catalog entries only; it does not mean anything is for sale right now. Use explain_product with a sku_id for full details.

NameTypeReqDescription
budget_jpynumber–Maximum original price in Japanese yen (overseas items are compared at a fixed rate), e.g. 5000. Optional.
characterstring–Character name in English or Japanese, e.g. "Sora", "ソラ", "Organization XIII". Partial match. Optional.
ipstring–Series ID. Live series: "kingdom-hearts" (Kingdom Hearts), "kimetsu-no-yaiba" (Demon Slayer), "one-piece" (One Piece). Optional: omit to search all of them.
limitnumber–Maximum number of items to return (default 10). total_matches always gives the full count.
purposestring–"display" = figures, plush, prizes, acrylic stands; "wear" = apparel; "read" = books; "play" = games and cards; "any" (default).
termsobject–Filter by series vocabulary (factions, worlds, keyblades, songs…) found in item names, aliases or notes. Optional.

No output schema declared.

No examples provided.

estimate_landed_cost ~252

Estimate the total cost of buying an item in Japan and having it forwarded abroad. Example: {price_jpy: 4500, sku_id: "ichiban-kuji-kh-2018-a", dest_country: "US"}. Returns routes[] (forwarding service × shipping method, with fees and total_jpy, cheapest first) and cheapest. Rough figures only: fee and shipping tables currently cover US, GB, DE and FR (other countries return no routes), come from third-party comparison guides (mid-2026) and exclude duties. Not a quote; we are not affiliated with any forwarding service.

NameTypeReqDescription
dest_countrystringyesDestination country as an ISO 3166-1 alpha-2 code, e.g. "US", "GB", "AU".
price_jpynumberyesItem price in Japanese yen (required).
proxystring–Only show one forwarding service, e.g. "buyee". Optional.
sku_idstring–Catalog sku_id, used to look up the weight. Optional.
weight_gnumber–Package weight in grams, when there is no sku_id or the catalog has no weight.

No output schema declared.

No examples provided.

explain_product ~309

Get the full record for one catalog item (Kingdom Hearts, Demon Slayer and One Piece). Pass a sku_id from discover/resolve_listing (e.g. {sku_id: "ichiban-kuji-kh-2018-a"}), or a free-text query such as {query: "Sora Bring Arts Halloween Town"} to get the best match. Returns names (en/ja), product line (maker, line type, release date), characters, original price (msrp_jpy, price_local, currency, price_basis), acquisition_type (retail, kuji, prize, …), availability (hint + confidence), typical_channels, shipping (whether it is only sold at shops that ship within Japan, so a shipping-forwarding service is needed from abroad; costs are not calculated; for Mercari/Suruga-ya items a note that Mercari's global app may allow direct purchase in some countries), size/weight, re-release dates, official (licensed or fan-made), verified (checked against the source), source_url (primary source) and page_url (the item's page on merchgraph.app; cite both).

NameTypeReqDescription
querystring–Free-text product name in English or Japanese when you have no sku_id, e.g. "一番くじ キングダムハーツ A賞".
sku_idstring–Catalog SKU ID, e.g. "ichiban-kuji-kh-2018-a". Either sku_id or query is required.

No output schema declared.

No examples provided.

report_correction ~210

Report a mistake or missing item in the catalog (reviewed by hand before anything changes). Example: {sku_id: "ichiban-kuji-kh-2018-a", field: "msrp_jpy", proposed_value: "750", source_url: "https://…"}. Please include a primary source (maker, official shop or reliable press) when you can. Returns {accepted, correction_id}.

NameTypeReqDescription
fieldstringyesWhat is wrong, as a catalog field name, e.g. "name_en", "msrp_jpy", "availability_hint", "official", or "new_item".
notestring–Anything else worth knowing. Optional.
proposed_valuestringyesThe correct value (or, for a new item, its name and details).
sku_idstring–The item's sku_id. Leave empty to suggest a new item.
source_urlstring–URL of a primary source that confirms it. Optional but strongly preferred.

No output schema declared.

No examples provided.

resolve_listing ~390

Identify a Kingdom Hearts, Demon Slayer and One Piece item from a marketplace listing (Mercari, Yahoo! Auctions, Suruga-ya, Mandarake, eBay…). Paste the listing title as-is (Japanese or English), e.g. {title: "一番くじ キングダムハーツ A賞 ソラ フィギュア 箱なし", price_jpy: 4500}. Returns candidates[] (sku_id, name_en, confidence 0-1, why, source_url, page_url = the item's page on merchgraph.app; several when the title is ambiguous), weak_matches[] when unsure, conditions[] (Japanese condition words such as 未使用/箱なし explained), flags[] (bootleg caution notes, not a verdict), price (original price and listing-to-original ratio when price_jpy is given), shipping (whether a shipping-forwarding service is needed from abroad; set platform for a precise answer; for Mercari/Suruga-ya a note that Mercari's global app may allow direct purchase in some countries), acquisition notes and next_checks_en (what to ask the seller). Listing text is not stored. For many listings at once use resolve_listings_batch.

NameTypeReqDescription
descriptionstring–Part of the listing description, e.g. condition notes such as 開封済み. Optional; improves condition and bootleg checks.
platformstring–Where it is listed. Optional.
price_jpynumber–Listing price in Japanese yen. Optional; enables the comparison with the original price.
srcstring–Traffic-source tag for usage statistics, used by the website (optional; only the tag and time are logged). Agents can omit it.
titlestringyesThe listing title, copied as-is (required).
urlstring–Listing URL. Optional; not stored and not fetched.

No output schema declared.

No examples provided.

resolve_listings_batch ~134

Run resolve_listing on up to 5 listings in one call, e.g. when comparing search results from a marketplace. Example: {listings: [{title: "…", price_jpy: 3000}, {title: "…"}]}. Returns an array in the same order; each element has the same shape as a resolve_listing result (or {error} for that one listing only). For more than 5, split into several calls. For a single listing use resolve_listing.

NameTypeReqDescription
listingsarrayyesListings to check (1–5); each takes the same arguments as resolve_listing.

No output schema declared.

No examples provided.

Install

How do I install the Merchgraph MCP server?

Merchgraph is a hosted endpoint at https://kh-merch-graph.fandex.workers.dev/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 · kh-merch-graph.fandex.workers.dev

# add to Claude Code
claude mcp add --transport http marleyhereicome-cpu-merchgraph 'https://kh-merch-graph.fandex.workers.dev/mcp'
Common questions

What is the Merchgraph MCP server?

Merchgraph is an MCP server listed in the public MCP registry as io.github.marleyhereicome-cpu/merchgraph. Anime & game merch catalog: identify listings, release prices, official status, how to buy. This page covers its hosted endpoint (https://kh-merch-graph.fandex.workers.dev/mcp).

Is the Merchgraph MCP server safe to use?

Merchgraph scores 68 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 Merchgraph MCP server expose?

Merchgraph exposes 6 tools: resolve_listing, resolve_listings_batch, explain_product, discover, estimate_landed_cost, report_correction. Their descriptions and schemas cost roughly 1,757 tokens of context every time the server is loaded.

Does the Merchgraph MCP server require authentication?

No. We connected to Merchgraph without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Merchgraph MCP server still maintained?

Merchgraph 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 Merchgraph MCP server?

VerifyMCP ran 12 checks on Merchgraph, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Merchgraph: HTTPS. 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.