_ registry / mcp streamable-http · checked 13h ago

Fun Slots UK

listed under this name in a public catalogue; the server gives only its address, fun-slots.uk

https://fun-slots.uk

Registry code: 8dec813151ede339

api record

Fun Slots. A site that reviews online slots. It is not a gambling operator and accepts no bets or deposits. The mechanics, bonus features, RTP, volatility, maximum win, reels and lines appear in every review. Casino links on these pages can be partner links. Bonus conditions belong to the casino that provides them. Each RTP figure is theoretical and can change from one casino to another, so no session outcome follows from it. This site is for adults 18+ who live where online gambling is legal. Review count: 10. Game studios covered: 1. Collections: 1.

endpoint
https://fun-slots.uk/mcp
protocol
streamable-http ·2025-06-18
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 Fun Slots UK live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is Fun Slots UK free to use?
Yes — the hub reached it with no key and no payment.
What tools does Fun Slots UK have?
3 tools: games_results, online_games, top_games.
Is Fun Slots UK 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
100%

90 days 100%· all time 100%

latency
251ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
1 open 2 never probed 1 of 3 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.

  • top_games open 13h ago

    Returns the themed collections of games published on this website, each with its page address. Collections: 1

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • games_results unknown 13h ago

    Finds game, game studio and collection pages by matching the given text against page names. Descriptions, topics and themes lie outside its scope. Review count: 10

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 64,
      "minLength": 2,
      "description": "A game, studio or collection title, or a fragment of one, containing two or more characters."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • online_games unknown 13h ago

    Given the address of a page, returns what the page shows: the details of one game or its list of games.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 300,
      "description": "Location of a page on this website, given as a full address or a path starting with a slash."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
_ try it 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 8dec813151ede339.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/8dec813151ede339/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/8dec813151ede339/badge.svg)](https://brick.blue/agent/8dec813151ede339?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 know
card completeness
70%

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.