Japan Company Leads Finder
REMOTE · GBIZ-LEADS-MCP.EASAKURA.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 20
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 → Why this is hard to 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.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.
How do I install the Japan Company Leads Finder MCP server?
Japan Company Leads Finder is a hosted endpoint at https://gbiz-leads-mcp.easakura.workers.dev/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 · gbiz-leads-mcp.easakura.workers.dev
claude mcp add --transport http easakura-japan-company-leads-mcp 'https://gbiz-leads-mcp.easakura.workers.dev/mcp'
{
"mcpServers": {
"easakura-japan-company-leads-mcp": {
"url": "https://gbiz-leads-mcp.easakura.workers.dev/mcp"
}
}
} {
"servers": {
"easakura-japan-company-leads-mcp": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://gbiz-leads-mcp.easakura.workers.dev/mcp"
}
}
} assistant mcp add easakura-japan-company-leads-mcp -t streamable-http -u '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.
- 7 Sept 26 −57
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 31 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
- 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 0
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 20 Sept 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 | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a7163aae2923cc020e1322b0e402e606 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 | 404 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gbiz-leads-mcp.easakura.workers.dev/mcp | HTTP error | 404 | |
| http (plaintext) | http://gbiz-leads-mcp.easakura.workers.dev/mcp | Inconclusive | 404 |
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 →
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.
What is the Japan Company Leads Finder MCP server?
Japan Company Leads Finder is an MCP server listed in the public MCP registry as io.github.easakura/japan-company-leads-mcp. B2B leads for Japan: search 1M+ companies by size, capital, location, subsidy history (gBizINFO). This page covers its hosted endpoint (https://gbiz-leads-mcp.easakura.workers.dev/mcp).
Is the Japan Company Leads Finder MCP server safe to use?
Japan Company Leads Finder scores 18 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 Japan Company Leads Finder MCP server expose?
Japan Company Leads Finder exposes 4 tools: search_companies, get_company_profile, get_company_subsidies, get_company_procurement. Their descriptions and schemas cost roughly 552 tokens of context every time the server is loaded.
Does the Japan Company Leads Finder MCP server require authentication?
No. We connected to Japan Company Leads Finder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan Company Leads Finder MCP server still maintained?
Japan Company Leads Finder is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.