Japan Company Leads Finder
REMOTE · GBIZ-LEADS-MCP.EASAKURA.WORKERS.DEV · 2 COMPONENTS · SCANNED AUG 3
B2B leads for Japan: search 1M+ companies by size, capital, location, subsidy history (gBizINFO).
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 552 tokens (~138/item across 4 items; 4 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
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 · gbiz-leads-mcp.easakura.workers.dev
claude mcp add --transport http easakura-japan-company-leads-mcp https://gbiz-leads-mcp.easakura.workers.dev/mcp
[mcp_servers.easakura-japan-company-leads-mcp] url = "https://gbiz-leads-mcp.easakura.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"easakura-japan-company-leads-mcp": {
"type": "remote",
"url": "https://gbiz-leads-mcp.easakura.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add easakura-japan-company-leads-mcp --url https://gbiz-leads-mcp.easakura.workers.dev/mcp --transport streamable-http
mcp_servers:
easakura-japan-company-leads-mcp:
url: "https://gbiz-leads-mcp.easakura.workers.dev/mcp" {
"mcpServers": {
"easakura-japan-company-leads-mcp": {
"type": "http",
"url": "https://gbiz-leads-mcp.easakura.workers.dev/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.
- 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 +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.
- 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.
- 27 Jul 26 +1
- 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://gbiz-leads-mcp.easakura.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=easakura.workers.dev | CN=WE1,O=Google Trust Services,C=US | 13 Jul 2026 | 11 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 997e95d4e676a1e20e6b46db6f16ffd5 |
| SANs: easakura.workers.dev, *.easakura.workers.dev | ||||||
| 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 gbiz-leads-mcp.easakura.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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://gbiz-leads-mcp.easakura.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://gbiz-leads-mcp.easakura.workers.dev/mcp | 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.
get_company_procurement 企業の官公庁取引実績を取得 ~78
法人番号を指定して、その企業の政府調達（官公庁との取引）実績を取得する。官公需に強い企業の発掘や、取引先の信用調査の参考に使える。
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_number | string | yes | 法人番号（13桁） |
No output schema declared.
No examples provided.
get_company_profile 企業プロフィールを取得 ~86
法人番号を指定して企業の詳細プロフィールを取得する：代表者名・役職、従業員数、資本金、設立日、事業概要、会社URL、全省庁統一資格など。営業アプローチの下調べに使う。
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_number | string | yes | 法人番号（13桁） |
No output schema declared.
No examples provided.
get_company_subsidies 企業の補助金受給歴を取得 ~91
法人番号を指定して、その企業が国から受給した補助金の履歴を取得する。「補助金で設備投資した企業」「IT導入補助金の受給企業」など、予算と投資意欲のある企業の発掘に使える。
| Name | Type | Req | Description |
|---|---|---|---|
| corporate_number | string | yes | 法人番号（13桁） |
No output schema declared.
No examples provided.
search_companies 日本企業をリード条件で検索 ~297
日本の法人データベース（経産省gBizINFO、約100万社超の活動情報）から営業リード候補を検索する。都道府県・従業員数・資本金・売上・設立年・補助金受給歴の有無で絞り込める。結果のcorporate_number（法人番号）をget_company_profile / get_company_subsidiesに渡すと詳細が取れる。
| Name | Type | Req | Description |
|---|---|---|---|
| capital_max_yen | integer | — | 資本金の上限（円） |
| capital_min_yen | integer | — | 資本金の下限（円） |
| employees_max | integer | — | 従業員数の上限 |
| employees_min | integer | — | 従業員数の下限 |
| founded_year | integer | — | 設立年（例: 2015） |
| max_results | integer | — | 最大件数（1〜50） |
| name | string | — | 法人名（部分一致） |
| page | integer | — | ページ番号（1〜10） |
| prefecture | string | — | 都道府県名（例: 東京都） |
| with_subsidy_history | boolean | — | trueで国の補助金受給歴がある企業に限定（予算獲得力・投資意欲のシグナル） |
No output schema declared.
No examples provided.