io.github.justinmont84/loyaltyvip
REMOTE · LOYALTYVIP.COM · 2 COMPONENTS · SCANNED SEP 22
U.S. casino directory + a player's loyalty data, comps, tiers, and gambling tax docs.
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 5 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 417 tokens (~69/item across 6 items; 5 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 54% of tool parameters carry a description.Partial
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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the io.github.justinmont84/loyaltyvip MCP server?
io.github.justinmont84/loyaltyvip is a hosted endpoint at https://loyaltyvip.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 · loyaltyvip.com
claude mcp add --transport http justinmont84-loyaltyvip 'https://loyaltyvip.com/mcp'
{
"mcpServers": {
"justinmont84-loyaltyvip": {
"url": "https://loyaltyvip.com/mcp"
}
}
} {
"servers": {
"justinmont84-loyaltyvip": {
"type": "http",
"url": "https://loyaltyvip.com/mcp"
}
}
} [mcp_servers.justinmont84-loyaltyvip] url = "https://loyaltyvip.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"justinmont84-loyaltyvip": {
"type": "remote",
"url": "https://loyaltyvip.com/mcp",
"enabled": true
}
}
} openclaw mcp add justinmont84-loyaltyvip --url 'https://loyaltyvip.com/mcp' --transport streamable-http
mcp_servers:
justinmont84-loyaltyvip:
url: "https://loyaltyvip.com/mcp" {
"McpServers": {
"justinmont84-loyaltyvip": {
"Transport": "http",
"Url": "https://loyaltyvip.com/mcp"
}
}
} assistant mcp add justinmont84-loyaltyvip -t streamable-http -u 'https://loyaltyvip.com/mcp'
{
"mcpServers": {
"justinmont84-loyaltyvip": {
"type": "http",
"url": "https://loyaltyvip.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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 +1
- Stability: 0.97 → pass security
- 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
- 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
- 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
- 26 Jul 26 0
First indexed and scored.
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 22 Sept 2026 · Probed https://loyaltyvip.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.loyaltyvip.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 30 Apr 2026 | 13 Nov 2026 | RSA 2048 | SHA256-RSA | 49a5bdbbe410ff27b257efd43e2585d |
| SANs: *.loyaltyvip.com, loyaltyvip.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of loyaltyvip.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| loyaltyvip.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 | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| 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://loyaltyvip.com/mcp | Verified | 200 | |
| http (plaintext) | http://loyaltyvip.com/mcp | HTTPS enforced | 301 | https://loyaltyvip.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 →
get_casino ~52
Get a casino's detail including its rewards/players-club program and full tier ladder, by slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Casino slug, e.g. bellagio-nv-880e8400 |
No output schema declared.
No examples provided.
get_rewards_program ~64
Get one rewards/players-club program by id — brand, earning rules, status-match notes, and full tier ladder. (get_casino also returns a casino's program inline.)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Rewards program id (UUID), from list_rewards_programs |
No output schema declared.
No examples provided.
list_rewards_programs ~48
List casino rewards/players-club programs, optionally filtered by search term or brand.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | – |
| limit | integer | – | – |
| search | string | – | – |
No output schema declared.
No examples provided.
player_action ~88
Authenticated. Invoke any LoyaltyVIP player/host action (proxies POST /v1/player). Requires a Bearer API key in the Authorization header. Examples: tier_status, bankroll_status, list_trips, list_w2g, tax_year_summary, host_dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action name, e.g. tier_status |
| params | object | – | Optional action parameters |
No output schema declared.
No examples provided.
search_casinos ~104
Search the public U.S. casino directory by name, state (two-letter code), type (commercial|tribal|racino), or rewards availability.
| Name | Type | Req | Description |
|---|---|---|---|
| has_rewards | boolean | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| q | string | – | Name search |
| state | string | – | Two-letter state code, e.g. NV |
| type | string | – | casino_type: commercial | tribal | racino |
No output schema declared.
No examples provided.
What is the io.github.justinmont84/loyaltyvip MCP server?
io.github.justinmont84/loyaltyvip is an MCP server listed in the public MCP registry as io.github.justinmont84/loyaltyvip. U.S. casino directory + a player's loyalty data, comps, tiers, and gambling tax docs. This page covers its hosted endpoint (https://loyaltyvip.com/mcp).
Is the io.github.justinmont84/loyaltyvip MCP server safe to use?
io.github.justinmont84/loyaltyvip scores 80 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.justinmont84/loyaltyvip MCP server expose?
io.github.justinmont84/loyaltyvip exposes 5 tools: search_casinos, get_casino, list_rewards_programs, get_rewards_program, player_action. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Does the io.github.justinmont84/loyaltyvip MCP server require authentication?
No. We connected to io.github.justinmont84/loyaltyvip without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.justinmont84/loyaltyvip MCP server still maintained?
io.github.justinmont84/loyaltyvip is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.