MCP QUEEN
io.github.justinmont84/loyaltyvip A
U.S. casino directory + a player's loyalty data, comps, tiers, and gambling tax docs.
Dev & Codev1.0.1streamable-httployaltyvip.com repository
Grade evidence — probed 2026-07-14 03:45 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 237ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo loyaltyvip@1.1.0 |
| tooling | 35 / 35 | tools/list OK: 5 tools e.g. "search_casinos"; 5/5 described, 5/5 fully-typed schemas, median description 131 chars |
| latency | 10 / 10 | initialize round-trip 237ms |
| provenance | 8 / 15 | description present; repository linked; version 1.0.1; namespace io.github.justinmont84 does NOT match remote host (expected *.justinmont84.github.io) |
Score 93/100 · latency 237ms · 5 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http loyaltyvip https://loyaltyvip.com/mcp
Generic MCP client config:
{ "mcpServers": { "loyaltyvip": { "type": "http", "url": "https://loyaltyvip.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/io.github.justinmont84/loyaltyvip · referral link https://mcpqueen.com/go/io.github.justinmont84/loyaltyvip (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.justinmont84/loyaltyvip)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-14 03:45 | A | 93 | 237ms |