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

bankday

https://bankday.jacklehoff4866.workers.dev

Registry code: 5cc8e69e3050bf2b

api record

Business-day, holiday and settlement-date calculations for payment rails (ACH/Fedwire, TARGET2, Bacs), 28 stock exchanges and 240+ countries.

endpoint
https://bankday.jacklehoff4866.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
0 · newcomer
_ is it live, free and safe measured by this hub
Is bankday live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is bankday free to use?
No — it asks for a key or a login before it will serve.
What tools does bankday have?
8 tools: is_business_day, today_status, ach_settlement_date, search_calendars, count_business_days, list_holidays, add_business_days, fx_spot_date.
Is bankday 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
150ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 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 8 tools
8 auth-required 8 of 8 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 auth-required never probed

    Check whether a date is a business day on a calendar; returns closures and the next/previous business day.

    mcp-tool

    {
      "type": "object",
      "required": [
        "calendar",
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date as YYYY-MM-DD"
        },
        "calendar": {
          "type": "string",
          "description": "Calendar id, or several comma-separated for a joint calendar. E.g. us-fed (US ACH/Fedwire), xnys (NYSE), eu-target2, uk-bacs, or a country code like de, jp, br."
        }
      }
    }
    arguments 17 lines
  • today_status auth-required never probed

    Is today a business day on this calendar (in the calendar's local time zone)? Includes upcoming holidays.

    mcp-tool

    {
      "type": "object",
      "required": [
        "calendar"
      ],
      "properties": {
        "calendar": {
          "type": "string",
          "description": "Calendar id, or several comma-separated for a joint calendar. E.g. us-fed (US ACH/Fedwire), xnys (NYSE), eu-target2, uk-bacs, or a country code like de, jp, br."
        }
      }
    }
    arguments 12 lines
  • ach_settlement_date auth-required never probed

    Estimate when a US ACH payment settles given submission time and standard vs same-day.

    mcp-tool

    {
      "type": "object",
      "required": [
        "submitted_at"
      ],
      "properties": {
        "type": {
          "enum": [
            "standard",
            "same_day"
          ],
          "type": "string"
        },
        "amount": {
          "type": "number"
        },
        "submitted_at": {
          "type": "string",
          "description": "ISO 8601 timestamp"
        }
      }
    }
    arguments 22 lines
  • search_calendars auth-required 1h ago

    Find calendar ids by name, country or type (rail, exchange, country).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string"
        },
        "type": {
          "enum": [
            "rail",
            "exchange",
            "country"
          ],
          "type": "string"
        }
      }
    }
    arguments 16 lines
  • count_business_days auth-required 1h ago

    Count business days between two dates (start exclusive, end inclusive).

    mcp-tool

    {
      "type": "object",
      "required": [
        "calendar",
        "start",
        "end"
      ],
      "properties": {
        "end": {
          "type": "string",
          "description": "Date as YYYY-MM-DD"
        },
        "start": {
          "type": "string",
          "description": "Date as YYYY-MM-DD"
        },
        "calendar": {
          "type": "string",
          "description": "Calendar id, or several comma-separated for a joint calendar. E.g. us-fed (US ACH/Fedwire), xnys (NYSE), eu-target2, uk-bacs, or a country code like de, jp, br."
        }
      }
    }
    arguments 22 lines
  • list_holidays auth-required 1h ago

    List holidays/closures for a calendar in a year.

    mcp-tool

    {
      "type": "object",
      "required": [
        "calendar"
      ],
      "properties": {
        "year": {
          "type": "integer"
        },
        "calendar": {
          "type": "string",
          "description": "Calendar id, or several comma-separated for a joint calendar. E.g. us-fed (US ACH/Fedwire), xnys (NYSE), eu-target2, uk-bacs, or a country code like de, jp, br."
        }
      }
    }
    arguments 15 lines
  • add_business_days auth-required never probed

    Add (or subtract, with a negative number) business days to a date.

    mcp-tool

    {
      "type": "object",
      "required": [
        "calendar",
        "date",
        "days"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date as YYYY-MM-DD"
        },
        "days": {
          "type": "integer"
        },
        "calendar": {
          "type": "string",
          "description": "Calendar id, or several comma-separated for a joint calendar. E.g. us-fed (US ACH/Fedwire), xnys (NYSE), eu-target2, uk-bacs, or a country code like de, jp, br."
        }
      }
    }
    arguments 21 lines
  • fx_spot_date auth-required never probed

    FX spot value date for a currency pair and trade date (T+2 / T+1 conventions, joint holiday calendars).

    mcp-tool

    {
      "type": "object",
      "required": [
        "pair",
        "trade_date"
      ],
      "properties": {
        "pair": {
          "type": "string",
          "description": "e.g. EURUSD"
        },
        "trade_date": {
          "type": "string",
          "description": "Date as YYYY-MM-DD"
        }
      }
    }
    arguments 17 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 5cc8e69e3050bf2b.

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