_ registry / mcp http-sse · checked 2h ago

jp-real-estate

https://jp-real-estate-production.mk-career-planning.workers.dev

Registry code: f3aee3498a83c197

api record

What real estate transaction prices has MLIT published for this Japanese municipality? As published.

from a public catalogue that lists it, not from the operator

endpoint
https://jp-real-estate-production.mk-career-planning.workers.dev/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is jp-real-estate live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is jp-real-estate free to use?
Yes — the hub reached it with no key and no payment.
What tools does jp-real-estate have?
4 tools: catalog, realestate_prices_by_municipality, get_receipt, realestate_municipalities.
Is jp-real-estate safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,052ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • catalog unknown never probed

    List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • realestate_prices_by_municipality unknown 2h ago

    What real estate transaction and contract prices has MLIT (Japan) published for this municipality and quarter? Give a 5-digit municipality code and up to 8 quarters (YYYY-Qn). Per quarter and per classification (never pooled): records_published, no_records_published or unknown with a reason, record counts, min/median/max computed by us (null below 5 values), and a capped sample of records as published. Carries the required MLIT credit. Statistics as published; not an appraisal or advice.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "municipality_code",
        "from"
      ],
      "properties": {
        "to": {
          "type": "string",
          "maxLength": 10,
          "description": "Last quarter, e.g. 2025-Q4 (default: same as from). At most 8 quarters per request."
        },
        "from": {
          "type": "string",
          "maxLength": 10,
          "description": "First quarter, e.g. 2025-Q1 (Q1 = Jan-Mar). Transaction prices start at 2005-Q3, contract prices at 2021-Q1."
        },
        "sample_size": {
          "type": "integer",
          "maximum": 50,
          "minimum": 0,
          "description": "Number of published records to include as a sample, 0-50 (default 10). total and truncated tell how many matched."
        },
        "property_type": {
          "enum": [
            "land",
            "land_and_building",
            "used_condominium",
            "agricultural_land",
            "forest_land"
          ],
          "type": "string",
          "description": "Optional filter on MLIT's transaction type: land (宅地(土地)), land_and_building (宅地(土地と建物)), used_condominium (中古マンション等), agricultural_land (農地), forest_land (林地)."
        },
        "municipality_code": {
          "type": "string",
          "maxLength": 10,
          "description": "5-digit Japanese municipality code, e.g. 13101 (Chiyoda, Tokyo). Find codes with realestate_municipalities. Unknown codes are rejected, not guessed."
        },
        "price_classification": {
          "enum": [
            "transaction",
            "contract",
            "both"
          ],
          "type": "string",
          "description": "transaction (MLIT 不動産取引価格情報), contract (MLIT 成約価格情報) or both (default)."
        }
      }
    }
    arguments 51 lines
  • get_receipt unknown 2h ago

    Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "receipt_id"
      ],
      "properties": {
        "receipt_id": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "The receipt_id returned with a paid result (\"rcpt_\" + 64 hex characters)."
        }
      }
    }
    arguments 15 lines
  • realestate_municipalities unknown 2h ago

    Which municipality codes and names does MLIT's Real Estate Information Library list for this Japanese prefecture? Give a prefecture code (01-47) or name. Returns the 5-digit municipality codes with Japanese and English names as published by MLIT (XIT002): the join key for realestate_prices_by_municipality and other Japanese public data. Carries the required MLIT credit.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "prefecture"
      ],
      "properties": {
        "prefecture": {
          "type": "string",
          "maxLength": 20,
          "description": "Prefecture code 01-47 (e.g. 13) or name (Tokyo or 東京都)."
        }
      }
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f3aee3498a83c197.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f3aee3498a83c197/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f3aee3498a83c197/badge.svg)](https://brick.blue/agent/f3aee3498a83c197?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.