ヨミタス
REMOTE · MCP.YOMITASU.JP
サイトのページを読み込んで、AI アプリがつなげる形(MCP サーバー)にして配信する無料のサービスです。(yomitasu.jp の内容を検索して答える。ヨミタス経由)
Available components
Last scanned (16 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Search and Retrieval
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. 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
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 819 tokens (~136/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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 →
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 0
- The server rewrote its instructions, which are the text every model session reads security
- 16 Nov 26 0
- Stability: 0.97 → pass security
- 15 Nov 26 0
- Stability: pass → 0.97 functional
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://mcp.yomitasu.jp/s/yomitasu-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. | DS published | 6961 | 8 | Verified |
| yomitasu.jp. | 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://mcp.yomitasu.jp/s/yomitasu-jp/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.yomitasu.jp/s/yomitasu-jp/mcp | HTTPS enforced | 301 | https://mcp.yomitasu.jp/s/yomitasu-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 ページの中身を読む ~104
「ヨミタス」のページの本文を、最初から最後まで返します。利用規約やプライバシーポリシーの条文、使い方の手順を、言い換えずに正確に確かめるときに使います。
| 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 ページの中身を読む(以前の名前) ~98
「ヨミタス」(yomitasu.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。fetch と同じようにページの本文を返しますが、返す形が違います。新しく使うときは fetch を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | ページの URL かパス(日本語のままでも可) |
No output schema declared.
No examples provided.
list_pages どんなページがあるか見る ~103
「ヨミタス」に読み込まれているページの一覧(タイトルと URL)を返します。/guide/ は使い方、/faq/ はよくある質問、/pricing/ は料金、/terms/・/privacy/・/policy/ は規約と方針、/sites/ の下は登録されているサイトの紹介ページです。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
No output schema declared.
No examples provided.
search サイトの中を探す ~164
「ヨミタス」のページから、言葉に当てはまる箇所を抜粋つきで探します。ヨミタスの仕組み、AI アプリへのつなぎ方、料金(すべて無料)、よくある質問、運営方針、利用規約、プライバシーポリシー、運営会社を探せます。ヨミタスについて質問されたら、まずこれを使ってください。登録されているサイトの紹介ページも探せますが、そのサイトの中身は、そのサイト用の MCP サーバーで調べてください。
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 探したい言葉(例: 料金 支払い方法) |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| results | array | yes | – |
No examples provided.
search_pages サイトの中を探す(以前の名前) ~103
「ヨミタス」(yomitasu.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。search と同じようにサイトの中を探しますが、返す形が違います。新しく使うときは search を使ってください。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | 探したい言葉(例: 料金 支払い方法) |
No output schema declared.
No examples provided.
site_overview サイトの概要を知る ~90
「ヨミタス」の概要を返します。サイトのページを読み込んで、AI アプリがつなげる形(MCP サーバー)にして配信する無料のサービスです。サイトの持ち主がタグを 1 行置くだけで登録できます。どんなサービスかを最初に知りたいときに使います。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the ヨミタス MCP server?
ヨミタス is a hosted endpoint at https://mcp.yomitasu.jp/s/yomitasu-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-yomitasu-jp 'https://mcp.yomitasu.jp/s/yomitasu-jp/mcp'
What is the ヨミタス MCP server?
ヨミタス is an MCP server listed in the public MCP registry as jp.yomitasu/yomitasu-jp. サイトのページを読み込んで、AI アプリがつなげる形(MCP サーバー)にして配信する無料のサービスです。(yomitasu.jp の内容を検索して答える。ヨミタス経由). This page covers its hosted endpoint (https://mcp.yomitasu.jp/s/yomitasu-jp/mcp).
Is the ヨミタス MCP server safe to use?
ヨミタス scores 84 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 server expose?
ヨミタス exposes 6 tools: search, fetch, list_pages, site_overview, search_pages, get_page. Their descriptions and schemas cost roughly 662 tokens of context every time the server is loaded.
Does the ヨミタス MCP server require authentication?
No. We connected to ヨミタス without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ヨミタス MCP server still maintained?
ヨミタス 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 ヨミタス MCP server?
VerifyMCP ran 13 checks on ヨミタス, 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.