jp_court_search
Pack: jp-courts · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/jp_court_search for the schema, then POST the same URL with its arguments for the data.
Search the Courts of Japan (裁判所) judgments database: Supreme Court, high court, lower court, administrative, labour and Intellectual Property High Court decisions. Japanese full-text query; each hit gives the case number (e.g. 平成30(受)1961), case name, decision date, court, the court’s detail lines and the link to the full text. Words separated by spaces match decisions containing ANY of them; use must_include to require further words; a search matching over 2,000 decisions is refused by the court (empty_reason too_many_results) so use specific terms. court narrows to one part of the database (supreme, high, lower, administrative, labor, ip; default all). Dates are YYYY-MM-DD, Showa era onward. Only some decisions are published, so no hit does not mean no such case. Example: query=“ストックオプション”, court=“supreme”.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
query | string | yes | Japanese words, separated by spaces (any word matches). |
must_include | string | no | Optional extra words the decision must also contain. |
court | string | no | Part of the database: all (default), supreme, high, lower, administrative, labor, ip. |
date_from | string | no | Earliest decision date, YYYY-MM-DD (1926-12-25 or later). |
date_to | string | no | Latest decision date, YYYY-MM-DD. |
limit | number | no | Records returned from the page (1-30, default 10). |
offset | number | no | Result offset for the next page: use next_offset from the previous response (pages of 30). |
Example call
Arguments
{
"query": "ストックオプション",
"court": "supreme"
}
curl
curl -X POST https://gateway.pipeworx.io/jp-courts/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"jp_court_search","arguments":{"query":"ストックオプション","court":"supreme"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('jp_court_search', {
"query": "ストックオプション",
"court": "supreme"
});
Response shape
| Field | Type | Description |
|---|---|---|
query | object | |
found | boolean | |
total | number | null | |
returned | number | |
offset | number | |
next_offset | number | null | |
records | array | |
sort | string | |
source | string | |
caveat | string | |
empty_reason | string | |
note | string |
Full JSON Schema
{
"type": "object",
"properties": {
"query": {
"type": "object",
"additionalProperties": true
},
"found": {
"type": "boolean"
},
"total": {
"type": [
"number",
"null"
]
},
"returned": {
"type": "number"
},
"offset": {
"type": "number"
},
"next_offset": {
"type": [
"number",
"null"
]
},
"records": {
"type": "array",
"items": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"get_id": {
"type": "string"
},
"kind": {
"type": "number"
},
"category": {
"type": [
"string",
"null"
]
},
"case_number": {
"type": [
"string",
"null"
]
},
"case_name": {
"type": [
"string",
"null"
]
},
"decision_date": {
"type": [
"string",
"null"
]
},
"decision_date_ja": {
"type": [
"string",
"null"
]
},
"court": {
"type": [
"string",
"null"
]
},
"detail": {
"type": "array",
"items": {
"type": "array",
"items": {
"type": "string"
}
}
},
"detail_url": {
"type": "string"
},
"full_text_pdf_url": {
"type": [
"string",
"null"
]
}
},
"additionalProperties": true
}
},
"sort": {
"type": "string"
},
"source": {
"type": "string"
},
"caveat": {
"type": "string"
},
"empty_reason": {
"type": "string"
},
"note": {
"type": "string"
}
},
"additionalProperties": true
}
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the jp-courts pack
{
"mcpServers": {
"jp-courts": {
"url": "https://gateway.pipeworx.io/jp-courts/mcp"
}
}
}
See Getting Started for client-specific install steps.