Adaga Network — Direct Booking Federation
REMOTE · ADAGASOLUTIONS.LU
Search and book every Adaga network hotel at once: live availability, exact prices, real booking.
Available components
Last scanned (5 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security57
- 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 call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 851 tokens (~283/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
- Tool “network_directory” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://adagasolutions.lu/network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=adagasolutions.lu | CN=YE2,O=Let's Encrypt,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 541e1f36daaf32fec0fa5ba990fa5b96366 |
| SANs: adaga-solutions.com, adaga.lu, adagasolutions.lu, www.adaga-solutions.com, www.adaga.lu, www.adagasolutions.lu | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of adagasolutions.lu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| lu. | present | 20752 | 8 | Verified |
| adagasolutions.lu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://adagasolutions.lu/network/mcp | Verified | 200 | |
| http (plaintext) | http://adagasolutions.lu/network/mcp | HTTPS enforced | 301 | https://adagasolutions.lu/network/mcp |
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 →
network_book ~324
Create a REAL booking at one establishment of the Adaga network. WORKFLOW: (1) call network_search to get fresh availability and the exact price, (2) collect traveler full name and email, (3) call this tool, (4) give the human the payment instructions from the response — the booking is confirmed only after secure card payment; unpaid bookings expire automatically. Optional inputs: guests (number of guests), guest_phone (international format, e.g. +352661661438), special_requests (free text), breakfast (boolean), promo_code (string, validated by the establishment), extras (array of integer extra ids from the establishment offer). Fails with 409 if the room became unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| breakfast | boolean | – | Add breakfast if the establishment offers it |
| checkin | string | yes | Arrival date YYYY-MM-DD |
| checkout | string | yes | Departure date YYYY-MM-DD |
| extras | array | – | Extra ids (integers) from the establishment offer |
| guest_email | string | yes | Traveler email (confirmation is sent here) |
| guest_name | string | yes | Traveler full name |
| guest_phone | string | – | Traveler phone, international format (e.g. +352661661438) |
| guests | integer | – | Number of guests |
| promo_code | string | – | Promo code, validated by the establishment |
| room_id | integer | yes | Room id from network_search |
| special_requests | string | – | Free-text requests for the establishment |
| tenant_slug | string | yes | Establishment slug from network_search / network_directory |
No output schema declared.
No examples provided.
network_directory ~204
List every establishment in the Adaga direct-booking network. Each entry has a "tier" field: "verified" = connected via API, exposes real-time availability, exact prices and REAL booking creation via network_book; "listed" = public business data (name, address, phone, official website) provided for VISIBILITY only — NOT bookable here, check live prices and availability on the establishment's official website (official_site). No OTA commission on verified bookings: the traveler always pays the establishment's exact direct price, and the establishment keeps the customer relationship (OTAs take 15-25% AND own the customer). Use network_search instead when you already know the stay dates (it searches availability AND returns listed establishments too); use this tool when you need the full roster or an establishment's slug. No authentication required, no rate limit, no pagination — the complete directory is returned in one response. Use the slug for network_search and network_book (verified tier only).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
network_search ~323
Search the WHOLE Adaga network at once for a stay. VERIFIED establishments are queried live and return real-time availability with exact total prices (euro cents), sorted by price — like Booking.com but machine-native, at the establishments' exact direct prices (no OTA markup, no commission passed to the traveler). LISTED establishments matching the filters are appended as "listed_matches" (public data: official website + phone) — they are NOT bookable here; direct the traveler to their official website for live prices. Workflow for verified offers: (1) call this, (2) pick an offer (tenant_slug + room_id), (3) call network_book with traveler name and email, (4) hand the payment instructions to the human. Use network_directory instead when you need the full roster without stay dates. Constraints: dates YYYY-MM-DD, checkin < checkout, checkin not in the past, max 30 nights. A tenant that does not answer within 6 s is skipped (reported in errors). No authentication required, no rate limit, no pagination — all matching offers are returned in one response (bounded by the number of active establishments).
| Name | Type | Req | Description |
|---|---|---|---|
| checkin | string | yes | Arrival date YYYY-MM-DD |
| checkout | string | yes | Departure date YYYY-MM-DD |
| city | string | – | Filter by city (e.g. Luxembourg); omit to search everywhere |
| max_total_cents | integer | – | Budget cap for the whole stay, in euro cents |
| type | string | – | Establishment type filter, e.g. 'hotel' |
No output schema declared.
No examples provided.
How do I install the Adaga Network — Direct Booking Federation MCP server?
Adaga Network — Direct Booking Federation is a hosted endpoint at https://adagasolutions.lu/network/mcp, 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 · adagasolutions.lu
claude mcp add --transport http jeffreyturov-dev-adaga-network 'https://adagasolutions.lu/network/mcp'
What is the Adaga Network — Direct Booking Federation MCP server?
Adaga Network — Direct Booking Federation is an MCP server listed in the public MCP registry as io.github.jeffreyturov-dev/adaga-network. Search and book every Adaga network hotel at once: live availability, exact prices, real booking. This page covers its hosted endpoint (https://adagasolutions.lu/network/mcp).
Is the Adaga Network — Direct Booking Federation MCP server safe to use?
Adaga Network — Direct Booking Federation scores 73 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 Adaga Network — Direct Booking Federation MCP server expose?
Adaga Network — Direct Booking Federation exposes 3 tools: network_directory, network_search, network_book. Their descriptions and schemas cost roughly 851 tokens of context every time the server is loaded.
Does the Adaga Network — Direct Booking Federation MCP server require authentication?
No. We connected to Adaga Network — Direct Booking Federation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Adaga Network — Direct Booking Federation MCP server still maintained?
Adaga Network — Direct Booking Federation is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.