Connect with MCP
Endpoint
Section titled “Endpoint”https://biz.ossalt.jp/mcpThe server speaks Streamable HTTP in its simplest form: you POST one JSON-RPC 2.0 message and receive one JSON answer.
| Property | Value |
|---|---|
| Authentication | None |
| Protocol versions | 2025-06-18, 2025-03-26 and 2024-11-05 (negotiated in initialize) |
| Capabilities | tools only (no resources, prompts, logging, sampling or elicitation) |
| Sessions | Stateless: the server does not issue a session ID |
| Streaming | Not used. GET /mcp returns 405; there is no SSE stream |
| Batching | Not supported: a JSON array is rejected with -32600 |
| Browser use | CORS allows any origin; allowed request headers are content-type, accept, mcp-protocol-version |
Connect a client
Section titled “Connect a client”Add the URL as a remote (Streamable HTTP) MCP server. Menu names change between versions, so check your client’s documentation if a label differs.
| Client | How |
|---|---|
| Claude (custom connector) | In the connector settings, add a custom connector and enter the URL above. |
| Claude Code | claude mcp add --transport http jp-biz-tools https://biz.ossalt.jp/mcp |
| Cursor | In mcp.json: {"mcpServers": {"jp-biz-tools": {"url": "https://biz.ossalt.jp/mcp"}}} |
| VS Code | In .vscode/mcp.json: {"servers": {"jp-biz-tools": {"type": "http", "url": "https://biz.ossalt.jp/mcp"}}} |
| MCP Inspector | npx @modelcontextprotocol/inspector --cli https://biz.ossalt.jp/mcp --transport http --method tools/list |
| stdio-only clients | Bridge with npx mcp-remote https://biz.ossalt.jp/mcp |
What we have verified. The endpoint was checked with the MCP Inspector CLI and the MCP conformance suite (see Trust & transparency). The per-client steps above follow each client’s documented configuration; we have not tested every client ourselves.
The 13 tools
Section titled “The 13 tools”See the tool reference for every input. In short:
| Category | Tools |
|---|---|
| Calendar | list_holidays, check_business_day, add_business_days, count_business_days, adjust_to_business_day, last_business_day_of_month |
| Japanese eras | to_japanese_era, from_japanese_era |
| Postal codes & addresses | lookup_postal_code, search_postal_code, normalize_address |
| Corporate records | lookup_corporate_number, search_corporation_by_name |
All tools declare readOnlyHint: true and idempotentHint: true, and none declares an outputSchema. Their inputs are JSON Schemas that you get from tools/list. Unknown input fields are rejected.
Input and output
Section titled “Input and output”A call:
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": { "name": "to_japanese_era", "arguments": { "date": "2019-05-01" } }}A successful result carries the answer shape twice: as JSON text in content[0].text and as an object in structuredContent.
{ "jsonrpc": "2.0", "id": 1, "result": { "content": [{ "type": "text", "text": "{\"result\":{…},\"source\":{…},\"as_of\":\"…\",\"notes\":[],\"flags\":[]}" }], "structuredContent": { "result": {}, "source": {}, "as_of": "YYYY-MM-DD", "notes": [], "flags": [] } }}Errors
Section titled “Errors”| Situation | What you get |
|---|---|
| Invalid input (bad date, out-of-range number, unknown field) | A normal result with isError: true. The text starts with Invalid input. The message is Japanese text, with the reason. |
| The server or its data is unavailable | A normal result with isError: true. The text starts with Server error. Retry later. |
| Unknown tool | JSON-RPC error -32602 |
| Unknown method | JSON-RPC error -32601 |
| Malformed JSON | JSON-RPC error -32700 |
| Batch array, or a request that is not a single JSON-RPC message | HTTP 400, JSON-RPC error -32600 |
| Too many requests | HTTP 429, JSON-RPC error -32000 with data.type: "rate_limited" and data.retry_after (seconds) |
Treat isError as the signal for input mistakes and unavailable data. A tool that finds nothing returns a normal answer with the not_found flag.
Limits
Section titled “Limits”- Requests are limited per client IP address to about 60 per minute (counted per Cloudflare location, so approximate). The MCP endpoint has an additional burst limit at the network edge. Please do not run bulk jobs through the public endpoint.
- The request body is limited to 64 KB, and each text field to 200 characters.
count_business_dayscovers up to 3,660 days;add_business_daysaccepts ±2,000 days; years run from 1980 to 2099.- The service has no uptime guarantee or SLA.
See Trust & transparency for data sources, freshness and known limitations.
Operated by Momonga