io.github.naeem-jtr/jtr-holidays
REMOTE · API.JTRHOLIDAYS.COM · SCANNED SEP 20
Search tours, attraction tickets, and holiday packages across 24 countries.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.naeem-jtr/jtr-holidays MCP server?
io.github.naeem-jtr/jtr-holidays is a hosted endpoint at https://api.jtrholidays.com/mcp/v1, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.jtrholidays.com
claude mcp add --transport http naeem-jtr-jtr-holidays 'https://api.jtrholidays.com/mcp/v1'
{
"mcpServers": {
"naeem-jtr-jtr-holidays": {
"url": "https://api.jtrholidays.com/mcp/v1"
}
}
} {
"servers": {
"naeem-jtr-jtr-holidays": {
"type": "http",
"url": "https://api.jtrholidays.com/mcp/v1"
}
}
} [mcp_servers.naeem-jtr-jtr-holidays] url = "https://api.jtrholidays.com/mcp/v1"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"naeem-jtr-jtr-holidays": {
"type": "remote",
"url": "https://api.jtrholidays.com/mcp/v1",
"enabled": true
}
}
} openclaw mcp add naeem-jtr-jtr-holidays --url 'https://api.jtrholidays.com/mcp/v1' --transport streamable-http
mcp_servers:
naeem-jtr-jtr-holidays:
url: "https://api.jtrholidays.com/mcp/v1" {
"McpServers": {
"naeem-jtr-jtr-holidays": {
"Transport": "http",
"Url": "https://api.jtrholidays.com/mcp/v1"
}
}
} assistant mcp add naeem-jtr-jtr-holidays -t streamable-http -u 'https://api.jtrholidays.com/mcp/v1'
{
"mcpServers": {
"naeem-jtr-jtr-holidays": {
"type": "http",
"url": "https://api.jtrholidays.com/mcp/v1"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 5 Aug 26 0
- Authorization: unverified → partial ▲ security
- DNSSEC: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.33 ▲ functional
- 4 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.27 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- DNSSEC: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.jtrholidays.com/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jtrholidays.com | CN=WE1,O=Google Trust Services,C=US | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | bd5034f56982c9090e4a7e9108c18982 |
| SANs: jtrholidays.com, *.jtrholidays.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.jtrholidays.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jtrholidays.com. | present | 2371 | 13 | Verified |
| api.jtrholidays.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=0; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.jtrholidays.com/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://api.jtrholidays.com/mcp/v1 | HTTPS enforced | 301 | https://api.jtrholidays.com/mcp/v1 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_availability ~75
Check if an activity is available on a specific date and get pricing options
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | Activity UUID |
| date | string | yes | Date to check in Y-m-d format (e.g. "2025-12-25") |
| pax | integer | – | Number of people (default: 1) |
No output schema declared.
No examples provided.
compare_activities ~78
Compare 2–5 JTR activities side-by-side on price, discount, rating, inclusions, and cancellation policy. Use this when a user asks "which is better?" or wants to choose between specific activities.
| Name | Type | Req | Description |
|---|---|---|---|
| activity_ids | array | yes | Array of 2–5 activity UUIDs to compare (from search_activities results) |
No output schema declared.
No examples provided.
get_activity_details ~43
Get full details for a single activity including inclusions, exclusions, cancellation policy, and reviews
| Name | Type | Req | Description |
|---|---|---|---|
| activity_id | string | yes | Activity UUID from search_activities results |
No output schema declared.
No examples provided.
get_current_offers ~81
Return activities with active discounts — where the current price is lower than the original price. Sorted by discount percentage. Use this when a user asks for deals, discounts, or best value.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Filter offers to a specific city or country |
| limit | integer | – | Max results (default: 20, max: 50) |
No output schema declared.
No examples provided.
get_destinations ~29
List all destinations (countries) where JTR Holidays offers tours, with activity counts and popular picks
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_holiday_packages ~71
Browse multi-day holiday packages with itineraries, departures, and pricing
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | Filter by country or region |
| duration_days | integer | – | Filter by exact number of days |
| limit | integer | – | Max results to return (default: 20, max: 50) |
No output schema declared.
No examples provided.
search_activities ~105
Search JTR Holidays activity/tour catalog by destination, category, and budget
| Name | Type | Req | Description |
|---|---|---|---|
| budget_max | number | – | Maximum price per person in the activity's local currency |
| category | string | – | Activity category (e.g. "Desert Safari", "Sightseeing") |
| destination | string | – | City or country name (e.g. "Dubai", "Singapore") |
| limit | integer | – | Max results to return (default: 20, max: 50) |
No output schema declared.
No examples provided.
What is the io.github.naeem-jtr/jtr-holidays MCP server?
io.github.naeem-jtr/jtr-holidays is an MCP server listed in the public MCP registry as io.github.naeem-jtr/jtr-holidays. Search tours, attraction tickets, and holiday packages across 24 countries. This page covers its hosted endpoint (https://api.jtrholidays.com/mcp/v1).
Is the io.github.naeem-jtr/jtr-holidays MCP server safe to use?
io.github.naeem-jtr/jtr-holidays scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.naeem-jtr/jtr-holidays MCP server expose?
io.github.naeem-jtr/jtr-holidays exposes 7 tools: search_activities, get_activity_details, check_availability, get_destinations, get_holiday_packages, and 2 more. Their descriptions and schemas cost roughly 482 tokens of context every time the server is loaded.
Does the io.github.naeem-jtr/jtr-holidays MCP server require authentication?
No. We connected to io.github.naeem-jtr/jtr-holidays without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.naeem-jtr/jtr-holidays MCP server still maintained?
io.github.naeem-jtr/jtr-holidays is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.