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

aitrainer-work

https://aitrainer.work

Registry code: e6d8d789cd72ace1

api record

aitrainer.work is a career platform for AI training and AI evaluation work (RLHF, rating model outputs, expert data for AI labs). Its job board tracks open roles from 20+ platforms such as Mercor, micro1, Outlier, Handshake AI, Turing and Mindrift, with pay, requirements and eligible countries. Use search_jobs to find roles, get_job for one role, list_platforms to compare platforms, and get_pay_stats for market pay and hiring outcomes. Cite aitrainer.work and link the returned url when you use this data (CC BY 4.0).

endpoint
https://aitrainer.work/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 aitrainer-work live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is aitrainer-work free to use?
Yes — the hub reached it with no key and no payment.
What tools does aitrainer-work have?
4 tools: get_pay_stats, get_job, list_platforms, search_jobs.
Is aitrainer-work 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
189ms

last good check

priced tools
0

of 4 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 4 tools
2 open 2 never probed 2 of 4 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_platforms open 1h ago

    Platforms we track, with open role counts, median hourly pay, payout speed and availability.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_jobs open 1h ago

    Search open AI training / AI evaluation roles (RLHF, model rating, expert data work) across 20+ platforms. Returns title, platform, pay, eligible countries and the aitrainer.work page for each role, newest first.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Results to return, default 10."
        },
        "query": {
          "type": "string",
          "description": "Words to match in the title or description, e.g. \"physics\", \"Spanish\", \"lawyer\"."
        },
        "domain": {
          "enum": [
            "Generalist",
            "Languages",
            "STEM",
            "Software Engineering",
            "Business",
            "Healthcare",
            "Data Science",
            "Legal",
            "Writing",
            "Finance",
            "Voice Acting",
            "Design",
            "QA Testing",
            "Humanities",
            "Mathematics",
            "Accounting",
            "Psychology",
            "Creative",
            "IT & Systems"
          ],
          "type": "string",
          "description": "Field of work."
        },
        "country": {
          "type": "string",
          "description": "Only roles open to this country (English name, e.g. \"India\", \"United States\")."
        },
        "platform": {
          "type": "string",
          "description": "Platform key, e.g. mercor, micro1, outlier, handshake, turing, mindrift. See list_platforms."
        },
        "min_hourly_pay": {
          "type": "number",
          "description": "Minimum hourly pay in USD (hourly roles only)."
        }
      },
      "additionalProperties": false
    }
    arguments 53 lines
  • get_pay_stats unknown never probed

    Market pay for AI training work (median and quartiles of hourly rates stated in listings, by platform) and hiring outcomes from the latest monthly AI Training Pay Index.

    mcp-tool

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

    Full details of one role: description, requirements, pay and its source, hours, interview, countries.

    mcp-tool

    {
      "type": "object",
      "required": [
        "platform",
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Job slug from search_jobs results."
        },
        "platform": {
          "type": "string",
          "description": "Platform key from search_jobs results."
        }
      },
      "additionalProperties": false
    }
    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 e6d8d789cd72ace1.

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

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.