Ad Arch Agents
REMOTE · AGENTS.ADARCH.CO.JP · SCANNED SEP 26
Request quotes for video, shooting, social media, ad media, design, web and events in Japan.
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 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. 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
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4252 tokens (~607/item across 7 items; 7 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Ad Arch Agents MCP server?
Ad Arch Agents is a hosted endpoint at https://agents.adarch.co.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 · agents.adarch.co.jp
claude mcp add --transport http jp-co-adarch-agents 'https://agents.adarch.co.jp/mcp'
{
"mcpServers": {
"jp-co-adarch-agents": {
"url": "https://agents.adarch.co.jp/mcp"
}
}
} {
"servers": {
"jp-co-adarch-agents": {
"type": "http",
"url": "https://agents.adarch.co.jp/mcp"
}
}
} [mcp_servers.jp-co-adarch-agents] url = "https://agents.adarch.co.jp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jp-co-adarch-agents": {
"type": "remote",
"url": "https://agents.adarch.co.jp/mcp",
"enabled": true
}
}
} openclaw mcp add jp-co-adarch-agents --url 'https://agents.adarch.co.jp/mcp' --transport streamable-http
mcp_servers:
jp-co-adarch-agents:
url: "https://agents.adarch.co.jp/mcp" {
"McpServers": {
"jp-co-adarch-agents": {
"Transport": "http",
"Url": "https://agents.adarch.co.jp/mcp"
}
}
} assistant mcp add jp-co-adarch-agents -t streamable-http -u 'https://agents.adarch.co.jp/mcp'
{
"mcpServers": {
"jp-co-adarch-agents": {
"type": "http",
"url": "https://agents.adarch.co.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.
- 26 Sept 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.
- 25 Sept 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
- 24 Sept 26 73
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 26 Sept 2026 · Probed https://agents.adarch.co.jp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agents.adarch.co.jp | CN=YR1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | RSA 2048 | SHA256-RSA | 565f02d06f703bec5a334fbfb672393b8da |
| SANs: agents.adarch.co.jp | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agents.adarch.co.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| co.jp. | absent | Delegated | ||
| adarch.co.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https://*.tile.openstreetmap.org https://cyberjapandata.gsi.go.jp https://lh3.googleusercontent.com https://lh4.googleusercontent.com https://images.unsplash.com https://image.mux.com https://*.line-scdn.net; media-src 'self' blob: https://stream.mux.com https://*.mux.com; worker-src 'self' blob:; connect-src 'self' blob: https://*.ingest.sentry.io https://*.mux.com https://*.production.mux.com https://inferred.litix.io https://*.litix.io; font-src 'self' https://fonts.gstatic.com; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com https://player.vimeo.com https://stream.mux.com https://drive.google.com; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agents.adarch.co.jp/mcp | Verified | 200 | |
| http (plaintext) | http://agents.adarch.co.jp/mcp | HTTPS enforced | 301 | https://agents.adarch.co.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 →
creator_register クリエイター・制作会社の登録の案内 ~123
制作者（撮影・編集など）としての登録ページのURLと、登録について決まっている事実（無料・対象・手続き・守秘義務）を返す。仕事の量や収入の見込みは含まない。
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | 相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う |
No output schema declared.
No examples provided.
find_ad_awards 出せる広告賞を探す（全国・地方・国際） ~225
応募できる広告賞と、次の応募期間（受付中／次回の目安）を返す。都道府県を渡すとその地方の賞を先頭に返す。category は TVCM / WEB動画 / ラジオCM / 新聞 / 雑誌 / OOH交通 / デジタルWeb / PR / BtoB / キャンペーン総合 / デザイン / パッケージ / 学生 / その他 のどれか。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| includeInternational | boolean | – | – |
| limit | integer | – | 既定15・最大30 |
| openOnly | boolean | – | 今受付中のものだけ |
| prefecture | string | – | – |
| role | string | – | 相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う |
No output schema declared.
No examples provided.
find_subsidies 広告費・動画制作費に使える補助金を探す ~216
国・自治体の補助金（jGrants）のうち、広告費・動画制作費が対象になる、またはなる可能性がある制度を、締切の近い順に返す。都道府県と業種（例: 製造業、宿泊業、飲食サービス業）で絞れる。採択を保証するものではない。
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | 業種の言葉（例: 製造業／宿泊業／小売業） |
| limit | integer | – | 既定10・最大20 |
| prefecture | string | – | 例: 香川県（全国の制度は常に含む） |
| role | string | – | 相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う |
No output schema declared.
No examples provided.
list_services アドアーチができること（サービス内容・納品物・納期） ~172
アドアーチに依頼できるサービスの種類（撮影・動画制作・YouTube・SNS・TVer・広告媒体・デザイン・WEBサイト・イベントなど）と、種類ごとに依頼の前に確かめる項目（askFor）・納品物・納期を返す。category で絞れる（例: 制作 / TVer / SNS / 採用）。金額は返さない。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| role | string | – | 相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う |
No output schema declared.
No examples provided.
request_order アドアーチに見積・手配を依頼する ~710
アドアーチへの見積・制作・媒体手配のご依頼（仮押さえ）を1件受け付け、受付番号と返答の目安を返す。見積だけのご依頼も受け付ける。種類（kind）ごとに見積に必要な項目があり、hearing に項目と答えが揃っていない場合は保存せず、足りない項目を返す。agreeToTerms が true でない場合も受け付けない。受け付けは契約の成立ではない（お見積りのご承諾後、担当からの確定のご連絡で成立）。担当からは平日9〜18時の営業時間で2時間以内を目安に連絡する。kind: SHOOTING=撮影（location と preferredDates 必須）/ VIDEO=動画制作 / YOUTUBE=YouTubeの運用・動画 / SNS=SNSの撮影・運用 / TVER=TVer広告 / MEDIA=そのほかの広告媒体（mediaName に媒体名）/ DESIGN=デザイン / WEB=WEBサイト / EVENT=イベント / CREATIVE=そのほかのクリエイティブ / OTHER=その他・見積だけ / CREATOR=クリエイター・制作会社としての登録希望（登録ページを返し、保存しない）。
| Name | Type | Req | Description |
|---|---|---|---|
| agreeToTerms | boolean | yes | ご本人がご利用条件（担当する拠点への共有・見込み先としての記録を含む）に同意したかどうか。true でない場合は受け付けない |
| budgetRange | string | – | 予算の目安（任意） |
| companyName | string | yes | 会社名（個人事業の方は屋号） |
| contactName | string | yes | 担当者のお名前 |
| detail | string | yes | ご依頼の内容（ここまでの会話をまとめた文。2000字まで） |
| string | yes | 連絡先メール | |
| hearing | array | – | 見積に必要な項目とご本人の答え（OTHER は不要）。揃っていない項目があると受け付けられず、足りない項目が返る |
| kind | string | yes | – |
| location | string | – | 撮影地・実施場所（例: 香川県高松市） |
| mediaName | string | – | 媒体の購入のとき、媒体名（例: 地元ラジオ・駅のサイネージ） |
| phone | string | – | 電話（任意） |
| prefecture | string | – | 会社の所在地の都道府県（日本国内の会社のとき。海外の会社は空のまま、国名を detail に書く） |
| preferredDates | string | – | 希望の日時・時期（幅のある書き方でよい） |
| role | string | – | 相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う |
No output schema declared.
No examples provided.
suggest_media 手配できる広告媒体（アドアーチがやること・始めるまでの日数・単位） ~326
アドアーチが手配できる広告媒体の一覧と、媒体ごとの「アドアーチが行うこと・始めるまでの日数・単位・動画の形式・見積の依頼方法」を返す。地域（都道府県・市区町村）を渡すと、TVerはそのエリアの月額の目安の下限（税抜）も返す。media に媒体名を渡すとその媒体だけを返す。TVer以外の金額は返さない。
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | 市区町村（例: 高松市） |
| industry | string | – | 業種 |
| media | string | – | 特定の媒体だけ詳しく知りたいとき（例: シネアド / LINE / 折込） |
| prefecture | string | – | 地域の都道府県（例: 香川県） |
| purpose | string | yes | 用途・目的（例: 採用 / 見学会の集客 / 新商品の告知） |
| role | string | – | 相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う |
| target | string | – | 届けたい相手（例: 20代の求職者 / 近所の家族連れ） |
No output schema declared.
No examples provided.
tver_area_plan TVer広告のエリアの月額の目安（◯円から） ~222
都道府県と市区町村を指定すると、そのエリアのTVer広告の月額の目安の下限（◯円から・税抜）と、最短の期間を返す。allCities: true で県内の全市区町村を人口の多い順に返す。プランごとの月額と届く人数の目安は返さない。
| Name | Type | Req | Description |
|---|---|---|---|
| allCities | boolean | – | 県内の全市区町村をまとめて |
| city | string | – | 例: 高松市（省略で県内の最大の市） |
| prefecture | string | yes | 例: 香川県（「県」「府」「都」まで） |
| role | string | – | 相手の立場：company＝制作・広告を頼む側の企業／creator＝制作者・クリエイター／agency＝広告代理店・制作会社（同業）。立場によって使えるツールが違う |
No output schema declared.
No examples provided.
What is the Ad Arch Agents MCP server?
Ad Arch Agents is an MCP server listed in the public MCP registry as jp.co.adarch/agents. Request quotes for video, shooting, social media, ad media, design, web and events in Japan. This page covers its hosted endpoint (https://agents.adarch.co.jp/mcp).
Is the Ad Arch Agents MCP server safe to use?
Ad Arch Agents 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 Ad Arch Agents MCP server expose?
Ad Arch Agents exposes 7 tools: list_services, request_order, suggest_media, tver_area_plan, find_subsidies, and 2 more. Their descriptions and schemas cost roughly 1,994 tokens of context every time the server is loaded.
Does the Ad Arch Agents MCP server require authentication?
No. We connected to Ad Arch Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ad Arch Agents MCP server still maintained?
Ad Arch Agents is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.