Japan Real Estate Intel
REMOTE · REALESTATE-MCP.JP · 2 COMPONENTS · SCANNED SEP 20
Japan real estate MCP: land price, risk, foot traffic, renovation. 10 prefectures.
Available components
Recent critical change
TLS certificate (19 Sept 2026). See the changelog before you install this server.
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 Security0
- TLS check failed: the certificate is expired or not yet valid (as of 2026-08-07). See how to fix → View diagnostics → Fail
- 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 TLS certificate failed verification. 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 Real Estate Intel MCP server?
Japan Real Estate Intel is a hosted endpoint at https://realestate-mcp.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 · realestate-mcp.jp
claude mcp add --transport http sugukurukabe-japan-real-estate-intel-mcp 'https://realestate-mcp.jp/mcp'
{
"mcpServers": {
"sugukurukabe-japan-real-estate-intel-mcp": {
"url": "https://realestate-mcp.jp/mcp"
}
}
} {
"servers": {
"sugukurukabe-japan-real-estate-intel-mcp": {
"type": "http",
"url": "https://realestate-mcp.jp/mcp"
}
}
} [mcp_servers.sugukurukabe-japan-real-estate-intel-mcp] url = "https://realestate-mcp.jp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sugukurukabe-japan-real-estate-intel-mcp": {
"type": "remote",
"url": "https://realestate-mcp.jp/mcp",
"enabled": true
}
}
} openclaw mcp add sugukurukabe-japan-real-estate-intel-mcp --url 'https://realestate-mcp.jp/mcp' --transport streamable-http
mcp_servers:
sugukurukabe-japan-real-estate-intel-mcp:
url: "https://realestate-mcp.jp/mcp" {
"McpServers": {
"sugukurukabe-japan-real-estate-intel-mcp": {
"Transport": "http",
"Url": "https://realestate-mcp.jp/mcp"
}
}
} assistant mcp add sugukurukabe-japan-real-estate-intel-mcp -t streamable-http -u 'https://realestate-mcp.jp/mcp'
{
"mcpServers": {
"sugukurukabe-japan-real-estate-intel-mcp": {
"type": "http",
"url": "https://realestate-mcp.jp/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.
- 20 Sept 26 0
- HTTPS: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but the TLS certificate failed verification. security
- 19 Sept 26 0
- TLS certificate: pass → fail ▼ critical
- Score status: scored → failed ▼ critical
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HTTPS: unverified → pass ▲ security
- 17 Sept 26 0
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. security
- 16 Sept 26 −5
- HTTPS: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but the TLS certificate failed verification. security
- 15 Sept 26 +5
- HTTPS: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. security
- 12 Sept 26 0
- Transport: Transport check failed: declared streamable-http, but the TLS certificate failed verification. security
- 10 Sept 26 0
- Endpoint reachability: unreachable → not serving MCP ▼ security
- HTTPS: pass → unverified ▼ security
- 9 Sept 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HTTPS: unverified → pass ▲ security
- Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. security
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://realestate-mcp.jp/mcp
TLS invalid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
Chain error: expired
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=realestate-mcp.jp | CN=E8,O=Let's Encrypt,C=US | 9 May 2026 | 7 Aug 2026 | ECDSA 256 | ECDSA-SHA384 | 6b8fd5190f74dd2de2dda4d2d1cb16594cf |
| SANs: realestate-mcp.jp | ||||||
| CN=E8,O=Let's Encrypt,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 Mar 2024 | 12 Mar 2027 | ECDSA 384 | SHA256-RSA | 63959363c24e7082715918bfc3d7ed56 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of realestate-mcp.jp. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| jp. | present | 33631 | 8 | Verified |
| realestate-mcp.jp. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://realestate-mcp.jp/mcp | TLS failed | ||
| http (plaintext) | http://realestate-mcp.jp/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 →
No tool schema has been captured from this endpoint yet.
What is the Japan Real Estate Intel MCP server?
Japan Real Estate Intel is an MCP server listed in the public MCP registry as io.github.sugukurukabe/japan-real-estate-intel-mcp. Japan real estate MCP: land price, risk, foot traffic, renovation. 10 prefectures. This page covers its hosted endpoint (https://realestate-mcp.jp/mcp).
Does the Japan Real Estate Intel MCP server require authentication?
No. We connected to Japan Real Estate Intel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan Real Estate Intel MCP server still maintained?
Japan Real Estate Intel is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 18 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.