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

Slots Diamant FR

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

https://slots-diamant.fr

Registry code: 183d12664aa6a7f2

api record

Slots Diamant. Plateforme de critiques de machines à sous en ligne. Aucun pari n'est accepté, aucun dépôt n'est possible. Des casinos partenaires sont liés depuis certaines pages. C’est chaque casino qui définit les conditions de bonus. Théorique et mesuré sur le long terme, le RTP varie selon les casinos et ne promet rien pour une session donnée. 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. Public adulte 18+ uniquement, dans les pays où le jeu en ligne est autorisé. Avis sur les jeux: 16.…

endpoint
https://slots-diamant.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 Diamant 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 Diamant FR free to use?
Yes — the hub reached it with no key and no payment.
What tools does Slots Diamant FR have?
3 tools: jackpots_sans_telechargement, rouleaux_recherche, rouleaux_en_ligne.
Is Slots Diamant 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
321ms

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.

  • rouleaux_en_ligne open 13h ago

    Cette fonction renvoie les collections de jeux du site et l'adresse de la page associée à chacune. Nombre de collections: 1

    mcp-tool

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

    Fournit, pour une adresse de page donnée, le contenu présenté : les informations relatives au jeu ou la liste des jeux.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 300,
      "description": "Ce paramètre reconnaît l'adresse complète de la page ou la portion qui commence par une barre oblique."
    }
  },
  "additionalProperties": false
}
    arguments 14 lines
  • rouleaux_recherche unknown 13h ago

    La recherche porte sur les noms de pages : jeux, studios de jeux et collections. Elle ne s'applique ni aux sujets, ni aux thèmes, ni aux descriptions. Avis sur les jeux: 16

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 64,
      "minLength": 2,
      "description": "Nom ou partie du nom d’un jeu, d’un studio ou d’une collection, 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 183d12664aa6a7f2.

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