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.

入札案件観測所

REMOTE · MCP.KANSOKUJO.JP

Japan public procurement: open tenders, upcoming bid plans, and award results since 2004.

Available components

73 Trust /100

Last scanned (19 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

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 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 2877 tokens (~359/item across 8 items; 8 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 21 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.

  • 19 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.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • “search_bid_notices” added an optional parameter “changed_since” cosmetic
  • 17 Nov 26 71

    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 21 Nov 2026 · Probed https://mcp.kansokujo.jp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kansokujo.jp CN=WE1,O=Google Trust Services,C=US 17 Nov 2026 15 Feb 2027 ECDSA 256 ECDSA-SHA256 c0a04c32397ecbd130d3e37c5aefed3
SANs: kansokujo.jp, mcp.kansokujo.jp, *.mcp.kansokujo.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.kansokujo.jp. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
jp. DS published 6961 8 Verified
kansokujo.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.kansokujo.jp/mcp Verified 200
http (plaintext) http://mcp.kansokujo.jp/mcp HTTPS enforced 301 https://mcp.kansokujo.jp/mcp
MCP tools · 8 exposed · ~2,651 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_bid_notice ~104

Get the key points of one open tender notice (summary, procedure and deadlines, eligibility, place, period) and the link to the original notice. Use the notice_id from search_bid_notices. Summaries are machine-made; the original document is authoritative. 入札公告の概要・締切・参加資格・原文

NameTypeReqDescription
notice_idstringyesID from search_bid_notices, e.g. kkj-156722 or ext-4418
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
closed_reasonstring––
data_as_ofstringyes–
deadline_kindsarray–Each date in deadlines with what it is (participation application, bid submission, opening, question, notification, document issue, briefing, unknown)
deadline_notestring––
deadlinesarray––
eligibilitystring––
existsboolean–When found is false: true if the notice exists but is no longer open (access not_public_now), false if no such notice is known
expiredboolean––
foundbooleanyes–
last_datestring––
messagestring––
notestringyes–
notice_idstring––
original_urlstring––
periodstring––
placestring––
procedurestring––
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
retrievedstringyes–
search_urlstring––
sourcestringyes–
summarystring––
titlestring––
urlstringyes–

No examples provided.

get_buyer_profile ~210

Summary of one procuring entity in Japan (ministry, agency, prefecture, city, public corporation): award counts by year and category, most frequent suppliers, and its currently open notices. If the name matches several entities, candidates are returned instead of a guess. When records exist only per department (e.g. 岡崎市 総務部契約課), a city or prefecture name returns the departments combined (`departments`). 発注機関・官公庁・自治体

NameTypeReqDescription
areastring–Prefecture, to tell same-name entities apart. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
buyerstringyesName (e.g. 福岡市, 国交省) or buyer_id
response_formatstring–concise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
ambiguousboolean––
areastring––
awards_by_categoryarray––
awards_by_yeararray––
awards_totalnumber––
buyer_idstring––
candidatesarray––
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
data_as_ofstringyes–
foundbooleanyes–
levelstring––
messagestring––
namestring––
notestringyes–
open_noticesarray––
open_notices_totalnumber––
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
retrievedstringyes–
sourcestringyes–
top_suppliersarray––
urlstringyes–

No examples provided.

get_coverage ~166

What this server covers and does not cover: counts, period, last update, and which claims the data can and cannot support. Use this before stating that something does not exist. It describes the data set itself (what is included, how recent), not a region's or buyer's activity: for trends, top suppliers or counts of a prefecture, city or agency (e.g. 静岡県 as a buyer), use get_buyer_profile or search_awards. 収録範囲・更新日・網羅性

NameTypeReqDescription
areastring–Optional prefecture: adds the number of covered buyers and results there. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
awardsobjectyes–
buyersnumberyes–
can_sayarrayyes–
cannot_sayarrayyes–
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
data_as_ofstringyes–
notestringyes–
open_noticesobjectyes–
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
retrievedstringyes–
sourcestringyes–
suppliers_with_profilenumberyes–
urlstringyes–

No examples provided.

get_supplier_profile ~194

Summary of one company's public-sector award record in Japan: counts by year and category, main buyers, and recent awards. Accepts a company name or the 13-digit corporate number (法人番号). Corporations only; individuals and joint ventures are excluded. 落札企業・受注実績・競合

NameTypeReqDescription
areastring–Prefecture of the head office, to tell same-name companies apart. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
response_formatstring–concise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.
supplierstringyesCompany name as the user wrote it (legal form such as 株式会社 may be omitted), 13-digit corporate number, or supplier_id. A name matching several companies returns candidates
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
aliasesarray––
ambiguousboolean––
awards_by_categoryarray––
awards_by_yeararray––
awards_totalnumber––
candidatesarray––
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
confirmedboolean––
corporate_numberstring––
data_as_ofstringyes–
foundbooleanyes–
messagestring––
namestring––
notestringyes–
recent_awardsarray––
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
retrievedstringyes–
sourcestringyes–
supplier_idstring––
top_buyersarray––
urlstringyes–

No examples provided.

resolve_names ~198

Find buyers or suppliers by partial name, abbreviation or former name (e.g. 国交省, NTT, 旧 防衛庁) and get their IDs. Only for when the user wants to look up or list names, or when another tool returned candidates; the buyer and supplier arguments of the other tools already accept names and abbreviations such as 国交省, so do not call this first. 発注機関・企業の名前の検索

NameTypeReqDescription
areastring–Prefecture. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
kindstring–buyer = procuring entities, supplier = companies, any (default) = both
limitnumber–1-10 (default 10)
querystringyesPart of a name, an abbreviation, or a 13-digit corporate number
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
candidatesarrayyes–
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
data_as_ofstringyes–
messagestring––
notestringyes–
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
retrievedstringyes–
sourcestringyes–
totalnumberyes–
urlstringyes–

No examples provided.

search_awards ~654

Use this when the user asks who won, or how often, in Japanese public procurement: award and contract results from 2004 onward for national agencies and local governments. Filter by keyword, buyer, supplier, area, category and period; set group_by to get counts instead of rows. At least one of keyword, buyer, supplier or a non-default status is required. Counts include only results that reached an award or contract; unsuccessful (不調), cancelled (中止) and unresolved (結果未確定) records are counted separately in not_awarded, or listed with status. Amounts are shown as bands. 落札結果・契約結果・落札者・随意契約

NameTypeReqDescription
areastring–Prefecture of the buyer. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
buyerstring–Procuring entity: name, abbreviation (国交省) or buyer_id
categorystring–物品=goods/supplies, 工事=construction works, 役務=services/outsourcing (業務委託), 保守=maintenance, 設計・調査=design/survey/consulting, IT=systems/software/IT equipment, 賃貸借=lease/rental, イベント=events, その他=other
cursorstring–next_cursor from the previous result, with the same other arguments. Up to 3 pages.
date_fromstring–Result date on or after, YYYY-MM-DD
date_tostring–Result date on or before, YYYY-MM-DD
fiscal_yearnumber–Japanese fiscal year (April to March). 2024 = 2024-04-01 to 2025-03-31 = 令和6年度. 令和N年度 = 2018+N.
group_bystring–none (default): rows, newest first. Otherwise counts per group: all years, the top 10 buyers/suppliers/categories, or all amount bands (amount_band: number of records in each published-amount band, p…
keywordstring–Words in the contract title. Space = AND. Example: 庁舎 清掃
limitnumber–Rows per page, 1-10 (default 10)
response_formatstring–concise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.
statusstring–awarded (default): only results that reached an award or contract (落札・契約). unsuccessful = 不調 (no valid bid), cancelled = 中止, unresolved = 結果未確定 (published without a winner), not_awarded = those three…
supplierstring–Winning company: name as the user wrote it, 13-digit corporate number (法人番号) or supplier_id. A name matching several companies returns candidates
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
appliedobjectyes–
candidatesobject––
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
data_as_ofstringyes–
groupsarray––
hintsarray––
messagestring––
next_cursorstring––
notestringyes–
period_notestring––
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
resultsarray––
retrievedstringyes–
returnednumberyes–
sourcestringyes–
totalnumber––
total_all_periodsnumber–When a period (date_from, date_to or fiscal_year) is given: the count for the same conditions without the period
urlstringyes–

No examples provided.

search_bid_notices ~664

Use this when the user asks which public tenders are open now in Japan (national agencies, prefectures, municipalities), by keyword, area, category, buyer or deadline. Returns up to 10 notices, nearest deadline first, with the total count. Not for past results: use search_awards. Includes nominated tenders and requests for comments, marked by `notice_type`; use `types` to leave them out. For tenders not yet announced, use search_bid_plans. 受付中の入札公告・公募・プロポーザル・見積合わせ・指名競争・意見招請(官公需・調達)

NameTypeReqDescription
areastring–Prefecture. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
buyerstring–Procuring entity: name (part of it is fine, e.g. 福岡市) or a buyer_id
categoriesarray–One or more of: 物品=goods/supplies, 工事=construction works, 役務=services/outsourcing (業務委託), 保守=maintenance, 設計・調査=design/survey/consulting, IT=systems/software/IT equipment, 賃貸借=lease/rental, イベント=even…
changed_sincestring–Only notices that are new or whose title, deadline, method, eligibility, procedure, period or place changed on or after this date, YYYY-MM-DD (for example yesterday, for "what is new or changed since…
cursorstring–next_cursor from the previous result, with the same other arguments. Up to 3 pages.
deadline_fromstring–Deadline on or after this date, YYYY-MM-DD. The result's `today` field gives the current date in Japan. A deadline range leaves out notices whose deadline could not be read; `deadline_unknown_count`…
deadline_tostring–Deadline on or before this date, YYYY-MM-DD
keywordstring–Words in the title or summary. Space = AND. Example: 庁舎 清掃
limitnumber–Rows per page, 1-10 (default 10)
response_formatstring–concise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.
sortstring–deadline (default): nearest deadline first. newest: most recently published first.
typesarray–bid = tenders anyone qualified can apply for; nominated = 指名競争入札, only companies the buyer nominates can bid (no application); opinion = 意見招請・資料提供招請, requests for comments or information, not a tende…
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
appliedobjectyes–
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
data_as_ofstringyes–
deadline_notestring––
deadline_unknown_countnumber––
hintsarray––
messagestring––
next_cursorstring––
no_area_countnumber––
notestringyes–
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
resultsarrayyes–
retrievedstringyes–
returnednumberyes–
sourcestringyes–
todaystringyes–
totalnumberyes–
urlstringyes–

No examples provided.

search_bid_plans ~461

Use this when the user asks what public works, services or goods Japanese buyers plan to put out to tender in the coming months (発注の見通し), before the tender notice is published. Returns up to 10 planned procurements, soonest period first, with the total count and counts per quarter. Periods are as published by the buyer (Japanese fiscal year starts in April). For tenders already open, use search_bid_notices. 入札予定・発注の見通し・発注予定(工事・委託・物品役務)

NameTypeReqDescription
areastring–Prefecture. Accepts 福岡県, 福岡, Fukuoka, 40 (JIS code), national (国の機関)
buyerstring–Procuring entity: name (part of it is fine) or a buyer_id from resolve_names / get_buyer_profile
cursorstring–next_cursor from the previous result, with the same other arguments. Up to 3 pages.
fiscal_yearnumber–Japanese fiscal year (April to March), e.g. 2026 = 2026-04 to 2027-03
include_announcedboolean–true: also return plans whose tender notice has already been published (with a link to it). Default false.
keywordstring–Words in the title, buyer, department, work type or place. Space = AND. Example: 舗装 修繕
kindstring–工事 = construction works, 委託 = consulting/survey/design and other outsourcing, 物品役務 = goods and services
limitnumber–Rows per page, 1-10 (default 10)
quarternumber–Quarter of the fiscal year: 1 = Apr-Jun, 2 = Jul-Sep, 3 = Oct-Dec, 4 = Jan-Mar. Without fiscal_year and quarter, plans from the current quarter on are returned (and those with no period given).
response_formatstring–concise (default): fewer fields per row. detailed: adds IDs, method, original URL and retrieval date per row.
NameTypeReqDescription
accessstring–Whether this result is shown in full through this server: public = yes; not_public_now = the item exists but this server does not return it at present (e.g. a notice whose deadline has passed); login…
appliedobjectyes–
by_quarterarray––
cite_asstring–One-line source citation for this result: the page title on 入札案件観測所, the data date, and the URL of that page (same as `url`).
data_as_ofstringyes–
hintsarray––
messagestring––
next_cursorstring––
notestringyes–
relatedarray–Facts related to this result (counts) and the tool call that returns them
restrictedarray–Items that exist but are not returned here, with their access value. An item listed here is not missing from the data.
resultsarrayyes–
retrievedstringyes–
returnednumberyes–
sourcestringyes–
todaystringyes–
totalnumberyes–
urlstringyes–

No examples provided.

Install

How do I install the 入札案件観測所 MCP server?

入札案件観測所 is a hosted endpoint at https://mcp.kansokujo.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.kansokujo.jp

# add to Claude Code
claude mcp add --transport http jp-kansokujo-bids 'https://mcp.kansokujo.jp/mcp'
Common questions

What is the 入札案件観測所 MCP server?

入札案件観測所 is an MCP server listed in the public MCP registry as jp.kansokujo/bids. Japan public procurement: open tenders, upcoming bid plans, and award results since 2004. This page covers its hosted endpoint (https://mcp.kansokujo.jp/mcp).

Is the 入札案件観測所 MCP server safe to use?

入札案件観測所 scores 73 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 8 tools: search_bid_notices, get_bid_notice, search_bid_plans, search_awards, get_buyer_profile, and 3 more. Their descriptions and schemas cost roughly 2,651 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.