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.

joino Japan Events

REMOTE · JOINO.ME

Search 70,000+ local events, festivals and experiences across Japan. Daily updates, en/zh/ko.

Available components

74 Trust /100

Last scanned (21 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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 Security80
  • 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 is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • 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 (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1804 tokens (~200/item across 9 items; 9 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 Management17
  • Stability observed for 5 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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 (13)

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

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.

  • 21 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.

  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 19 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.

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 71

    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://joino.me/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=links.popegg.com CN=WR3,O=Google Trust Services,C=US 20 Oct 2026 18 Jan 2027 RSA 2048 SHA256-RSA 5fd6400e23a01e3112ce70161bbd0676
SANs: links.popegg.com, www.less-bound.com, intranet.k-9apps.com, letsbegin.inspirepositivechanges.com, yujoonlee.com, birdrides-opt-out.ilymgroup.com, m4ttbit.dev, www.df3d.com, kol.matrixengagementgroup.com, dashboard.loadmax.com, app.monnos.com, tmdigital.terramagna.com.br and 88 more
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of joino.me. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
me. DS published 45352 8 Verified
joino.me. 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
Header Value
strict-transport-security max-age=31556926

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://joino.me/mcp Verified 200
http (plaintext) http://joino.me/mcp HTTPS enforced 301 https://joino.me/mcp
MCP tools · 9 exposed · ~1,491 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
build_navigation_url ~227

Build car navigation URLs (Google Maps, Apple Maps, Waze, etc.) via chosen event venues. 選んだイベント会場を経由地に含むカーナビURLを生成する(6サービス対応)。 Google Maps、Apple Maps、Yahoo!カーナビ、Waze、HERE WeGo、MapFanの URLを一括生成して返す。

NameTypeReqDescription
destinationstringyesDestination place name or address (e.g. "Hakone", "箱根"). 目的地(地名・住所)
event_ids––Optional event ids (from search results) to show as waypoints on the joino.me route page
originstringyesStart place name or address (e.g. "Tokyo Station", "東京駅"). 出発地(地名・住所)
waypoint_addressesarrayyesWaypoint addresses in visiting order, e.g. venues of events chosen from search results (up to 10; extra ones are ignored). 経由地の住所リスト(最大10箇所)

Structured output declared, but exposes no named fields.

No examples provided.

get_event_detail ~80

Get full details of an event by its id. イベントIDから詳細情報を取得する。

NameTypeReqDescription
event_idstringyesEvent id (UUID) returned by the search tools
langstring–Language of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that language

Structured output declared, but exposes no named fields.

No examples provided.

list_categories ~31

List event category keys with labels and counts. 登録されているカテゴリの一覧と件数を返す。

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_spot_categories ~36

List tourist spot category keys with labels and counts. 登録されているスポットカテゴリの一覧と件数を返す。

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

search_events ~261

Search events in Japan by keyword, prefecture, category and date range. イベントを検索する。キーワード、都道府県、カテゴリ、日付範囲で絞り込み可能。

NameTypeReqDescription
categorystring–Event category key(s), comma separated. See list_categories (e.g. festival, culture, sports)
date_fromstring–Events held on or after this date (YYYY-MM-DD). Default: today (ended events are excluded)
date_tostring–Events starting on or before this date (YYYY-MM-DD)
include_experiencesboolean–Also include year-round bookable experiences/activities (tours, workshops), listed after dated events
keywordstring–Keyword matched against title/description/translations (Japanese or English, e.g. "花火", "fireworks")
langstring–Language of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that language
limitinteger–Max results (1-100, default 20)
prefecturestring–Prefecture in English or Japanese (e.g. "Tokyo", "Kyoto", "東京都")

Structured output declared, but exposes no named fields.

No examples provided.

search_nearby_events ~218

Search events near a coordinate in Japan. 指定座標の周辺イベントを検索する(PostGIS使用)。

NameTypeReqDescription
date_fromstring–Events held on or after this date (YYYY-MM-DD). Default: today (ended events are excluded)
date_tostring–Events starting on or before this date (YYYY-MM-DD)
include_experiencesboolean–Also include year-round bookable experiences/activities (tours, workshops), listed after dated events
langstring–Language of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that language
latitudenumberyesLatitude in decimal degrees (e.g. 35.6812)
limitinteger–Max results (1-100, default 20)
longitudenumberyesLongitude in decimal degrees (e.g. 139.7671)
radius_kmnumber–Search radius in km (default 10)

Structured output declared, but exposes no named fields.

No examples provided.

search_nearby_spots ~139

Search tourist spots near a coordinate in Japan. 指定座標の周辺スポットを検索する(PostGIS使用)。

NameTypeReqDescription
categorystring–Spot category key(s), comma separated. See list_spot_categories (e.g. culture_onsen)
latitudenumberyesLatitude in decimal degrees (e.g. 35.6812)
limitinteger–Max results (1-100, default 20)
longitudenumberyesLongitude in decimal degrees (e.g. 139.7671)
radius_kmnumber–Search radius in km (default 10)

Structured output declared, but exposes no named fields.

No examples provided.

search_route_events ~351

Find events along a driving route in Japan, with car navigation URLs. ドライブルート沿いのイベントを検索し、Google Mapsカーナビ付きで返す。 出発地→目的地のルート沿いを等間隔でスキャンし、周辺イベントを収集する。 結果にはイベント一覧と、選んだイベントを経由地に含むカーナビURLが含まれる。

NameTypeReqDescription
categorystring–Event category key(s), comma separated. See list_categories (e.g. festival, culture, sports)
date_fromstring–Events held on or after this date (YYYY-MM-DD). Default: today (ended events are excluded)
date_tostring–Events starting on or before this date (YYYY-MM-DD)
destinationstringyesDestination place name/address/station (e.g. "Hakone", "箱根")
include_experiencesboolean–Also include year-round bookable experiences/activities (tours, workshops), listed after dated events
keywordstring–Keyword matched against title/description/translations (Japanese or English, e.g. "花火", "fireworks")
langstring–Language of the user's conversation: ja, en, zh or ko (default ja). Sets joino_url to the page in that language
limitinteger–Max results (1-50, default 30)
originstringyesStart place name/address/station (e.g. "Tokyo Station", "東京駅")
radius_kmnumber–Search radius from the route in km (default 15)

Structured output declared, but exposes no named fields.

No examples provided.

search_spots ~148

Search tourist spots in Japan by keyword, prefecture and category. 観光スポットを検索する。キーワード、都道府県、カテゴリで絞り込み可能。

NameTypeReqDescription
categorystring–Spot category key(s), comma separated. See list_spot_categories (e.g. nature_mountain, culture_shrine_temple)
keywordstring–Keyword matched against spot name/address (Japanese, e.g. "温泉", "城")
limitinteger–Max results (1-100, default 20)
prefecturestring–Prefecture in English or Japanese (e.g. "Tokyo", "Kyoto", "東京都")

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the joino Japan Events MCP server?

joino Japan Events is a hosted endpoint at https://joino.me/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 · joino.me

# add to Claude Code
claude mcp add --transport http warao-shikyo-joino-japan-events 'https://joino.me/mcp'
Common questions

What is the joino Japan Events MCP server?

joino Japan Events is an MCP server listed in the public MCP registry as io.github.warao-shikyo/joino-japan-events. Search 70,000+ local events, festivals and experiences across Japan. Daily updates, en/zh/ko. This page covers its hosted endpoint (https://joino.me/mcp).

Is the joino Japan Events MCP server safe to use?

joino Japan Events 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 joino Japan Events MCP server expose?

joino Japan Events exposes 9 tools: search_events, search_nearby_events, get_event_detail, list_categories, search_spots, and 4 more. Their descriptions and schemas cost roughly 1,491 tokens of context every time the server is loaded.

Does the joino Japan Events MCP server require authentication?

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

Is the joino Japan Events MCP server still maintained?

joino Japan Events 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 joino Japan Events MCP server?

VerifyMCP ran 13 checks on joino Japan Events, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.