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.

io.github.kodandy/jp-biz-opportunity

REMOTE · JP-BIZ-OPPORTUNITY-62KO7B2UWA-AN.A.RUN.APP

Japanese public-sector business opportunities for AI agents: tenders, subsidies, sanctions. x402.

0 this week 78 Trust /100

Last scanned (21 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security57
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 711 tokens (~118/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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.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 6 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 (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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 fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 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
  • 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
  • 26 Aug 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 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
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 21 Nov 2026 · Probed https://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WE2,O=Google Trust Services,C=US 3 Nov 2026 26 Jan 2027 ECDSA 256 ECDSA-SHA256 f668c9036838957b095b05d18ab2228d
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WE2,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 7ff32d6b409d15d5965b05873a7c72e0
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 jp-biz-opportunity-62ko7b2uwa-an.a.run.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
run.app. 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
Header Value
content-security-policy default-src 'none'
x-content-type-options nosniff
x-frame-options DENY

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/mcp Verified 200
http (plaintext) http://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/mcp HTTPS enforced 302 https://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/mcp
MCP tools · 6 exposed · ~711 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
get_subsidy_program ~143

Full raw record of one Japanese subsidy / grant program: sponsor, maximum grant amount, subsidy rate, eligible industries and application window. Paid via x402: each call costs 0.05 USDC. This tool returns the HTTP 402 payment challenge for the resource. Private beta note: a successful settlement is acknowledged with a receipt that records your priority access; the dataset itself unlocks for early settlers as provisioning goes live.

NameTypeReqDescription
subsidy_idstringyesSubsidy program ID: live jGrants id from search_subsidies (e.g. a0WJ200000CDanIMAT), or sample S-2026-NNNN

No output schema declared.

No examples provided.

get_tender_notice ~128

Full raw record of one Japanese public-sector open tender notice: agency, region, category, publication date, submission deadline and specification summary. Paid via x402: each call costs 0.05 USDC. This tool returns the HTTP 402 payment challenge for the resource. Private beta note: a successful settlement is acknowledged with a receipt that records your priority access; the dataset itself unlocks for early settlers as provisioning goes live.

NameTypeReqDescription
tender_idstringyesTender notice ID in the form T-2026-NNNN, e.g. T-2026-0117

No output schema declared.

No examples provided.

list_opportunity_datasets ~69

Free catalog lookup. Lists the raw Japanese public-sector business-opportunity datasets on this gateway (open tender notices, subsidy programs, procurement sanction lists) with per-call x402 pricing (0.05 USDC per call). Use the search/get tools or the returned api_url to retrieve data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_open_tenders ~136

FREE — returns live data. Search nationwide Japanese public-sector tender notices (官公需情報ポータルサイト検索API) by keyword: title, agency, region, category, notice text excerpt and the original document URL. keyword (min 2 chars) is required; region is folded into the query. Attribution included.

NameTypeReqDescription
deadline_within_daysinteger–Only tenders whose submission deadline falls within N days
keywordstring–Free-text keyword, e.g. 空調 or AI チャットボット
regionstring–Region filter, e.g. tohoku, kanto

No output schema declared.

No examples provided.

search_sanctions ~120

Look up suspension-of-nomination (指名停止) and administrative action records for one Japanese corporate number (法人番号). Paid via x402: each call costs 0.05 USDC. This tool returns the HTTP 402 payment challenge for the resource. Private beta note: a successful settlement is acknowledged with a receipt that records your priority access; the dataset itself unlocks for early settlers as provisioning goes live.

NameTypeReqDescription
corporate_idstringyes13-digit Japanese corporate number (法人番号), e.g. 9010001054321

No output schema declared.

No examples provided.

search_subsidies ~115

FREE — returns live data. Search currently-open Japanese subsidy and grant programs (jGrants 公開API) by keyword: titles, deadlines, max amounts, target areas. keyword (min 2 chars) is required. Attribution included.

NameTypeReqDescription
deadline_within_daysinteger–Only programs whose application window closes within N days
industrystring–Industry filter, e.g. manufacturing, tourism
keywordstring–Free-text keyword, e.g. 省力化 or 観光

No output schema declared.

No examples provided.

Install

How do I install the io.github.kodandy/jp-biz-opportunity MCP server?

io.github.kodandy/jp-biz-opportunity is a hosted endpoint at https://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/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 · jp-biz-opportunity-62ko7b2uwa-an.a.run.app

# add to Claude Code
claude mcp add --transport http kodandy-jp-biz-opportunity 'https://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/mcp'
Common questions

What is the io.github.kodandy/jp-biz-opportunity MCP server?

io.github.kodandy/jp-biz-opportunity is an MCP server listed in the public MCP registry as io.github.kodandy/jp-biz-opportunity. Japanese public-sector business opportunities for AI agents: tenders, subsidies, sanctions. x402. This page covers its hosted endpoint (https://jp-biz-opportunity-62ko7b2uwa-an.a.run.app/mcp).

Is the io.github.kodandy/jp-biz-opportunity MCP server safe to use?

io.github.kodandy/jp-biz-opportunity scores 78 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 io.github.kodandy/jp-biz-opportunity MCP server expose?

io.github.kodandy/jp-biz-opportunity exposes 6 tools: list_opportunity_datasets, search_open_tenders, get_tender_notice, search_subsidies, get_subsidy_program, search_sanctions. Their descriptions and schemas cost roughly 711 tokens of context every time the server is loaded.

Does the io.github.kodandy/jp-biz-opportunity MCP server require authentication?

No. We connected to io.github.kodandy/jp-biz-opportunity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.kodandy/jp-biz-opportunity MCP server still maintained?

io.github.kodandy/jp-biz-opportunity 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 io.github.kodandy/jp-biz-opportunity MCP server?

VerifyMCP ran 12 checks on io.github.kodandy/jp-biz-opportunity, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.kodandy/jp-biz-opportunity: Authorization. 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.