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.

pare-suitengumae.jp

REMOTE · MCP.YOMITASU.JP

人形町・水天宮前で内科、外科ならメディカルクリニックパレ水天宮前。(pare-suitengumae.jp の内容を検索して答える。ヨミタス経由)

Available components

+4 this week 75 Trust /100

Last scanned (6 minutes ago)

Scores higher than 62% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Health and Science

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 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
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 911 tokens (~151/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 Management40
  • Stability observed for 12 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
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.

  • 22 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 69

    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 22 Nov 2026 · Probed https://mcp.yomitasu.jp/s/pare-suitengumae-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/pare-suitengumae-jp/mcp Verified 200
http (plaintext) http://mcp.yomitasu.jp/s/pare-suitengumae-jp/mcp HTTPS enforced 301 https://mcp.yomitasu.jp/s/pare-suitengumae-jp/mcp
MCP tools · 6 exposed · ~746 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
fetch ~133

「pare-suitengumae.jp」(pare-suitengumae.jp)の、読み込んだページの本文を全文返します。id には、探した結果の id(ページの URL)か、ページの URL・パスを渡します。料金・日付・条件・規約など、正確さが大事なことは、答える前にこれで本文を確かめてください。

NameTypeReqDescription
idstringyes探した結果の id(ページの URL)。ページの URL かパスでも可(日本語のままでも可)
NameTypeReqDescription
idstringyes–
metadataobject––
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_page ~103

「pare-suitengumae.jp」(pare-suitengumae.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。fetch と同じようにページの本文を返しますが、返す形が違います。新しく使うときは fetch を使ってください。

NameTypeReqDescription
urlstringyesページの URL かパス(日本語のままでも可)

No output schema declared.

No examples provided.

list_pages ~111

「pare-suitengumae.jp」(pare-suitengumae.jp)で読み込んだページの一覧を、タイトルと URL で返します。一度に 50 件ずつ(limit で最大 200 件)で、続きは offset で取れます。どんなページがあるか知りたいときや、探しても見つからないときに使います。

NameTypeReqDescription
limitinteger––
offsetinteger––

No output schema declared.

No examples provided.

search ~218

「pare-suitengumae.jp」(pare-suitengumae.jp)から読み込んだページの中を言葉で探し、当てはまる箇所を抜粋と URL つきで返します。pare-suitengumae.jp について質問されたら、まずこれを使ってください。探せるのは読み込んだページだけで、ネット全体や、読み込んだあとの更新は含みません。見つからないときは、略語を正式な名前にする、同じ意味の別の言葉にするなど、言い方を変えて探し直してください。それでも見つからないときに返るページの候補も読み、それでも見つからなければ推測で答えず、このサイトの中では見つけられなかったと伝えてください。

NameTypeReqDescription
querystringyes探したい言葉(例: 料金 支払い方法)
NameTypeReqDescription
candidatesarray––
resultsarrayyes–

No examples provided.

search_pages ~108

「pare-suitengumae.jp」(pare-suitengumae.jp)の以前の名前の機能です(すでにつないでいる人のために残しています)。search と同じようにサイトの中を探しますが、返す形が違います。新しく使うときは search を使ってください。

NameTypeReqDescription
limitinteger––
querystringyes探したい言葉(例: 料金 支払い方法)

No output schema declared.

No examples provided.

site_overview ~73

「pare-suitengumae.jp」(pare-suitengumae.jp)がどんなサイトかを返します。種類・紹介文・読み込んだページ数・主なページが分かります。最初にサイトの全体像をつかみたいときに使います。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the pare-suitengumae.jp MCP server?

pare-suitengumae.jp is a hosted endpoint at https://mcp.yomitasu.jp/s/pare-suitengumae-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

# add to Claude Code
claude mcp add --transport http jp-yomitasu-pare-suitengumae-jp 'https://mcp.yomitasu.jp/s/pare-suitengumae-jp/mcp'
Common questions

What is the pare-suitengumae.jp MCP server?

pare-suitengumae.jp is an MCP server listed in the public MCP registry as jp.yomitasu/pare-suitengumae-jp. 人形町・水天宮前で内科、外科ならメディカルクリニックパレ水天宮前。(pare-suitengumae.jp の内容を検索して答える。ヨミタス経由). This page covers its hosted endpoint (https://mcp.yomitasu.jp/s/pare-suitengumae-jp/mcp).

Is the pare-suitengumae.jp MCP server safe to use?

pare-suitengumae.jp scores 75 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 pare-suitengumae.jp MCP server expose?

pare-suitengumae.jp exposes 6 tools: search, fetch, list_pages, site_overview, search_pages, get_page. Their descriptions and schemas cost roughly 746 tokens of context every time the server is loaded.

Does the pare-suitengumae.jp MCP server require authentication?

No. We connected to pare-suitengumae.jp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the pare-suitengumae.jp MCP server still maintained?

pare-suitengumae.jp is still listed as active in the MCP registry. We last reached this channel on 22 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 pare-suitengumae.jp MCP server?

VerifyMCP ran 13 checks on pare-suitengumae.jp, 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.