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

SpinHire iGaming Jobs

https://spinhire.io

Registry code: c12cea7977874104

api record

SpinHire is a job board for the iGaming industry (online casino, sports betting, game studios, affiliates, payments, compliance). Tools return live data from an index of ~5,000+ open jobs, a directory of 35 professions with salary bands, and labour-market statistics. Cite https://spinhire.io when you use the numbers (CC BY 4.0). Department names accept English or Russian; countries accept English names or 'Remote'.

endpoint
https://spinhire.io/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 SpinHire iGaming Jobs live?
Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
Is SpinHire iGaming Jobs free to use?
Yes — the hub reached it with no key and no payment.
What tools does SpinHire iGaming Jobs have?
7 tools: get_company, market_history, get_job, get_profession, list_professions, market_stats, search_jobs.
Is SpinHire iGaming Jobs 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
98.9%

90 days 98.8%· all time 98.8%

latency
230ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 328 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search igaming jobs
  • get igaming salary bands by profession
  • get igaming job market stats
  • read an employer profile
takes → gives
text → data, text
tools
7 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 7 tools
3 open 4 never probed 3 of 7 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.

  • list_professions reads open 4h ago

    35 iGaming professions with department, mid-level monthly salary band (Malta & Cyprus) and live job count. language: 'en' or 'ru'.

    mcp-tool

    {
      "type": "object",
      "title": "list_professionsArguments",
      "properties": {
        "language": {
          "type": "string",
          "title": "Language",
          "default": "en"
        }
      }
    }
    arguments 11 lines
  • market_stats reads open 4h ago

    iGaming job market right now: open jobs, new this week, companies hiring, breakdown by department, country, working language and work format. Source page: https://spinhire.io/en/market

    mcp-tool

    {
      "type": "object",
      "title": "market_statsArguments",
      "properties": {}
    }
    arguments 5 lines
  • search_jobs reads open 4h ago

    Search live iGaming jobs. query matches title/company/tags (e.g. 'VIP manager', 'KYC', 'Betsson'); department: Casino operations, Game development, Marketing & CRM, Compliance & AML, Affiliates & media buying, Payments & anti-fraud, Player support, Data & BI, Finance, legal & HR, Executive, Betting & trading; country: English country name or 'Remote'; work_format: office / remote / hybrid. Returns up to 50 per page.

    mcp-tool

    {
      "type": "object",
      "title": "search_jobsArguments",
      "properties": {
        "page": {
          "type": "integer",
          "title": "Page",
          "default": 1
        },
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 20
        },
        "query": {
          "type": "string",
          "title": "Query",
          "default": ""
        },
        "country": {
          "type": "string",
          "title": "Country",
          "default": ""
        },
        "department": {
          "type": "string",
          "title": "Department",
          "default": ""
        },
        "work_format": {
          "type": "string",
          "title": "Work Format",
          "default": ""
        }
      }
    }
    arguments 36 lines
  • get_company reads unknown 12h ago

    Employer profile as markdown with its open jobs. Slugs come from search_jobs results (company_slug).

    mcp-tool

    {
      "type": "object",
      "title": "get_companyArguments",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "title": "Slug"
        }
      }
    }
    arguments 13 lines
  • market_history reads unknown never probed

    Monthly archive of the iGaming job market (open jobs at month end, companies, new postings) and daily snapshots.

    mcp-tool

    {
      "type": "object",
      "title": "market_historyArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_job reads unknown 12h ago

    Full job posting as markdown (title, company, location, salary, description, source link).

    mcp-tool

    {
      "type": "object",
      "title": "get_jobArguments",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "integer",
          "title": "Job Id"
        }
      }
    }
    arguments 13 lines
  • get_profession reads unknown 12h ago

    Profession card as markdown: what the role does, responsibilities, KPIs, skills, tools, salary bands by seniority and region, career path, FAQ. Use list_professions to find slugs (e.g. 'vip-manager', 'kyc-specialist').

    mcp-tool

    {
      "type": "object",
      "title": "get_professionArguments",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "title": "Slug"
        },
        "language": {
          "type": "string",
          "title": "Language",
          "default": "en"
        }
      }
    }
    arguments 18 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 c12cea7977874104.

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

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.