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

kalender

https://kalender.halowerk.com

Registry code: 981cd80c0f1df626

api record

Für Zahlungsziele, Fristen und Liefertermine. Die Antwort nennt das Ergebnisdatum, die Zahl der Kalendertage und jeden übersprungenen Tag mit Grund.

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

endpoint
https://kalender.halowerk.com/mcp
door code
fdfc949878958489
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 kalender live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is kalender free to use?
Not measured yet.
What tools does kalender have?
4 tools: werktage_rechnen, feiertage, werktage, zeitzone.
Is kalender 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.8%

90 days 99.4%· all time 99.6%

latency
93ms

last good check

priced tools
3

of 4 tools

_ answered our checks, 90 days 1190 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
  • list public holidays in germany austria or switzerland
  • count working days between dates
  • add working days to a date
  • get time zone for a location
takes → gives
data → data
tools
4 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 also stands behind 121 other origins: the chain figures are the gateway's, not this listing's alone. 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
46

distinct

settlements
9,342

last 2026-11-10

received on chain
37.4096 USDC

shared-payto

_ what it can do 4 tools
3 paid 1 never probed 3 of 4 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.

  • feiertage reads 0.001 USDC paid never probed

    Public holidays for one year in Germany, Austria or Switzerland, resolved down to the federal state or canton. Every entry carries its legal standing, the rule it was derived from and whether it actually stops work. Paid per call in USDC over x402.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "jahr": {
      "type": "integer",
      "maximum": 2200,
      "minimum": 1970,
      "description": "Calendar year. Defaults to the current one."
    },
    "land": {
      "enum": [
        "DE",
        "AT",
        "CH"
      ],
      "type": "string",
      "default": "DE",
      "description": "Country code."
    },
    "region": {
      "type": "string",
      "description": "State code for DE (BW, BY, BE, BB, HB, HH, HE, MV, NI, NW, RP, SL, SN, ST, SH, TH) and AT (B, K, N, O, S, ST, T, V, W), canton code for CH (AG, AI, AR, BE, BL, BS, FR, GE, GL, GR, JU, LU, NE, NW, OW, SG, SH, SO, SZ, TG, TI, UR, VD, VS, ZG, ZH). \"DE-BY\" works as well. Germany also knows the municipal code BY-AU for the city of Augsburg. Without a region only nationwide holidays are returned."
    }
  }
}
    arguments 25 lines
  • werktage reads 0.001 USDC paid never probed

    Count working days between two dates for a given state or canton. Returns the count, the list of working days and a reason for every skipped day.

    mcp-tool

    {
  "type": "object",
  "required": [
    "von",
    "bis"
  ],
  "properties": {
    "bis": {
      "type": "string",
      "format": "date",
      "description": "Last day of the range, inclusive."
    },
    "von": {
      "type": "string",
      "format": "date",
      "description": "First day of the range, inclusive, format YYYY-MM-DD."
    },
    "land": {
      "enum": [
        "DE",
        "AT",
        "CH"
      ],
      "type": "string",
      "default": "DE",
      "description": "Country code."
    },
    "region": {
      "type": "string",
      "description": "State code for DE (BW, BY, BE, BB, HB, HH, HE, MV, NI, NW, RP, SL, SN, ST, SH, TH) and AT (B, K, N, O, S, ST, T, V, W), canton code for CH (AG, AI, AR, BE, BL, BS, FR, GE, GL, GR, JU, LU, NE, NW, OW, SG, SH, SO, SZ, TG, TI, UR, VD, VS, ZG, ZH). \"DE-BY\" works as well. Germany also knows the municipal code BY-AU for the city of Augsburg. Without a region only nationwide holidays are returned."
    },
    "zusatzfrei": {
      "type": "array",
      "items": {
        "type": [
          "string",
          "object"
        ]
      },
      "maxItems": 100,
      "description": "Own days off on top of the statutory ones, for example company holidays. Either \"2026-05-15\" or {\"datum\":\"2026-05-15\",\"grund\":\"Betriebsferien\"}."
    },
    "samstag_ist_werktag": {
      "type": "boolean",
      "default": false,
      "description": "Count Saturdays as working days."
    },
    "sonntag_ist_werktag": {
      "type": "boolean",
      "default": false
    }
  }
}
    arguments 53 lines
  • zeitzone reads 0.001 USDC paid never probed

    Time zone for a coordinate or an IANA name: current UTC offset, local time, whether DST is active and the next transition to the minute.

    mcp-tool

    {
  "type": "object",
  "anyOf": [
    {
      "title": "IANA time zone name",
      "required": [
        "zone"
      ]
    },
    {
      "title": "Geographic coordinates",
      "required": [
        "lat",
        "lon"
      ]
    }
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude, resolved to a zone offline."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180
    },
    "zone": {
      "type": "string",
      "minLength": 1,
      "description": "IANA time zone name, for example Europe/Berlin. Either this or lat and lon."
    },
    "zeitpunkt": {
      "type": "string",
      "format": "date-time",
      "description": "Point in time to evaluate. Defaults to now."
    }
  }
}
    arguments 41 lines
  • werktage_rechnen reads unknown never probed

    Add or subtract working days from a start date. Built for payment terms, notice periods and delivery dates.

    mcp-tool

    {
  "type": "object",
  "required": [
    "start",
    "werktage"
  ],
  "properties": {
    "land": {
      "enum": [
        "DE",
        "AT",
        "CH"
      ],
      "type": "string",
      "default": "DE",
      "description": "Country code."
    },
    "start": {
      "type": "string",
      "format": "date",
      "description": "Start date, format YYYY-MM-DD. It is never counted itself."
    },
    "region": {
      "type": "string",
      "description": "State code for DE (BW, BY, BE, BB, HB, HH, HE, MV, NI, NW, RP, SL, SN, ST, SH, TH) and AT (B, K, N, O, S, ST, T, V, W), canton code for CH (AG, AI, AR, BE, BL, BS, FR, GE, GL, GR, JU, LU, NE, NW, OW, SG, SH, SO, SZ, TG, TI, UR, VD, VS, ZG, ZH). \"DE-BY\" works as well. Germany also knows the municipal code BY-AU for the city of Augsburg. Without a region only nationwide holidays are returned."
    },
    "werktage": {
      "type": "integer",
      "maximum": 2000,
      "minimum": -2000,
      "description": "Positive counts forward, negative backward, 0 returns the next working day on or after the start date."
    },
    "zusatzfrei": {
      "type": "array",
      "items": {
        "type": [
          "string",
          "object"
        ]
      },
      "maxItems": 100,
      "description": "Own days off on top of the statutory ones, for example company holidays. Either \"2026-05-15\" or {\"datum\":\"2026-05-15\",\"grund\":\"Betriebsferien\"}."
    },
    "samstag_ist_werktag": {
      "type": "boolean",
      "default": false,
      "description": "Count Saturdays as working days."
    },
    "sonntag_ist_werktag": {
      "type": "boolean",
      "default": false
    }
  }
}
    arguments 54 lines
_ try it over mcp 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 981cd80c0f1df626.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/981cd80c0f1df626/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/981cd80c0f1df626/badge.svg)](https://brick.blue/agent/981cd80c0f1df626?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 knowoff the mcp door
card completeness
80%

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.

_ also on halowerk.com 109 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

101 more sit on this domain. All of them.