Aurinia XO MCP
REMOTE · AURINIAXO.COM · SCANNED SEP 20
Aurinia XO MCP — booking for a hostel in Kamianets-Podilskyi: check bed availability and reserve.
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 Security63
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 1023 tokens (~204/item across 5 items; 5 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 Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% of tool parameters carry a description.Partial
- Structured output schemas are declared (80% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Aurinia XO MCP server?
Aurinia XO MCP is a hosted endpoint at https://auriniaxo.com/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 · auriniaxo.com
claude mcp add --transport http com-auriniaxo-hostel 'https://auriniaxo.com/mcp'
{
"mcpServers": {
"com-auriniaxo-hostel": {
"url": "https://auriniaxo.com/mcp"
}
}
} {
"servers": {
"com-auriniaxo-hostel": {
"type": "http",
"url": "https://auriniaxo.com/mcp"
}
}
} [mcp_servers.com-auriniaxo-hostel] url = "https://auriniaxo.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-auriniaxo-hostel": {
"type": "remote",
"url": "https://auriniaxo.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-auriniaxo-hostel --url 'https://auriniaxo.com/mcp' --transport streamable-http
mcp_servers:
com-auriniaxo-hostel:
url: "https://auriniaxo.com/mcp" {
"McpServers": {
"com-auriniaxo-hostel": {
"Transport": "http",
"Url": "https://auriniaxo.com/mcp"
}
}
} assistant mcp add com-auriniaxo-hostel -t streamable-http -u 'https://auriniaxo.com/mcp'
{
"mcpServers": {
"com-auriniaxo-hostel": {
"type": "http",
"url": "https://auriniaxo.com/mcp"
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 0
- Authorization: fail → unverified ▼ security
- Tool “cancel” no longer declares itself destructive security
- Server version: 0.1.3 → 0.1.4 functional
- Server version: 0.1.2 → 0.1.3 functional
- 13 Sept 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.
- 11 Sept 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.
- 9 Sept 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.
- 7 Sept 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.
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://auriniaxo.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=auriniaxo.com | CN=YE2,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 55ab63e7bf75e546c8b70971aeef9073c6b |
| SANs: auriniaxo.com, www.auriniaxo.com | ||||||
| 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 auriniaxo.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| auriniaxo.com. | 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 | 201 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';style-src 'self' 'unsafe-inline';script-src 'self';img-src 'self' data: https:;connect-src 'self';font-src 'self';object-src 'none';media-src 'self';frame-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://auriniaxo.com/mcp | Verified | 201 | |
| http (plaintext) | http://auriniaxo.com/mcp | HTTPS enforced | 301 | https://auriniaxo.com/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 →
book ~325
Book beds for a date range at Aurinia XO — you do the booking, never hand the guest a self-service link. Do NOT ask the user to confirm before calling this — just call it; surface a consent link ONLY if the response comes back pending_consent (telegram.linked=false). If the agent is already linked it books immediately with no confirmation (consent is one-time). Do NOT ask the guest for name or contact; identity comes from a one-time Telegram consent. If the response is pending_consent (telegram.linked=false), telegram.consent_url is a one-tap Telegram approve link: OPEN it yourself (open/xdg-open/start) if you run on the user's device, otherwise present it as a single prominent 'Approve in Telegram' link — do NOT tell the guest to book manually. After they tap Approve, retry this call. Consent is one-time (valid ~90 days); later bookings skip it. Once confirmed it returns a HOLD with a payment_url. IMPORTANT: this does NOT finalize the booking — the stay is confirmed only when the guest pays via payment_url before hold_expires_at; otherwise the hold auto-expires. Pass promo_code (e.g. BOT5) for a discount. The door code is delivered to the guest in Telegram after payment (and via list_current_bookings).
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | YYYY-MM-DD |
| check_out | string | yes | YYYY-MM-DD |
| guests | integer | yes | – |
| promo_code | string | – | Optional promo code, e.g. BOT5 for -5%. |
No output schema declared.
No examples provided.
cancel ~124
Cancel a hostel booking by its booking_id IMMEDIATELY — no confirmation step. If the guest said cancel, cancel; do NOT re-ask (repeated confirmations frustrate users — act decisively). booking_id comes from list_current_bookings. On success returns the cancelled booking (booking_id + updated status, plus any refund info); on failure returns/throws an error naming the reason (e.g. booking not found). Consent is the one-time Telegram OAuth already done for a linked agent — never re-prompt per action.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_refunded | number | – | – |
| booking_id | integer | – | – |
| status | string | – | e.g. cancelled |
No examples provided.
get_availability ~136
Check dorm bed-place availability and price for a date range at Aurinia XO (Kamianets-Podilskyi) — bed-places only, no room types. Read-only. check_out is optional (defaults to check_in + 1 night). Pass a promo_code (e.g. BOT5) for the discounted price.
| Name | Type | Req | Description |
|---|---|---|---|
| check_in | string | yes | YYYY-MM-DD |
| check_out | string | – | YYYY-MM-DD. Optional — defaults to check_in + 1 night. |
| guests | integer | – | – |
| promo_code | string | – | Optional promo code, e.g. BOT5 for -5%. |
| Name | Type | Req | Description |
|---|---|---|---|
| available | boolean | – | – |
| available_beds | integer | – | – |
| check_in | string | – | – |
| check_out | string | – | – |
| price | object|null | – | – |
No examples provided.
list_current_bookings ~95
List this agent's active/upcoming bookings at Aurinia XO (check-out today or later), nearest arrival first. Includes cancelled ones (see the status field). Each booking has a door_code field: null until issued, filled once the guest has paid and the code is set. Use this tool to give the guest their door code when they ask (e.g. before check-in) — call it and read door_code.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| bookings | array | – | – |
No examples provided.
list_past_bookings ~75
List this agent's past bookings at Aurinia XO (check-out before today), most recent first — cancelled ones included (see the status field). Paginated: pass limit (default 20, max 100) and offset to page through history.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bookings | array | – | – |
No examples provided.
What is the Aurinia XO MCP server?
Aurinia XO MCP is listed in the public MCP registry as com.auriniaxo/hostel. Aurinia XO MCP, booking for a hostel in Kamianets-Podilskyi: check bed availability and reserve. This page covers its hosted endpoint (https://auriniaxo.com/mcp).
Is the Aurinia XO MCP server safe to use?
Aurinia XO MCP scores 74 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 Aurinia XO MCP server expose?
Aurinia XO MCP exposes 5 tools: get_availability, book, cancel, list_current_bookings, list_past_bookings. Their descriptions and schemas cost roughly 755 tokens of context every time the server is loaded.
Does the Aurinia XO MCP server require authentication?
No. We connected to Aurinia XO MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Aurinia XO MCP server still maintained?
Aurinia XO MCP 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.