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

Automatyzdarma 81 SI

listed under this name in a public catalogue; the server gives only its address, automatyzdarma-81.si

https://automatyzdarma-81.si

Registry code: f139cf0e1f986990

api record

Linije 81. Ocenjujemo spletne igralne avtomate, vendar nismo igralnica, zato stav in pologov ne sprejemamo. Ciljna publika so odrasli 18+. Velja samo tam, kjer je spletno igranje na srečo zakonito. Igralnice se na teh straneh pojavljajo prek povezav, za katere prejmemo plačilo. Pogoje za bonuse določajo posamezne igralnice, ne to spletišče. Vsaka recenzija opisuje delovanje igre, bonusne funkcije, RTP, volatilnost, največji dobitek, število kolutov in linij. RTP je teoretična dolgoročna številka; posamezne igralnice lahko navedejo drugačno vrednost. Za eno sejo ne pomeni nobene obljube.…

endpoint
https://automatyzdarma-81.si/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 Automatyzdarma 81 SI live?
Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
Is Automatyzdarma 81 SI free to use?
Yes — the hub reached it with no key and no payment.
What tools does Automatyzdarma 81 SI have?
2 tools: najboljsi_avtomati, iskanje_dobitki.
Is Automatyzdarma 81 SI 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
379ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 2 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.

  • najboljsi_avtomati unknown 13h ago

    Prejme naslov strani tega spletnega mesta in vrne njeno vsebino: podatke o igri ali seznam iger.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 300,
          "description": "Dopušča poln naslov strani tega spletnega mesta ali zgolj del, ki se začne s poševnico."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • iskanje_dobitki unknown 13h ago

    Poišče strani tega spletnega mesta, katerih imena vsebujejo vneseno besedilo: igre, studii iger in zbirke. Iskanje ne poteka po temi, tematiki ali opisu. Število ocen iger: 8

    mcp-tool

    {
      "type": "object",
      "required": [
        "isci"
      ],
      "properties": {
        "isci": {
          "type": "string",
          "maxLength": 64,
          "minLength": 2,
          "description": "Polje sprejme polno ali delno ime igre, studia oziroma zbirke, dolgo vsaj dva znaka."
        }
      },
      "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 f139cf0e1f986990.

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