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

japan-business-day

https://japan-business-day-api.matchan962.workers.dev

Registry code: 152481ade4fd689c

api record

Is a given date a business day in Japan? Returns weekday/holiday status, official holiday name (JA/EN) and next/previous business day. Source: Cabinet Office of Japan.

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

endpoint
https://japan-business-day-api.matchan962.workers.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is japan-business-day live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is japan-business-day free to use?
Yes — the hub reached it with no key and no payment.
What tools does japan-business-day have?
11 tools: jpx_trading_day, jpx_record_date, japanese_koyomi, is_business_day_free, jpx_sq_date, list_holidays, find_lucky_days_japan, is_business_day, ….
Is japan-business-day 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
99.2%

90 days 99.2%· all time 99.2%

latency
1,380ms

last good check

priced tools
4

of 11 tools

_ answered our checks, 90 days 381 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business calendar & scheduling
used for
  • check if a date is a business day in japan
  • add japanese business days to a date
  • list japanese holidays
  • find tokyo stock exchange trading days
  • calculate japanese payment due dates
takes → gives
data → data
tools
11 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 10 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
9

distinct

settlements
24

last 2026-11-09

received on chain
0.175 USDC

no flags

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 11 tools
4 paid 7 never probed 4 of 11 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.

  • is_business_day reads 0.005 USDC paid never probed

    Check whether a date is a business day in Japan (official Cabinet Office holiday data). Returns holiday name (JA/EN) and next/previous business day. Price: $0.005 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD. Supported range 1955-01-01..2027-12-31"
    },
    "calendar": {
      "enum": [
        "national",
        "bank"
      ],
      "type": "string",
      "description": "national (default): weekends + national holidays. bank: also Dec 31 - Jan 3 bank holidays"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • add_business_days reads 0.01 USDC paid never probed

    Add or subtract N Japanese business days from a date (settlement T+N, delivery ETA). Price: $0.01 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "days"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD. Supported range 1955-01-01..2027-12-31"
    },
    "days": {
      "type": "integer",
      "maximum": 366,
      "minimum": -366
    },
    "calendar": {
      "enum": [
        "national",
        "bank"
      ],
      "type": "string",
      "description": "national (default): weekends + national holidays. bank: also Dec 31 - Jan 3 bank holidays"
    }
  },
  "additionalProperties": false
}
    arguments 28 lines
  • payment_due_date reads 0.01 USDC paid never probed

    Japanese payment terms (shimebi/shiharaibi) calculator, e.g. month-end close paid end of next month; shifts to the previous/next business day on weekends/holidays. Price: $0.01 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "closing",
    "payDay"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Transaction or invoice date (YYYY-MM-DD)"
    },
    "adjust": {
      "enum": [
        "previous",
        "next",
        "none"
      ],
      "type": "string",
      "description": "Shift when not a business day; default previous"
    },
    "payDay": {
      "anyOf": [
        {
          "$ref": "#/properties/closing/anyOf/0"
        },
        {
          "$ref": "#/properties/closing/anyOf/1"
        }
      ],
      "description": "Payment day of month (1-31) or 'end'"
    },
    "closing": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 31,
          "minimum": 1
        },
        {
          "type": "string",
          "const": "end"
        }
      ],
      "description": "Closing day of month (1-31) or 'end'"
    },
    "calendar": {
      "enum": [
        "national",
        "bank"
      ],
      "type": "string",
      "description": "national (default): weekends + national holidays. bank: also Dec 31 - Jan 3 bank holidays"
    },
    "monthOffset": {
      "type": "integer",
      "maximum": 3,
      "minimum": 0,
      "description": "Months after closing; default 1 (next month)"
    }
  },
  "additionalProperties": false
}
    arguments 64 lines
  • bank_value_date reads 0.01 USDC paid never probed

    When will a Japanese bank transfer be credited? Returns the value date under standard processing (same day before the cutoff, default 15:00 JST, on a bank business day; otherwise next bank business day). Price: $0.01 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "cutoff": {
      "type": "string",
      "description": "Bank cutoff HH:MM JST, default 15:00"
    },
    "datetime": {
      "type": "string",
      "description": "Submission time ISO 8601 (default now; no offset = JST)"
    },
    "extraDays": {
      "type": "integer",
      "maximum": 30,
      "minimum": 0,
      "description": "Additional bank business days"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • jpx_trading_day reads unknown never probed

    Is the Tokyo Stock Exchange (JPX) open on a date? Next/previous trading day, first/last trading day of the year. Price: $0.005 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD. Supported range 1955-01-01..2027-12-31"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • jpx_record_date reads unknown never probed

    Japanese stocks: last cum-rights trading day and ex-rights date for a dividend/benefit record date (T+2 settlement, holiday-aware). Price: $0.01 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "recordDate"
  ],
  "properties": {
    "recordDate": {
      "type": "string",
      "description": "Record date (kenri kakutei-bi) YYYY-MM-DD"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • japanese_koyomi reads unknown never probed

    Japanese traditional calendar for a date: rokuyo (taian/butsumetsu lucky days), Reiwa era date, lunisolar date, 24 solar terms. Price: $0.005 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD (1955-2032)"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • is_business_day_free reads unknown never probed

    FREE: check whether a date between today and 90 days ahead (JST) is a business day in Japan. Official Cabinet Office holiday data, supports bank calendar (Dec 31 - Jan 3). For other dates, business-day arithmetic or holiday lists use the paid tools.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "Date in YYYY-MM-DD. Supported range 1955-01-01..2027-12-31"
    },
    "calendar": {
      "enum": [
        "national",
        "bank"
      ],
      "type": "string",
      "description": "national (default): weekends + national holidays. bank: also Dec 31 - Jan 3 bank holidays"
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • jpx_sq_date reads unknown never probed

    Nikkei 225 futures/options SQ day and last trading day for a contract month (2nd Friday, moved earlier on holidays). Price: $0.01 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "month"
  ],
  "properties": {
    "month": {
      "type": "string",
      "description": "Contract month YYYY-MM"
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • list_holidays reads unknown 24h ago

    List Japanese national holidays for a year with JA/EN names. Price: $0.01 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "year"
  ],
  "properties": {
    "year": {
      "type": "integer"
    },
    "calendar": {
      "enum": [
        "national",
        "bank"
      ],
      "type": "string",
      "description": "national (default): weekends + national holidays. bank: also Dec 31 - Jan 3 bank holidays"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • find_lucky_days_japan reads unknown 24h ago

    Find auspicious Japanese dates: days in a range matching rokuyo (e.g. taian) and optional weekdays (e.g. sat,sun) for weddings, moving, contracts. Price: $0.01 USDC via x402.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "End date YYYY-MM-DD (max 366 days)"
    },
    "from": {
      "type": "string",
      "description": "Start date YYYY-MM-DD"
    },
    "rokuyo": {
      "type": "string",
      "description": "Comma-separated: taian,shakko,sensho,tomobiki,sakimake,butsumetsu (default taian)"
    },
    "weekdays": {
      "type": "string",
      "description": "Comma-separated weekdays, e.g. sat,sun"
    }
  },
  "additionalProperties": false
}
    arguments 27 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 152481ade4fd689c.

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