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

calendar

https://panembrivdienu.lv

Registry code: 5fd8c2c7a7fab8a9

api record

Latvian public holidays, days off and annual leave for 2026 and 2027, computed from Latvian law (not guessed). Use latvia_holidays for the holiday dates, latvia_calendar_statistics for counts of working days and days off, latvia_plan_time_off to find where a few leave days bridge weekends and holidays into long breaks, and latvia_leave_entitlement to estimate annual leave. The planner counts leave in working days; the entitlement is in calendar days excluding holidays, a different unit. apply_transfers=true applies the 2026 workday transfers, which bind only specified state-funded…

endpoint
https://panembrivdienu.lv/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 calendar live?
Yes — it answered the hub's last check (checked 2h ago). It answered 98% of checks over the last 30 days.
Is calendar free to use?
Yes — the hub reached it with no key and no payment.
What tools does calendar have?
4 tools: latvia_plan_time_off, latvia_leave_entitlement, latvia_calendar_statistics, latvia_holidays.
Is calendar 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
97.7%

90 days 98.6%· all time 98.6%

latency
236ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 347 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • list latvian public holidays
  • count working days in latvia
  • plan leave to bridge holidays
  • estimate annual leave entitlement
takes → gives
data → data
tools
4 reads
_ 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

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 4 tools
4 never probed 0 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.

  • latvia_plan_time_off reads unknown 21h ago

    Suggest up to ten long breaks in 2026 or 2027, best first, where a few leave days bridge weekends and Latvian holidays. Use it to decide when to take leave; for the holiday dates alone use latvia_holidays, and for how much leave the user has use latvia_leave_entitlement. pto_days caps the working days of leave each break may use on its own; it is not a yearly budget to split. A break takes every working day between runs of days off and holds a holiday or other day off on a weekday, so a week that only joins two weekends is not listed. Leave is never planned before today in Latvia or before employment_start_date. extra_days_off adds days the employer gives, so breaks can build on them. Breaks rank by days off, then fewer leave days, then date; efficiency is days off per leave day. pto_hours is the working hours of leave, assuming a full-time 8-hour day; 7 hours on a pre-holiday day.

    mcp-tool

    {
      "type": "object",
      "required": [
        "year",
        "pto_days"
      ],
      "properties": {
        "year": {
          "type": "integer",
          "description": "year to plan leave in: 2026 or 2027"
        },
        "pto_days": {
          "type": "integer",
          "description": "most working days of leave one break may use, 1 to 100"
        },
        "extra_days_off": {
          "type": [
            "null",
            "array"
          ],
          "items": {
            "type": "string"
          },
          "description": "extra days off such as ones the employer gives, YYYY-MM-DD in 2026 or 2027, at most 100"
        },
        "apply_transfers": {
          "type": "boolean",
          "description": "apply the 2026 workday transfers (2026 only)"
        },
        "employment_start_date": {
          "type": "string",
          "description": "YYYY-MM-DD; no leave is planned before it (nor before today in Latvia)"
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
  • latvia_leave_entitlement reads unknown 5h ago

    Estimate annual paid leave under the Latvian Labour Law, in calendar days excluding public holidays. Use it to answer how much leave someone has in a year; to find when to take it use latvia_plan_time_off, which counts leave in working days, a different unit. Pass annual_base=28 (the legal minimum) unless the contract grants more, and fte_percentage=1 for full time; part-time work does not shorten leave. birth_date matters only for employees under 18, who get one calendar month. If employment_start_date is on or after 1 January of year, the result is an accrual estimate; the full leave may be requested after six months of work.

    mcp-tool

    {
      "type": "object",
      "required": [
        "employment_start_date",
        "year",
        "fte_percentage",
        "annual_base"
      ],
      "properties": {
        "year": {
          "type": "integer",
          "description": "year to estimate, 2020 to 2100"
        },
        "birth_date": {
          "type": "string",
          "description": "YYYY-MM-DD; employees under 18 get one calendar month"
        },
        "annual_base": {
          "type": "integer",
          "description": "annual leave in calendar days, 28 (the legal minimum) to 60"
        },
        "fte_percentage": {
          "type": "number",
          "description": "working time as a fraction of full time, 0.1 to 1.0 (part-time work does not shorten leave)"
        },
        "employment_start_date": {
          "type": "string",
          "description": "YYYY-MM-DD"
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • latvia_calendar_statistics reads unknown 21h ago

    Count working days, weekend days, holidays, total days off and working hours in 2026 or 2027 for a Monday-to-Friday week. Use it for yearly totals, such as how many working days or hours a year has; months gives each month's working days, working hours (a day before a holiday is one hour shorter), weekday_holidays (holidays that fall on a weekday) and pre-holiday dates; for the holiday dates use latvia_holidays, and for leave suggestions use latvia_plan_time_off. year must be 2026 or 2027. apply_transfers=true (2026 only) moves working days and days off as the 2026 transfers do, which bind only specified state-funded institutions; the moved counts are then non-zero.

    mcp-tool

    {
      "type": "object",
      "required": [
        "year"
      ],
      "properties": {
        "year": {
          "type": "integer",
          "description": "calendar year: 2026 or 2027"
        },
        "apply_transfers": {
          "type": "boolean",
          "description": "apply the 2026 workday transfers (2026 only; they bind only specified state-funded institutions)"
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • latvia_holidays reads unknown 21h ago

    List Latvia's public holidays in 2026 or 2027, sorted by date, each with its Latvian and English name. Use it when you need the dates themselves; for totals use latvia_calendar_statistics, and to turn holidays into long breaks use latvia_plan_time_off. year must be 2026 or 2027; any other year is an error. apply_transfers=true (2026 only) adds the moved days off, flagged is_moved_day. Set it only for staff of the state-funded institutions the transfers bind.

    mcp-tool

    {
      "type": "object",
      "required": [
        "year"
      ],
      "properties": {
        "year": {
          "type": "integer",
          "description": "calendar year: 2026 or 2027"
        },
        "apply_transfers": {
          "type": "boolean",
          "description": "apply the 2026 workday transfers (2026 only; they bind only specified state-funded institutions)"
        }
      },
      "additionalProperties": false
    }
    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 5fd8c2c7a7fab8a9.

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