_ registry / mcp http-sse · checked 11h ago

jitdot-catalog

https://jitdot.com

Registry code: bcb05cd8193a2565

api record

짓닷(jitdot.com) 카탈로그. 가격 · 재고는 응답 시각 기준이며 주문 전 짓닷에서 확인해야 합니다. 회원 등급별 가격은 jitdot.com 에서 확인하실 수 있습니다.

endpoint
https://jitdot.com/mcp
protocol
http-sse ·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 jitdot-catalog live?
Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
Is jitdot-catalog free to use?
Yes — the hub reached it with no key and no payment.
What tools does jitdot-catalog have?
5 tools: check_stock, search_materials, get_materials, get_design_files, list_filters.
Is jitdot-catalog 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
1,901ms

last good check

priced tools
0

of 5 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 5 tools
1 open 4 never probed 1 of 5 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_filters open 11h ago

    고를 수 있는 분류 · 규격 · 재질 · 마감과 그 종수를 본다. 분류를 주면 규격 · 재질 · 마감을 그 분류 안에서 센다. search_materials 의 조건 값은 여기서 고른다.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "category": {
          "enum": [
            "타일",
            "마루",
            "카펫타일",
            "LVT",
            "포보",
            "포보(LVS)"
          ],
          "type": "string",
          "description": "분류(category): 타일(tile) · 마루(wood flooring) · 카펫타일(carpet tile) · LVT · 포보(Forbo linoleum). list_filters 가 돌려준 값을 그대로 써도 된다"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • check_stock unknown 11h ago

    짓닷코드로 지금 재고 상태를 본다. 수량이 아니라 「재고 있음 · 재고 확인 필요 · 품절」 셋 가운데 하나이며 응답 시각 기준이다. 한 번에 10개까지.

    mcp-tool

    {
      "type": "object",
      "required": [
        "codes"
      ],
      "properties": {
        "codes": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^[A-Za-z0-9_-]{2,32}$",
            "description": "짓닷코드(jitdot code). 예: BTAJ8899"
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "짓닷코드 1~10개"
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • search_materials unknown 11h ago

    짓닷(jitdot.com)에 공개된 인테리어 마감재(타일 · 마루 · 카펫타일 · LVT · 포보)를 조건으로 찾는다. 규격 · 재질 · 마감 값은 list_filters 가 돌려준 값만 쓴다. 가격은 공개된 소비자가가 있는 자재에만 붙고 회원 등급 가격은 없다. 재고는 수량이 아니라 「재고 있음 · 재고 확인 필요 · 품절」이며 응답 시각 기준이다. 사람에게 답할 때는 짓닷코드와 표시명을 그대로 쓰고 urls.document 주소를 함께 준다. 추천 이유가 필요한 대화형 검색은 짓닷의 자재 검색 AI 짓피티(https://jitdot.com/jitpt)에서 한다.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "page": {
          "type": "integer",
          "default": 1,
          "maximum": 5,
          "minimum": 1
        },
        "size": {
          "type": "string",
          "pattern": "^[0-9][0-9,]*(\\.[0-9]+)?\\s*[xX×*]\\s*[0-9][0-9,]*(\\.[0-9]+)?$",
          "description": "가로x세로(size in mm). 순서는 상관없다. 예: 600x600 · 300x600"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 24,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "maxLength": 100,
          "description": "표시명 · 색 이름에서 찾을 낱말(keywords). 예: 콘크리트룩 그레이 · 테라조"
        },
        "finish": {
          "enum": [
            "무광",
            "유광",
            "반광"
          ],
          "type": "string",
          "description": "마감(finish): 무광(matte) · 유광(glossy) · 반광(semi-gloss)"
        },
        "category": {
          "enum": [
            "타일",
            "마루",
            "카펫타일",
            "LVT",
            "포보",
            "포보(LVS)"
          ],
          "type": "string",
          "description": "분류(category): 타일(tile) · 마루(wood flooring) · 카펫타일(carpet tile) · LVT · 포보(Forbo linoleum). list_filters 가 돌려준 값을 그대로 써도 된다"
        },
        "material": {
          "type": "string",
          "maxLength": 20,
          "description": "재질(material). list_filters 가 돌려준 값만. 예: 포세린 · 도기질 · 원목 · 마모륨"
        },
        "has_sketchup": {
          "type": "boolean",
          "default": false,
          "description": "스케치업 .skm 을 받을 수 있는 자재만(SketchUp material available)"
        },
        "in_stock_only": {
          "type": "boolean",
          "default": false,
          "description": "재고 있는 자재를 먼저 채우고, 모자라면 재고 확인 필요 자재를 뒤에 붙인다. 품절은 뺀다"
        }
      },
      "additionalProperties": false
    }
    arguments 64 lines
  • get_materials unknown never probed

    짓닷코드(jitdot code)로 자재의 공개 정보를 본다 — 표시명 · 분류 · 재질 · 마감 · 규격(mm) · 사진 · 설계 파일 유무 · 재고 유무 · 공개 소비자가. 한 번에 10개까지. 공개 카탈로그에 없는 코드는 not_found 에 담긴다.

    mcp-tool

    {
      "type": "object",
      "required": [
        "codes"
      ],
      "properties": {
        "codes": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^[A-Za-z0-9_-]{2,32}$",
            "description": "짓닷코드(jitdot code). 예: BTAJ8899"
          },
          "maxItems": 10,
          "minItems": 1,
          "description": "짓닷코드 1~10개"
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • get_design_files unknown never probed

    자재 하나의 설계 파일(스케치업 재질 .skm · 캐드 해치 .pat · 캐드 범례 .dxf · 텍스처 사진)이 있는지와 받는 곳을 본다. 설계 파일은 짓닷 회원만 받는다 — 회원 가입 뒤 라이브러리 자재 카드에서 받는다. 이 도구는 파일을 내주지 않는다.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "pattern": "^[A-Za-z0-9_-]{2,32}$",
          "description": "짓닷코드(jitdot code). 예: BTAJ8899"
        }
      },
      "additionalProperties": false
    }
    arguments 14 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 bcb05cd8193a2565.

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

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.