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.

mcp-dir — MCP directory for retail & e-commerce (Japanese)

REMOTE · MCP-DIR-SEARCH-BQAJ3TFEJQ-AN.A.RUN.APP

Search a Japanese directory of MCP servers for retail/e-commerce by task, with recipes. Read-only.

+3 this week 74 Trust /100

Last scanned (7 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 23 Oct 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 Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 613 tokens (~122/item across 5 items; 5 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 Management73
  • Stability observed for 22 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 10 Oct 26 +1

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

  • 9 Oct 26 +2

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

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 23 Oct 2026 · Probed https://mcp-dir-search-bqaj3tfejq-an.a.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WE2,O=Google Trust Services,C=US 28 Sept 2026 21 Dec 2026 ECDSA 256 ECDSA-SHA256 f744cc9b919363521044a86106657ba7
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WE2,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff32d6b409d15d5965b05873a7c72e0
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp-dir-search-bqaj3tfejq-an.a.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
run.app. absent 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://mcp-dir-search-bqaj3tfejq-an.a.run.app/mcp Verified 200
http (plaintext) http://mcp-dir-search-bqaj3tfejq-an.a.run.app/mcp HTTPS enforced 302 https://mcp-dir-search-bqaj3tfejq-an.a.run.app/mcp
MCP tools · 5 exposed · ~427 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
get_mcp ~67

掲載欄1件の詳細(提供元・認証・権限・接続の難しさ・料金・注意点・安全面・リンク)を slug で取る。

NameTypeReqDescription
slugstringyessearch_mcp の結果の slug

No output schema declared.

No examples provided.

get_recipe ~53

レシピ1件の詳細(手順・そのまま使えるプロンプト・出力例)を slug で取る。

NameTypeReqDescription
slugstringyessearch_recipes の結果の slug

No output schema declared.

No examples provided.

list_categories ~38

mcp-dir のカテゴリ一覧(key・名前・範囲・掲載数)と「目的から探す」タイルの一覧。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_mcp ~154

mcp-dir に掲載されているMCPサーバーを、やりたいこと・ツール名・用途から探す(日本語)。例:「在庫を見たい」「GA4」「レビューを分析したい」。query を空にして category だけ指定すると、そのカテゴリの一覧を検索需要順に返す。

NameTypeReqDescription
categorystring–カテゴリの key で絞る(list_categories で取れる。例: web, ec, voc)
limitinteger–件数(1〜10、既定5)
querystring–やりたいこと・ツール名・用途(自然文でよい)

No output schema declared.

No examples provided.

search_recipes ~115

複数のMCPを組み合わせて業務を1つ終わらせる手順(レシピ)を探す。例:「離脱の多い商品ページを直したい」「週次レポートを自動化」。query を空にすると全件を返す。

NameTypeReqDescription
limitinteger–件数(1〜20、既定5)
querystring–やりたいこと(自然文)。空なら全件

No output schema declared.

No examples provided.

Install

How do I install the mcp-dir — MCP directory for retail & e-commerce (Japanese) server?

mcp-dir — MCP directory for retail & e-commerce (Japanese) is a hosted endpoint at https://mcp-dir-search-bqaj3tfejq-an.a.run.app/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 · mcp-dir-search-bqaj3tfejq-an.a.run.app

# add to Claude Code
claude mcp add --transport http net-haldata-mcp-dir 'https://mcp-dir-search-bqaj3tfejq-an.a.run.app/mcp'
Common questions

What is the mcp-dir — MCP directory for retail & e-commerce (Japanese) server?

mcp-dir — MCP directory for retail & e-commerce (Japanese) is listed in the public MCP registry as net.haldata/mcp-dir. Search a Japanese directory of MCP servers for retail/e-commerce by task, with recipes. Read-only. This page covers its hosted endpoint (https://mcp-dir-search-bqaj3tfejq-an.a.run.app/mcp).

Is the mcp-dir — MCP directory for retail & e-commerce (Japanese) server safe to use?

mcp-dir — MCP directory for retail & e-commerce (Japanese) scores 74 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 mcp-dir — MCP directory for retail & e-commerce (Japanese) server expose?

mcp-dir — MCP directory for retail & e-commerce (Japanese) exposes 5 tools: search_mcp, get_mcp, list_categories, search_recipes, get_recipe. Their descriptions and schemas cost roughly 427 tokens of context every time the server is loaded.

Does the mcp-dir — MCP directory for retail & e-commerce (Japanese) server require authentication?

No. We connected to mcp-dir — MCP directory for retail & e-commerce (Japanese) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the mcp-dir — MCP directory for retail & e-commerce (Japanese) server still maintained?

mcp-dir — MCP directory for retail & e-commerce (Japanese) is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.