{
  "name": "rubik-jp",
  "title": "Rubik JP listings",
  "description": "Public, read-only MCP server exposing product, job and real-estate listings from Japanese sources that have opted in to this distribution channel. Japan only; all monetary values are JPY. Data is a periodic snapshot with per-source freshness, not a live feed.",
  "version": "1.0.0",
  "websiteUrl": "https://mcp.rubik.co.jp/",
  "documentationUrl": "https://mcp.rubik.co.jp/",
  "remotes": [
    {
      "type": "streamable-http",
      "url": "https://mcp.rubik.co.jp/mcp",
      "protocolVersion": "2026-07-28",
      "authentication": "none"
    }
  ],
  "capabilities": {
    "tools": {},
    "resources": false,
    "prompts": false
  },
  "tools": [
    { "name": "search_products", "description": "Search product listings from opted-in Japanese merchants." },
    { "name": "get_product", "description": "Fetch one product by source_id and id, with the full description." },
    { "name": "search_jobs", "description": "Search job postings. Salary is a range plus a period, with a dedicated undisclosed flag." },
    { "name": "get_job", "description": "Fetch one job posting by source_id and id." },
    { "name": "search_properties", "description": "Search real-estate listings by station, walk time, layout, rent or size." },
    { "name": "get_property", "description": "Fetch one property with every station it lists." },
    { "name": "list_sources", "description": "List the opted-in sources and the attribution text their listings must carry." },
    { "name": "data_version", "description": "Report data freshness per source rather than as one global figure." },
    { "name": "list_values", "description": "List the values a given filter will actually match, with counts." }
  ],
  "limits": {
    "maxRowsPerResponse": 25,
    "maxBytesPerResponse": 61440,
    "requestsPerMinutePerIp": 60,
    "maxRequestBytes": 262144
  },
  "coverage": {
    "country": "JP",
    "locale": "ja",
    "currency": "JPY",
    "verticals": ["products", "jobs", "real_estate"]
  },
  "readOnly": true,
  "_note": "SPECULATIVE PATH. As of the 2026-07-28 specification, .well-known is standardised only for OAuth authorization discovery (SEP-2351). Capability discovery itself is neither speculative nor optional: the server/discover RPC is mandatory for every 2026-07-28 server, and this server answers it through the mcp gem rather than through this file. What remains unmerged is serving that description at a .well-known PATH -- /.well-known/mcp/server-card.json (SEP-1649) and /.well-known/mcp (SEP-1960) are on the published roadmap only, and the field shapes below are a best reading of those proposals rather than a validated schema. Served because it is a static file and costs nothing; do not treat its presence as spec compliance. The authoritative machine-readable description of this server is tools/list over the endpoint itself."
}
