Uptime (30d)%100.0

Latency (p50)781 msfaster than 28% of servers

Protocol eraunknown

Tools—

Japan Company Leads Finder

https://gbiz-leads-mcp.easakura.workers.dev/mcp ↗

Japan Company Leads Finder is a remote MCP server published at gbiz-leads-mcp.easakura.workers.dev. It has been probed 33 times since 9/4/2026. It answered in 33 of them (100.0%), a near-uninterrupted record. Median response time is 781 ms, a delay an agent will notice. Its tool list could not be read; the server is closed to direct calls.

B2B leads for Japan: search 1M+ companies by size, capital, location, subsidy history (gBizINFO).

UnknownSpec: unknownVersion: —First probe: 2026-09-04 15:47:51Last probe: 2026-09-07 02:57:58

Agent readability score

Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.

Agent readability score

Clear tool descriptions with distinct functions but lacks detailed error handling.based on measured tool list

Strengths

Explicit parameter requirements
Non-overlapping tool functions
Scenario-specific use cases

Weaknesses

Missing error constraint documentation
Input schema details are abstracted

search_companies — Could benefit from clearer parameter constraints
get_company_profile — No mention of data freshness guarantees
get_company_subsidies — Missing guidance on historical data depth

Verdict

Tools are well-structured for B2B lead targeting but require more concrete error handling documentation to meet 85/100 readability standards.

9/6/2026, 4:18:20 PM

Event narrative

Raw observations

Run	Era	Modern	ms	Legacy	ms	Versions
2026-09-07 02:57:58	Unknown	404	114	404	120	—
2026-09-07 00:27:42	Unknown	404	113	404	128	—
2026-09-06 22:36:06	Legacy	400	210	200	676	2025-11-25
2026-09-06 20:44:13	Legacy	400	229	200	758	2025-11-25
2026-09-06 18:49:47	Legacy	400	295	200	1208	2025-11-25
2026-09-06 16:56:18	Legacy	400	1749	200	2263	2025-11-25
2026-09-06 15:42:25	Legacy	400	265	200	988	2025-11-25
2026-09-06 13:49:02	Legacy	400	387	200	1292	2025-11-25
2026-09-06 11:55:12	Legacy	400	364	200	855	2025-11-25
2026-09-06 10:02:05	Legacy	400	1381	200	1857	2025-11-25

Supported versions

—

as declared by server/discover + initialize

Capabilities

—

not readable

Schema score

—

not measurable

Era history

Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.

Era distribution

Legacy94%Unknown6%

Unknown07.09 02:57

04.09 15:47Measurements: 3307.09 02:57

LegacyUnknown

Response time history

The two probe legs separately: modern server/discover and legacy initialize.

server/discoverinitialize

Event log

Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.

3 hours agoSupported versions: 2025-11-25 → —
3 hours agoEra changed: Legacy → Unknown
3 days agoAdded to watch — era: Legacy

Get your badge

Add this badge to your README — it updates automatically as measurements change.

Markdown

[![mcpmetrics](https://mcpmetrics.io/badge/io.github.easakura/japan-company-leads-mcp/era.svg)](https://mcpmetrics.io/servers/io-github-easakura-japan-company-leads-mcp)

HTML

<a href="https://mcpmetrics.io/servers/io-github-easakura-japan-company-leads-mcp"><img src="https://mcpmetrics.io/badge/io.github.easakura/japan-company-leads-mcp/era.svg" alt="mcpmetrics"></a>

Raw observations

You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.