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

maison-de-talents

https://maisondetalents.com

Registry code: 31330e1935774048

api record

메종 드 탤런트(https://maisondetalents.com)는 백화점·면세점·명품 매장 판매직·서비스직 전문 채용 플랫폼입니다. 한국의 백화점·면세점·명품 브랜드 매장 판매직(CA·SA·BA·뷰티 어드바이저·매니저) 채용공고와 연봉 정보를 제공합니다. 결과의 url 은 원문 공고 페이지이며, 지원은 그 페이지에서 진행됩니다.

endpoint
https://maisondetalents.com/api/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 maison-de-talents live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is maison-de-talents free to use?
Yes — the hub reached it with no key and no payment.
What tools does maison-de-talents have?
3 tools: get_job, get_salary_benchmark, search_jobs.
Is maison-de-talents 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.8%

90 days 99.1%· all time 99.1%

latency
395ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 348 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search luxury retail jobs in korea
  • get job posting details
  • get salary benchmarks for retail roles
takes → gives
text → data
tools
3 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 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.

  • search_jobs reads open 15h ago

    [메종 드 탤런트 명품 매장 채용] 한국 백화점·면세점·명품 브랜드 매장의 진행 중인 채용공고를 검색합니다(판매직 CA/SA/BA, 뷰티 어드바이저, 매장 매니저, VMD 등). Search active retail job postings at luxury brand boutiques, department stores and duty-free shops in Korea (e.g. Chanel, Louis Vuitton, Rolex, Lotte Duty Free). 모든 인자는 선택입니다.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "brand": {
          "type": "string",
          "maxLength": 40,
          "description": "브랜드명 한글/영문 (예: 샤넬, Rolex, 루이비통)"
        },
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "최대 결과 수(기본 5, 최대 10)"
        },
        "query": {
          "type": "string",
          "maxLength": 50,
          "description": "직무·키워드 (예: 판매, 뷰티 어드바이저, 매니저, 면세점)"
        },
        "region": {
          "type": "string",
          "maxLength": 20,
          "description": "근무 지역 (예: 서울, 강남구, 부산, 인천공항)"
        }
      }
    }
    arguments 27 lines
  • get_job reads unknown 15h ago

    [메종 드 탤런트 명품 매장 채용] search_jobs 로 찾은 공고 id 의 상세(자격요건·근무조건·급여·마감일)를 가져옵니다. Get details of a job posting by id.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "format": "uuid",
          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
          "description": "search_jobs 결과의 공고 id"
        }
      }
    }
    arguments 15 lines
  • get_salary_benchmark reads unknown 15h ago

    [메종 드 탤런트 명품 매장 채용] 한국 럭셔리 리테일 매장직 연봉 벤치마크(만원, 연봉 기준)를 업종·경력별로 조회합니다. Salary benchmarks for Korean luxury/department store/duty-free retail staff by category and experience. 업종: luxury=럭셔리 패션, cosmetics=뷰티/화장품, jewelry=시계/주얼리, fashion=패션/의류, food=프리미엄 F&B, department=백화점, dutyfree=면세점, lifestyle=라이프스타일. 경력: entry=신입(0년), junior=주니어(1~3년), mid=미들(3~5년), senior=시니어(5~10년), lead=리드(10년+).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "category"
      ],
      "properties": {
        "category": {
          "enum": [
            "luxury",
            "cosmetics",
            "jewelry",
            "fashion",
            "food",
            "department",
            "dutyfree",
            "lifestyle"
          ],
          "type": "string",
          "description": "업종 코드"
        },
        "experience": {
          "enum": [
            "entry",
            "junior",
            "mid",
            "senior",
            "lead"
          ],
          "type": "string",
          "description": "경력 코드(생략 시 전 구간)"
        }
      }
    }
    arguments 34 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 31330e1935774048.

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