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

Slots Fruits FR

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

https://slots-fruits.fr

Registry code: 9afb78f3f7984250

api record

Slots Fruits. Plateforme de critiques de machines à sous en ligne. Aucun pari n'est accepté, aucun dépôt n'est possible. Ce site contient des liens partenaires vers des casinos. Chaque casino fixe les conditions de ses bonus. Pour chaque machine à sous, la revue précise les mécanismes, les fonctions bonus, le RTP, la volatilité, le gain maximal, les rouleaux et les lignes. Le RTP relève d'un calcul théorique de long terme ; chaque casino peut en proposer une version différente, sans prédire l'issue d'une session. Pour les adultes 18+ seulement, là où le jeu en ligne est permis. Jeux testés:…

endpoint
https://slots-fruits.fr/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 Slots Fruits FR live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is Slots Fruits FR free to use?
Yes — the hub reached it with no key and no payment.
What tools does Slots Fruits FR have?
2 tools: top_bandits_manchots, jeux_recherche.
Is Slots Fruits FR 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
347ms

last good check

priced tools
0

of 2 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 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_bandits_manchots unknown 13h ago

    Renvoie, d'après l'adresse d'une page, les éléments visibles de cette page : le détail du jeu ou l'inventaire des jeux.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 300,
      "description": "L'adresse de la page peut être complète ou commencer par une barre oblique."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • jeux_recherche unknown 13h ago

    Fonction qui renvoie les pages dont le nom contient le texte saisi, parmi les jeux, les studios de jeux et les collections, sans tenir compte du sujet, du thème ou de la description. Jeux testés: 7

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 64,
      "minLength": 2,
      "description": "La valeur correspond au nom ou à un élément du nom d’un jeu, d’un studio ou d’une collection, à condition d’au moins deux caractères."
    }
  },
  "additionalProperties": false
}
    arguments 15 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 9afb78f3f7984250.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9afb78f3f7984250/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/9afb78f3f7984250/badge.svg)](https://brick.blue/agent/9afb78f3f7984250?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
60%

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.