Zippa（ジッパ）
REMOTE · MCP.YOMITASU.JP · SCANNED SEP 28
サイトの表示速度を、JavaScript のタグを 1 本貼るだけで改善するサービスです。（zippa.jp の内容を検索して答える。ヨミタス経由）
Available components
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 898 tokens (~149/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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% 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 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
How do I install the Zippa（ジッパ） MCP server?
Zippa（ジッパ） is a hosted endpoint at https://mcp.yomitasu.jp/s/zippa-jp/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.yomitasu.jp
claude mcp add --transport http jp-yomitasu-zippa-jp 'https://mcp.yomitasu.jp/s/zippa-jp/mcp'
{
"mcpServers": {
"jp-yomitasu-zippa-jp": {
"url": "https://mcp.yomitasu.jp/s/zippa-jp/mcp"
}
}
} {
"servers": {
"jp-yomitasu-zippa-jp": {
"type": "http",
"url": "https://mcp.yomitasu.jp/s/zippa-jp/mcp"
}
}
} [mcp_servers.jp-yomitasu-zippa-jp] url = "https://mcp.yomitasu.jp/s/zippa-jp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-yomitasu-zippa-jp": {
"type": "remote",
"url": "https://mcp.yomitasu.jp/s/zippa-jp/mcp",
"enabled": true
}
}
} openclaw mcp add jp-yomitasu-zippa-jp --url 'https://mcp.yomitasu.jp/s/zippa-jp/mcp' --transport streamable-http
mcp_servers:
jp-yomitasu-zippa-jp:
url: "https://mcp.yomitasu.jp/s/zippa-jp/mcp" {
"McpServers": {
"jp-yomitasu-zippa-jp": {
"Transport": "http",
"Url": "https://mcp.yomitasu.jp/s/zippa-jp/mcp"
}
}
} assistant mcp add jp-yomitasu-zippa-jp -t streamable-http -u 'https://mcp.yomitasu.jp/s/zippa-jp/mcp'
{
"mcpServers": {
"jp-yomitasu-zippa-jp": {
"type": "http",
"url": "https://mcp.yomitasu.jp/s/zippa-jp/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_page” rewrote its description, which is the text the model reads security
- Tool “search_pages” rewrote its description, which is the text the model reads security
- Schema quality: 591 → 898 ▼ functional
- Tool coverage: 40% → 57% ▲ functional
- First check of Tool coverage: 33 functional
- New tool “fetch” functional
- New tool “search” functional
- Tool “get_page” changed its title: ページの中身を読む → ページの中身を読む（以前の名前） cosmetic
- Tool “search_pages” changed its title: サイトの中を探す → サイトの中を探す（以前の名前） cosmetic
- 26 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 62
First indexed and scored.
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 28 Sept 2026 · Probed https://mcp.yomitasu.jp/s/zippa-jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yomitasu.jp | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 4a1447d8f9e4e0b10e3615b5ae9f0732 |
| SANs: yomitasu.jp, *.yomitasu.jp | ||||||
| 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 mcp.yomitasu.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| yomitasu.jp. | 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.yomitasu.jp/s/zippa-jp/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.yomitasu.jp/s/zippa-jp/mcp | HTTPS enforced | 301 | https://mcp.yomitasu.jp/s/zippa-jp/mcp |
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 →
fetch ページの中身を読む ~116
「Zippa（ジッパ）」のページの本文を、最初から最後まで返します。高速化の機能の一覧、操作マニュアルの手順、利用規約やプライバシーポリシーの条文を、言い換えずに正確に確かめるときに使います。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 探した結果の id（ページの URL）。ページの URL かパスでも可（日本語のままでも可） |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_page ページの中身を読む（以前の名前） ~99
「Zippa（ジッパ）」（zippa.jp）の以前の名前の機能です（すでにつないでいる人のために残しています）。fetch と同じようにページの本文を返しますが、返す形が違います。新しく使うときは fetch を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | ページの URL かパス（日本語のままでも可） |
No output schema declared.
No examples provided.
list_pages どんなページがあるか見る ~134
「Zippa（ジッパ）」に読み込まれているページの一覧（タイトルと URL）を返します。トップ（/）は高速化の機能の紹介、/speed-check/ は無料スピード計測、/manual/ は操作マニュアル、/mission/ は Zippa への思い、/news/ の下はお知らせ、/terms/・/privacy/ は規約と方針、/company/・/operator/ は運営会社と運営者です。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
search サイトの中を探す ~182
「Zippa（ジッパ）」のページから、言葉に当てはまる箇所を抜粋つきで探します。Zippa は、計測タグを 1 本貼るだけでサイトの表示速度を改善する無料のサービスです。高速化の機能、無料スピード計測、管理画面の使い方と数字の読み方（操作マニュアル）、お知らせ、利用規約、プライバシーポリシー、運営会社を探せます。Zippa やサイトの表示速度の改善について質問されたら、まずこれを使ってください。言い換え（値段→価格・料金など）にも対応します。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 探したい言葉（例: 料金 支払い方法） |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_pages サイトの中を探す（以前の名前） ~104
「Zippa（ジッパ）」（zippa.jp）の以前の名前の機能です（すでにつないでいる人のために残しています）。search と同じようにサイトの中を探しますが、返す形が違います。新しく使うときは search を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | 探したい言葉（例: 料金 支払い方法） |
No output schema declared.
No examples provided.
site_overview サイトの概要を知る ~106
「Zippa（ジッパ）」の概要を返します。計測タグを 1 行貼るだけで、次のページの先読みや画像の遅延読み込みなど 14 種類の高速化が自動で効き、その効果を「あり・なし」を比べる実測で確かめられる無料のサービスです。どんなサービスかを最初に知りたいときに使います。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Zippa（ジッパ） MCP server?
Zippa（ジッパ） is an MCP server listed in the public MCP registry as jp.yomitasu/zippa-jp. サイトの表示速度を、JavaScript のタグを 1 本貼るだけで改善するサービスです。（zippa.jp の内容を検索して答える。ヨミタス経由）. This page covers its hosted endpoint (https://mcp.yomitasu.jp/s/zippa-jp/mcp).
Is the Zippa（ジッパ） MCP server safe to use?
Zippa（ジッパ） scores 71 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 Zippa（ジッパ） MCP server expose?
Zippa（ジッパ） exposes 6 tools: search, fetch, list_pages, site_overview, search_pages, get_page. Their descriptions and schemas cost roughly 741 tokens of context every time the server is loaded.
Does the Zippa（ジッパ） MCP server require authentication?
No. We connected to Zippa（ジッパ） without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Zippa（ジッパ） MCP server still maintained?
Zippa（ジッパ） is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.