agri-ja 日本の農業政策・補助金・米の概算金
REMOTE · AGRI-JA.NET
Japanese agriculture policy, subsidies and rice advance payments. 日本の農業政策・補助金・米の概算金
Available components
Last scanned (19 hours ago)
Scores higher than 10% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
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 yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
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.
- 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
- 19 Oct 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Oct 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- 12 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 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
- 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
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 9 Sept 26 0
- Stability: pass → 0.87 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://agri-ja.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agri-ja.net | CN=YR1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 628b02fbd0932e1305f664d140ab11b6dee |
| SANs: agri-ja.net | ||||||
| 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 agri-ja.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| agri-ja.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 402 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agri-ja.net/mcp | HTTP error | 402 | |
| http (plaintext) | http://agri-ja.net/mcp | HTTPS enforced | 308 | https://agri-ja.net/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 →
find_subsidy 使える補助金・交付金を探す ~392
立場・やりたいこと・品目から、日本の農業で使える補助金/交付金/制度資金の候補を返す。audience は new-farmer(これから始める・就農して間もない) / individual(個人・家族で経営している) / corporation(法人で経営している) / community(集落営農・JA・協議会)。purpose は machine(機械を買う・更新する) / facility(施設・ハウスを建てる) / loan(お金を借りる) / risk(収入減・価格下落に備える) / scale(規模を広げる・農地を増やす) / environment(環境・有機に取り組む) / disaster(被災から立て直す) / sales(売り先を広げる・輸出・加工) / labor(人を雇う・育てる・継ぐ) / crop-payment(作物ごとの交付金を受け取る)。crop は rice(米・水田) / vegetable(野菜) / fruit(果樹) / livestock(畜産) / flower(花き) / field-crop(麦・大豆・畑作) / other(その他・複合)。3つのうち分かるものだけ指定すればよい(最低1つ必要)。金額や補助率は代表的な目安で、実際の要件は公募要領と窓口での確認が必要。
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | 立場 |
| crop | string | – | 品目 |
| purpose | string | – | やりたいこと |
No output schema declared.
No examples provided.
get_article 記事の要点を取得する ~114
agri-ja.net の記事1本について、要点(takeaways)・見出し構成・本文の冒頭抜粋・一次資料の出典URL・更新日を返す。本文全文は返さないので、詳細が必要なときは戻り値の url を読者に案内すること。
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | 記事のslug(例: rice-advance-payment-by-region)。記事URLをそのまま渡してもよい |
No output schema declared.
No examples provided.
rice_advance_payment 米の概算金(令和8年産)を調べる ~319
令和8年産の米について、JA・県ごとの概算金(仮渡金)の提示額を返す。前年(令和7年産)との比較、発表日、未提示かどうかを含む。confirmation は情報源の区分で、決定=JA・全農が決定を自ら発表・公表した金額(announcedOn は発表日)、報道=報道機関の取材で判明しJA・全農は金額を公表していない金額(announcedOn は金額が明らかになった日)。報道もJAが決めた金額であり未決定ではない。回答では両者を区別すること。agri-ja.net が農協・報道発表をもとに独自に集計している一覧で、他に横断的な一覧表はほとんど存在しない。金額は60kgあたりの円。
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | 銘柄・品種で絞り込む(例: あきたこまち、コシヒカリ)。部分一致 |
| onlyAnnounced | boolean | – | true なら発表済みの行だけを返す |
| prefecture | string | – | 都道府県名で絞り込む(例: 秋田、新潟)。部分一致 |
No output schema declared.
No examples provided.
search_articles 記事を検索する ~171
農業情報メディア(agri-ja.net)の解説記事をキーワードで検索する。農林水産省などの一次資料をもとにした、日本の農業政策・補助金・交付金・制度資金・価格や統計の解説記事が対象。スペース区切りの語はすべて含む記事に絞り込まれる。戻り値には記事URLが含まれるので、回答では出典としてそのURLを示すこと。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 最大件数(既定 8、上限 20) |
| query | string | yes | 検索キーワード(例: 概算金 秋田 / 収入保険 デメリット) |
No output schema declared.
No examples provided.
How do I install the agri-ja 日本の農業政策・補助金・米の概算金 MCP server?
agri-ja 日本の農業政策・補助金・米の概算金 is a hosted endpoint at https://agri-ja.net/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 · agri-ja.net
claude mcp add --transport http net-agri-ja-agri-ja 'https://agri-ja.net/mcp'
What is the agri-ja 日本の農業政策・補助金・米の概算金 MCP server?
agri-ja 日本の農業政策・補助金・米の概算金 is an MCP server listed in the public MCP registry as net.agri-ja/agri-ja. Japanese agriculture policy, subsidies and rice advance payments. 日本の農業政策・補助金・米の概算金. This page covers its hosted endpoint (https://agri-ja.net/mcp).
Is the agri-ja 日本の農業政策・補助金・米の概算金 MCP server safe to use?
agri-ja 日本の農業政策・補助金・米の概算金 scores 25 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 agri-ja 日本の農業政策・補助金・米の概算金 MCP server expose?
agri-ja 日本の農業政策・補助金・米の概算金 exposes 4 tools: search_articles, get_article, rice_advance_payment, find_subsidy. Their descriptions and schemas cost roughly 996 tokens of context every time the server is loaded.
Does the agri-ja 日本の農業政策・補助金・米の概算金 MCP server require authentication?
Its publisher declares no required credentials for agri-ja 日本の農業政策・補助金・米の概算金. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the agri-ja 日本の農業政策・補助金・米の概算金 MCP server still maintained?
agri-ja 日本の農業政策・補助金・米の概算金 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 agri-ja 日本の農業政策・補助金・米の概算金 MCP server?
VerifyMCP ran 5 checks on agri-ja 日本の農業政策・補助金・米の概算金, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about agri-ja 日本の農業政策・補助金・米の概算金: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.