Is the Easakura Japan Real Estate MCP server down?

mcp-registry/io.github.easakura/japan-real-estate-mcp · v0.1.0

Also listed as glama/easakura/japan-real-estate-mcp

unknown
Last checked 2026-10-22 03:47 UTC · handshake 173ms

As of 2026-10-22 03:47 UTC, the Easakura Japan Real Estate MCP server is unknown with a Glimind reliability score of 51/100 (grade D). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.

uptime (30d checks)
0%
checks observed
4
outages (90d)
1
tools
3

Japan real estate transaction prices and official land values (MLIT data) by area, year, and type.

Point your MCP client at this streamable-http endpoint: https://fudousan-mcp.easakura.workers.dev/mcp

Agent-readiness: C (75/100)

C (75/100): 1 error(s), 1 warning(s) across 3 tool(s); ~455 tokens of tool definitions.
Scores higher than 10% of 15,752 MCP servers Glimind has audited.
Its tool list costs an agent ~455 tokens per session — lighter than 95% of servers.
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (3)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: get_land_price, list_municipalities, search_transactions

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.easakura%2Fjapan-real-estate-mcp/fixes

get_land_price 1 change 
{
  "name": "get_land_price",
  "description": "指定した都道府県・市区町村の地価公示価格（毎年1月1日時点の公的な土地評価額、いわゆる公示地価）を取得する。実勢の取引価格より安定した「公的基準地価」を知りたい場合に使う。",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "prefecture",
      "city_code",
      "year"
    ],
    "properties": {
      "year": {
        "type": "integer",
        "maximum": 2026,
        "minimum": 2005,
        "description": "公示年（例: 2025）"
      },
      "city_code": {
        "type": "string",
        "description": "市区町村コード5桁（list_municipalitiesで取得）"
      },
      "prefecture": {
        "type": "string",
        "description": "都道府県名（例: 東京都）"
      },
      "max_results": {
        "type": "integer",
        "default": 20,
        "maximum": 100,
        "minimum": 1,
        "description": "最大件数"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "地価公示・地価調査価格を取得"
}
list_municipalities 1 change 
{
  "name": "list_municipalities",
  "description": "都道府県名を指定して、その中の市区町村コード一覧を取得する。取引価格検索（search_transactions）に必要なcity codeの調べ物に使う。",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "prefecture"
    ],
    "properties": {
      "prefecture": {
        "type": "string",
        "description": "都道府県名（例: 東京都）"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "都道府県内の市区町村コード一覧を取得"
}
search_transactions 1 change 
{
  "name": "search_transactions",
  "description": "国土交通省の不動産取引価格情報（実際に成約した価格）を検索する。都道府県・市区町村・四半期を指定。市区町村コードが不明な場合はlist_municipalitiesで調べる。土地・戸建て・マンション等の実取引価格を含む、地価公示より生々しい相場データ。",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "prefecture",
      "year"
    ],
    "properties": {
      "year": {
        "type": "integer",
        "maximum": 2026,
        "minimum": 2005,
        "description": "取引年（例: 2025）"
      },
      "quarter": {
        "type": "integer",
        "maximum": 4,
        "minimum": 1,
        "description": "四半期（1〜4）。省略時は年間全体"
      },
      "city_code": {
        "type": "string",
        "description": "市区町村コード5桁（list_municipalitiesで取得。省略時は都道府県全体）"
      },
      "prefecture": {
        "type": "string",
        "description": "都道府県名（例: 東京都）"
      },
      "max_results": {
        "type": "integer",
        "default": 20,
        "maximum": 100,
        "minimum": 1,
        "description": "最大件数（1〜100）"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "不動産取引価格を検索"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.easakura/japan-real-estate-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.easakura/japan-real-estate-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.easakura%2Fjapan-real-estate-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.easakura%2Fjapan-real-estate-mcp?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.easakura%2Fjapan-real-estate-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.easakura%2Fjapan-real-estate-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.easakura%2Fjapan-real-estate-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.easakura%2Fjapan-real-estate-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:aac51ce896ef9923…, first seen 2026-10-17, included at leaf 15348 of 72,872. Version history · verify what your client received.

Tools (3)

Compare: most reliable data servers · most reliable retrieval servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Easakura Japan Real Estate MCP server down right now?

As of 2026-10-22 03:47 UTC, the Easakura Japan Real Estate MCP server is unknown with a Glimind reliability score of 51/100 (grade D). Over the last 30 days it answered 0% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.

How many tools does Easakura Japan Real Estate MCP server provide?

Easakura Japan Real Estate MCP server advertises 3 tools, including get_land_price, list_municipalities, search_transactions.

How do I install Easakura Japan Real Estate MCP server?

Point your MCP client at this streamable-http endpoint: https://fudousan-mcp.easakura.workers.dev/mcp

Is the Easakura Japan Real Estate MCP server safe to connect to an AI agent?

Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Easakura Japan Real Estate MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve