_ registry / mcp streamable-http · checked 12h ago

japan-foundry-mcp

https://japan-places.local-connect-design.trade

Registry code: 797a362b3fa8a28c

api record

Japan POI tools for AI agents: 2.94M facilities, station catchments, chains, grants and signals

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

endpoint
https://japan-places.local-connect-design.trade/mcp
protocol
streamable-http ·2025-03-26
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 japan-foundry-mcp live?
Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
Is japan-foundry-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does japan-foundry-mcp have?
16 tools: jp_quality, jp_catchment, jp_chains, jp_aliveness, jp_density, jp_energy_price, jp_land_price, jp_grant_deadline_alert, ….
Is japan-foundry-mcp 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
215ms

last good check

priced tools
0

of 16 tools

_ answered our checks, 90 days 2 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

_ what it can do 16 tools
1 open 15 never probed 1 of 16 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.

  • jp_gbizinfo_search open 12h ago

    gBizINFO法人登録データスナップショット（26,249法人）の検索

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "q": {
      "type": "string"
    },
    "limit": {
      "type": "string"
    },
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • jp_quality unknown never probed

    ジオコーディング品質の分布

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "min_score": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • jp_catchment unknown never probed

    駅周辺の人口・施設密度

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "string"
    }
  }
}
    arguments 9 lines
  • jp_chains unknown never probed

    チェーン店の出店密度

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "string"
    },
    "min_count": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • jp_aliveness unknown never probed

    街の活気スコア

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "string"
    },
    "min_score": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • jp_density unknown never probed

    都道府県×カテゴリのPOI密度

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "category": {
      "type": "string"
    },
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • jp_energy_price unknown never probed

    JEPX電力需給×気象からの価格シグナル

    mcp-tool

    {
  "type": "object",
  "required": [
    "area"
  ],
  "properties": {
    "area": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • jp_land_price unknown never probed

    都道府県別平均地価（国土数値情報 地価公示）

    mcp-tool

    {
  "type": "object",
  "required": [
    "prefecture_code"
  ],
  "properties": {
    "prefecture_code": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • jp_grant_deadline_alert unknown never probed

    補助金締切・要件アラート

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "string"
    },
    "status": {
      "type": "string"
    },
    "industry": {
      "type": "string"
    },
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 18 lines
  • jp_crime_statistics unknown never probed

    総務省統計局 都道府県データ基礎データによる都道府県別の刑法犯認知件数シグナル

    mcp-tool

    {
  "type": "object",
  "required": [
    "prefecture"
  ],
  "properties": {
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • jp_subsidy_award_rate unknown never probed

    補助金採択率推定インデックス

    mcp-tool

    {
  "type": "object",
  "required": [
    "industry",
    "prefecture"
  ],
  "properties": {
    "industry": {
      "type": "string"
    },
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • jp_tourism_signal unknown never probed

    総務省統計局 都道府県データ基礎データによる都道府県別の外国人延べ宿泊者数シグナル

    mcp-tool

    {
  "type": "object",
  "required": [
    "prefecture"
  ],
  "properties": {
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • jp_facility_signal unknown never probed

    OpenPOI公共施設カテゴリPOI集計による都道府県別の公共施設数シグナル

    mcp-tool

    {
  "type": "object",
  "required": [
    "prefecture"
  ],
  "properties": {
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • jp_municipality unknown never probed

    市区町村別センサス（人口・法人数・POI件数）

    mcp-tool

    {
  "type": "object",
  "required": [
    "prefecture"
  ],
  "properties": {
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • jp_jma_weather unknown never probed

    気象庁・気温・降水量・日照時間の都道府県別シグナル

    mcp-tool

    {
  "type": "object",
  "required": [
    "prefecture"
  ],
  "properties": {
    "prefecture": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • jp_boj_statistics unknown never probed

    日銀・金融統計・物価指数の時系列シグナル

    mcp-tool

    {
  "type": "object",
  "required": [
    "series"
  ],
  "properties": {
    "series": {
      "type": "string"
    }
  }
}
    arguments 11 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 797a362b3fa8a28c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/797a362b3fa8a28c/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/797a362b3fa8a28c/badge.svg)](https://brick.blue/agent/797a362b3fa8a28c?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
100%

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.