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.

dev.plugrail/expo2027-mcp

REMOTE · EXPO2027.PLUGRAIL.DEV

Unofficial read-only MCP server for GREEN×EXPO 2027, the 2027 Yokohama horticultural expo.

60 Trust /100

Last scanned (21 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

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 Security46
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 652 tokens (~108/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 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 (11)

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

Checks we could not complete (2)

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.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • 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
    • Stability: unverified → 0.03 ▲ functional
  • 19 Nov 26 59

    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://expo2027.plugrail.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=plugrail.dev CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 e5be922a259fc2091384e44d2a9f7797
SANs: plugrail.dev, expo2027.plugrail.dev, *.expo2027.plugrail.dev
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 expo2027.plugrail.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
plugrail.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://expo2027.plugrail.dev/mcp Verified 200
http (plaintext) http://expo2027.plugrail.dev/mcp Inconclusive 406
MCP tools · 6 exposed · ~603 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_access_options ~154

Unofficial. How to get to the venue: 4-station shuttle bus (Sotetsu Seya / Mitsukyo, Tokyu Minami-Machida, JR Yokohama Line Tokaichiba), direct buses, parking (car/motorcycle), park & ride, bicycle, walking. Optional filter, e.g. "瀬谷", "shuttle", "parking", "bicycle".

NameTypeReqDescription
fromstring–Optional filter for the access mode or station name.
langstring–Output language for labels. Supported: ja, en, fr, es, zh-Hant, zh-Hans, ko. Content facts stay in their source language. Default: en.

No output schema declared.

No examples provided.

get_event_info ~92

Unofficial. Basic facts of International Horticultural Expo 2027, Yokohama (GREEN×EXPO 2027): dates, venue, hours, theme, class, expected attendance.

NameTypeReqDescription
langstring–Output language for labels. Supported: ja, en, fr, es, zh-Hant, zh-Hans, ko. Content facts stay in their source language. Default: en.

No output schema declared.

No examples provided.

get_news ~89

Unofficial. Latest news items from the official site (Japanese titles, up to 20). News titles are NOT translated.

NameTypeReqDescription
langstring–Output language for labels. Supported: ja, en, fr, es, zh-Hant, zh-Hans, ko. Content facts stay in their source language. Default: en.
limitinteger–Max items (default 10).

No output schema declared.

No examples provided.

list_ticket_types ~83

Unofficial. Admission ticket types and JPY prices (early/regular/night/passes/group discounts). Verify on the official ticket site; prices may change.

NameTypeReqDescription
langstring–Output language for labels. Supported: ja, en, fr, es, zh-Hant, zh-Hans, ko. Content facts stay in their source language. Default: en.

No output schema declared.

No examples provided.

list_villages ~89

Unofficial. Lists the 12 Village exhibitors and 4 theme commercial venues with organizer, theme and official URL, plus key exhibits (テーマ館「ねっこ」 etc.).

NameTypeReqDescription
langstring–Output language for labels. Supported: ja, en, fr, es, zh-Hant, zh-Hans, ko. Content facts stay in their source language. Default: en.

No output schema declared.

No examples provided.

search_event_topics ~96

Unofficial. Keyword search over curated official-site topics (dates, tickets, access, pavilions, FAQ, mascot, etc.). Returns official URLs.

NameTypeReqDescription
langstring–Output language for labels. Supported: ja, en, fr, es, zh-Hant, zh-Hans, ko. Content facts stay in their source language. Default: en.
querystringyesSearch query (Japanese or English).

No output schema declared.

No examples provided.

Install

How do I install the dev.plugrail/expo2027-mcp server?

dev.plugrail/expo2027-mcp is a hosted endpoint at https://expo2027.plugrail.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 · expo2027.plugrail.dev

# add to Claude Code
claude mcp add --transport http dev-plugrail-expo2027-mcp 'https://expo2027.plugrail.dev/mcp'
Common questions

What is the dev.plugrail/expo2027-mcp server?

dev.plugrail/expo2027-mcp is listed in the public MCP registry as dev.plugrail/expo2027-mcp. Unofficial read-only MCP server for GREEN×EXPO 2027, the 2027 Yokohama horticultural expo. This page covers its hosted endpoint (https://expo2027.plugrail.dev/mcp).

Is the dev.plugrail/expo2027-mcp server safe to use?

dev.plugrail/expo2027-mcp scores 60 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 dev.plugrail/expo2027-mcp server expose?

dev.plugrail/expo2027-mcp exposes 6 tools: get_event_info, list_ticket_types, get_access_options, list_villages, get_news, search_event_topics. Their descriptions and schemas cost roughly 603 tokens of context every time the server is loaded.

Does the dev.plugrail/expo2027-mcp server require authentication?

No. We connected to dev.plugrail/expo2027-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dev.plugrail/expo2027-mcp server still maintained?

dev.plugrail/expo2027-mcp 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 dev.plugrail/expo2027-mcp server?

VerifyMCP ran 11 checks on dev.plugrail/expo2027-mcp, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about dev.plugrail/expo2027-mcp: Authorization and 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.