_ registry / mcp + a2a HTTP+JSON · checked 17m ago

loyaltyvip

https://loyaltyvip.com

Registry code: b7f0625429bb2de8

api record

LoyaltyVIP MCP. Use search_casinos / get_casino / list_rewards_programs for the public U.S. casino directory (no key). Use player_action with a Bearer API key for a player's own data.

endpoint
https://loyaltyvip.com/mcp
door code
83e595504346c43a
protocol
HTTP+JSON ·0.3
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is loyaltyvip live?
Yes — it answered the hub's last check (checked 17m ago). It answered 99% of checks over the last 30 days.
Is loyaltyvip free to use?
Yes — the hub reached it with no key and no payment.
What tools does loyaltyvip have?
6 tools: Get casino detail, Gambling tax documents, Cross-property tier match, Search casino directory, VIP host discovery, Comp / offer prediction.
Is loyaltyvip safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.3%· all time 99.3%

latency
333ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1110 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
games & entertainment
used for
  • search us casinos
  • get a casino rewards program and tiers
  • act on a player's loyalty account
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_casino reads unknown never probed

    Casino location, rewards/players-club program, and full tier ladder. Public, no key.

    casinorewardstierspublic

  • tax_summary unknown never probed

    Generate IRS gambling tax summaries, session logs, and W-2G reports. Requires API key (tax scope).

    taxw-2gauthenticatedsensitive

  • tier_match unknown never probed

    Find where a player is closest to a tier upgrade and draft a tier-match request. Requires API key (read).

    tierstier-matchauthenticated

  • search_casinos reads unknown never probed

    Search 2,400+ U.S. casinos by name, state, type, or rewards availability. Public, no key.

    casinodirectorypublicsearch

  • host_discovery unknown never probed

    Find and request connections with casino VIP hosts that match a player's profile. Requires API key (read).

    hostsdiscoveryauthenticated

  • comp_predict unknown never probed

    Predict likely comps and offers from a player's play history. Requires API key (read).

    compsofferspredictionauthenticated

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b7f0625429bb2de8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b7f0625429bb2de8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b7f0625429bb2de8/badge.svg)](https://brick.blue/agent/b7f0625429bb2de8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.