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.

AIDISH — AIエージェントから受取注文できる飲食店

REMOTE · AIDISH-APP.ONRENDER.COM · SCANNED SEP 20

Pickup orders at Japanese restaurants for AI agents: find stores, read menus, place orders. No auth.

+3 this week 68 Trust /100
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
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 503 tokens (~125/item across 4 items; 4 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Install

How do I install the AIDISH — AIエージェントから受取注文できる飲食店 MCP server?

AIDISH — AIエージェントから受取注文できる飲食店 is a hosted endpoint at https://aidish-app.onrender.com/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 · aidish-app.onrender.com

# add to Claude Code
claude mcp add --transport http ai-mentor-bot-aidish 'https://aidish-app.onrender.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-mentor-bot-aidish": {
      "url": "https://aidish-app.onrender.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-mentor-bot-aidish": {
      "type": "http",
      "url": "https://aidish-app.onrender.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-mentor-bot-aidish]
url = "https://aidish-app.onrender.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-mentor-bot-aidish": {
      "type": "remote",
      "url": "https://aidish-app.onrender.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-mentor-bot-aidish --url 'https://aidish-app.onrender.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-mentor-bot-aidish:
    url: "https://aidish-app.onrender.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-mentor-bot-aidish": {
      "Transport": "http",
      "Url": "https://aidish-app.onrender.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-mentor-bot-aidish -t streamable-http -u 'https://aidish-app.onrender.com/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-mentor-bot-aidish": {
      "type": "http",
      "url": "https://aidish-app.onrender.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 18 Sept 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 Sept 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 Sept 26 +1
    • Stability: unverified → 0.03 functional
  • 13 Sept 26 65

    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 20 Sept 2026 · Probed https://aidish-app.onrender.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 24 Jul 2026 22 Oct 2026 ECDSA 256 ECDSA-SHA256 756bcb97dcf1455f0ebf70e5dbe07256
SANs: onrender.com, *.onrender.com
CN=WE1,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 7ff31977972c224a76155d13b6d685e3
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 aidish-app.onrender.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self';base-uri 'self';object-src 'none';frame-ancestors 'none';form-action 'self';script-src 'self' 'unsafe-inline';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;img-src 'self' data: blob: https:;media-src 'self' blob: https: data:;font-src 'self' data: https://fonts.gstatic.com;connect-src 'self' https://*.supabase.co;report-uri /api/csp-report
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aidish-app.onrender.com/mcp Verified 200
http (plaintext) http://aidish-app.onrender.com/mcp HTTPS enforced 301 https://aidish-app.onrender.com/mcp
MCP tools · 4 exposed · ~411 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
check_pickup_availability ~68

今この店が受取注文(テイクアウト)を受け付けているか、最短の受取時刻、店の連絡先を返す。

NameTypeReqDescription
tenant_idstring店舗ID(省略時は既定店)

No output schema declared.

No examples provided.

find_stores ~102

AIから受取注文できる店を探す(店名・料理の種類・エリアで絞る)。tenant_id が分からない時は最初にこれを呼び、利用者に店を選んでもらう。

NameTypeReqDescription
areastringエリア(例: 世田谷)
qstring店名や料理の種類の一部(例: ピザ・ナポリ)

No output schema declared.

No examples provided.

list_menu ~71

店のお品書き(公開中の商品・税込価格・説明・オプション)を返す。注文の前に必ずこれで menu_id を確かめる。

NameTypeReqDescription
tenant_idstring店舗ID(省略時はこのサーバーの既定店)

No output schema declared.

No examples provided.

place_pickup_order ~170

受取注文(テイクアウト)を入れる。支払いは受取時に店頭(現金・カード・QR)。氏名と電話番号は必須で、店が受取時の本人確認と連絡に使う。注文前に必ず利用者に内容と受取時刻を確認すること。

NameTypeReqDescription
customer_namestringyes
customer_telstringyes利用者の電話番号(数字・ハイフン)
itemsarrayyes
notestring
pickup_atstring受取希望時刻 ISO8601(省略時は最短)
tenant_idstring店舗ID(省略時は既定店)

No output schema declared.

No examples provided.

Common questions

What is the AIDISH — AIエージェントから受取注文できる飲食店 MCP server?

AIDISH — AIエージェントから受取注文できる飲食店 is an MCP server listed in the public MCP registry as io.github.ai-mentor-bot/aidish. Pickup orders at Japanese restaurants for AI agents: find stores, read menus, place orders. No auth. This page covers its hosted endpoint (https://aidish-app.onrender.com/mcp).

Is the AIDISH — AIエージェントから受取注文できる飲食店 MCP server safe to use?

AIDISH — AIエージェントから受取注文できる飲食店 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 AIDISH — AIエージェントから受取注文できる飲食店 MCP server expose?

AIDISH — AIエージェントから受取注文できる飲食店 exposes 4 tools: find_stores, list_menu, check_pickup_availability, place_pickup_order. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.

Does the AIDISH — AIエージェントから受取注文できる飲食店 MCP server require authentication?

No. We connected to AIDISH — AIエージェントから受取注文できる飲食店 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AIDISH — AIエージェントから受取注文できる飲食店 MCP server still maintained?

AIDISH — AIエージェントから受取注文できる飲食店 is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.