A
licenseA
qualityC
maintenanceProvides real, official public holiday data for ~100 countries with tools to list holidays for a year and check if a specific date is a holiday. Free, no API key required, powered by Nager.Date.
2
MIT
lookup-holiday
Server Details
Real public holiday lookup for 206 countries via a rule-based calendar engine. Paid via x402.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- encodi/lookup-holiday
- GitHub Stars
- 0
- Server Listing
- lookup-holiday
Tool Definition Quality
A4.3/5.0
Tool DescriptionsA
Average 4.2/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusion between different tools. The tool's name and description clearly indicate its purpose.
Naming Consistency5/5
The single tool follows a clear verb_noun pattern (lookup_holiday), which is consistent with the server name. There is no mixture of conventions to cause inconsistency.
Tool Count3/5
The server has only one tool, which is on the low end of the typical range. While the tool is well-scoped for a single-purpose holiday lookup, the minimal count makes the server feel thin, though not absurdly incomplete.
Completeness5/5
The tool covers the full scope of holiday lookups, supporting country, state/region, year, and different holiday types. There are no obvious missing operations within its defined domain.
Available Tools
1 toollookup_holidayLook up public holidaysAInspect
Looks up real public/bank/school holidays for a country (and optionally a state/region) and year from a real rule-based calendar engine covering 206 countries — moveable holidays like Easter are computed astronomically, not guessed. Costs $0.01 USDC (Base) per call.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Calendar year to look up. Defaults to the current UTC year. Between 1900 and 2200. | |
| state | No | Optional subdivision code within the country (e.g. "CA" for California in "US"). | |
| types | No | Optional filter: only return holidays of these types (e.g. ["public"]). Default: all types. | |
| region | No | Optional sub-region code within the state. Requires `state` to also be set. | |
| country | Yes | ISO 3166-1 alpha-2 country code (e.g. "US", "FR", "JP"). | |
| language | No | Optional ISO 639-1 language code for holiday names (e.g. "es"). Falls back to the country default. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| year | Yes | |
| error | Yes | Error message if valid is false; null otherwise. |
| state | Yes | |
| valid | Yes | false if the input (country/state/region/year/type) was invalid. |
| region | Yes | |
| country | Yes | |
| holidays | Yes | Holidays for the requested year, sorted by date. |
Tool Definition Quality
A4.2/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses key behavioral traits: uses a real rule-based engine, covers 206 countries, computes moveable holidays astronomically (not guessed), and costs $0.01 USDC per call. These go beyond the basic schema and inform the agent about accuracy, breadth, and cost. It does not mention error handling or rate limits, but that is not essential for a read-only lookup tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three sentences long, front-loaded with the primary action, and every sentence contributes value: the first defines the purpose and scope, the second emphasizes accuracy, and the third discloses the cost. There is no redundancy or filler. It is appropriately concise for the tool's complexity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the output schema exists, the description does not need to explain return values. The description covers the core purpose, geographic coverage, accuracy, and cost, which are the most relevant contextual factors for agent decision-making. It does not mention caveats like invalid inputs or region/state dependencies, but the schema already details parameter constraints. Overall, it is complete for a simple lookup tool with robust structured metadata.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers all 6 parameters with 100% description coverage, so the baseline is 3. The description adds minimal semantic value by summarizing that the tool works for a 'country (and optionally a state/region) and year' and mentions 'public/bank/school holidays' which implicitly maps to the `types` parameter. It does not provide any additional meaning beyond what the schema already offers, but does not contradict it either.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool looks up 'real public/bank/school holidays' for a country (and optionally state/region) and year, with a specific verb 'looks up' and resource 'rule-based calendar engine covering 206 countries'. It distinguishes itself from guessing or approximate data by emphasizing accuracy and astronomical computation. Although there are no sibling tools to differentiate from, the purpose is unambiguous and specific.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context for when to use the tool: when you need genuine holiday data for a country/state/year, backed by a reliable engine. It also discloses the $0.01 cost, implying an economic consideration for use. It does not explicitly mention alternatives or exclusions, but no sibling tools exist, and the straightforward lookup context suffices. The 'not guessed' clause reinforces reliability, making the intended use clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseNot gradedqualityCmaintenancePublic holiday data for 30+ countries. Check holidays, working days, and full calendars via AI assistants like Claude and Cursor.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying public holiday data by country and year, checking if today is a holiday, and listing upcoming holidays through the MCP protocol.5MIT
- AlicenseNot gradedqualityBmaintenanceProvides public holidays, long weekends, and country data for 202 countries via the Nager.Date API, with client-side filtering and timezone-aware checks.BSD Zero Clause
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.