不動産情報検索・分析 MCP
REMOTE · MCP.N-3.AI · SCANNED AUG 3
中小企業庁が公開している公共調達情報を検索するためのサービスです。
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 →
Endpoint Security63
- 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 not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 960 tokens (~960/item across 1 items; 1 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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.n-3.ai
claude mcp add --transport http n-3inc-kkj https://mcp.n-3.ai/mcp?tools=kkj-search
[mcp_servers.n-3inc-kkj] url = "https://mcp.n-3.ai/mcp?tools=kkj-search"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"n-3inc-kkj": {
"type": "remote",
"url": "https://mcp.n-3.ai/mcp?tools=kkj-search",
"enabled": true
}
}
} openclaw mcp add n-3inc-kkj --url https://mcp.n-3.ai/mcp?tools=kkj-search --transport streamable-http
mcp_servers:
n-3inc-kkj:
url: "https://mcp.n-3.ai/mcp?tools=kkj-search" {
"mcpServers": {
"n-3inc-kkj": {
"type": "http",
"url": "https://mcp.n-3.ai/mcp?tools=kkj-search"
}
}
} 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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 27 Jul 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 Jul 26 60
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 3 Aug 2026 · Probed https://mcp.n-3.ai/mcp?tools=kkj-search
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=n-3.ai | CN=WE1,O=Google Trust Services,C=US | 1 Jul 2026 | 29 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | c5fb7b27aadb98fc13520b0defe9d256 |
| SANs: n-3.ai, mcp.n-3.ai | ||||||
| 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 |
DNSSEC insecure
Validation of mcp.n-3.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| n-3.ai. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.n-3.ai/mcp?tools=kkj-search | Verified | 200 | |
| http (plaintext) | http://mcp.n-3.ai/mcp?tools=kkj-search | Inconclusive | 406 |
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.
kkj-search 公共調達情報検索 / Public Procurement Information Search ~960
公共調達情報を検索します。検索クエリ、件名、機関名、都道府県コード、カテゴリ（物品、工事、役務）などのパラメータを使用して詳細な検索が可能です。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | カテゴリー (1:物品, 2:工事, 3:役務) |
| certification | array | — | 入札資格 (A, B, C, D) |
| cftIssueDate | string | — | 公告日またはデータ取得日の範囲。日付は YYYY-MM-DD 形式で「開始日/終了日」のように指定する（例: "2026-07-01/2026-07-15"。開始日のみ: "2026-07-01/"、終了日のみ: "/2026-07-15"、単日: "2026-07-14/2026-07-14"） |
| count | integer | — | 返却する検索結果の最大件数（1〜1000、デフォルト: 10）。API にページングはないため、総ヒット件数（応答の SearchHits）がこれを超える場合は count を増やすか、cftIssueDate などの日付範囲で条件を分割して取得する |
| lgCode | array | — | 都道府県コード (JIS X0401): 北海道=01, 青森県=02, 岩手県=03, 宮城県=04, 秋田県=05, 山形県=06, 福島県=07, 茨城県=08, 栃木県=09, 群馬県=10, 埼玉県=11, 千葉県=12, 東京都=13, 神奈川県=14, 新潟県=15, 富山県=16, 石川県=17, 福井県=18, 山梨県=19, 長野県=20, 岐阜県=21, 静岡県=22, 愛… |
| maxDescriptionLength | integer | — | 公告本文（ProjectDescription）の最大文字数（デフォルト: 1000）。超過分は切り詰められ ProjectDescriptionTruncated が true になる。全文が必要な場合は大きな値を指定するか、ExternalDocumentURI の原文書を参照する |
| openingTendersEvent | string | — | 開札日の範囲。YYYY-MM-DD 形式で「開始日/終了日」のように指定する（例: "2026-07-01/2026-08-31"。片側のみも可） |
| organizationName | string | — | 機関名 |
| periodEndTime | string | — | 納入期限日の範囲。YYYY-MM-DD 形式で「開始日/終了日」のように指定する（例: "2026-07-01/2026-12-31"。片側のみも可） |
| procedureType | string | — | 公示種別 (1:一般競争入札, 2:簡易公募型競争入札, 3:簡易公募型指名競争入札) |
| projectName | string | — | 件名 |
| query | string | — | 検索文字列 |
| tenderSubmissionDeadline | string | — | 入札開始日の範囲。YYYY-MM-DD 形式で「開始日/終了日」のように指定する（例: "2026-07-01/2026-08-31"。片側のみも可: "2026-07-01/"） |
| Name | Type | Req | Description |
|---|---|---|---|
| SearchHits | number | — | 検索条件に該当した総ヒット件数（常に返る）。SearchResult の件数（最大 count 件）がこれより少ない場合、続きは cftIssueDate などの日付範囲で条件を分割して取得する（この API にページングはない） |
| SearchResult | array | — | 検索結果の一覧（最大 count 件） |
| message | string | — | 0件時の案内 |
No examples provided.