Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

짓닷 자재 찾기

REMOTE · JITDOT.COM

짓닷(jitdot.com)에 공개된 타일 · 마루 · LVT 등 인테리어 마감재를 규격 · 재질 · 마감으로 찾는 읽기 전용 카탈로그

Available components

+2 this week 76 Trust /100

Last scanned (13 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1302 tokens (~260/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 −1
    • Tool “get_design_files” rewrote its description, which is the text the model reads security
    • Tool “get_materials” rewrote its description, which is the text the model reads security
    • Tool “search_materials” rewrote its description, which is the text the model reads security
    • Schema quality: 185 → 260 ▼ functional
    • Server version: 1.0.0 → 1.1.0 functional
    • “list_filters” reworded the description of “category” cosmetic
    • “search_materials” reworded the description of “category” cosmetic
    • “search_materials” reworded the description of “query” cosmetic
  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://jitdot.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jitdot.com CN=YR2,O=Let's Encrypt,C=US 2 Oct 2026 31 Dec 2026 RSA 4096 SHA256-RSA 6a8364a63c196a5c8fbc5d84f79a753e449
SANs: jitdot.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jitdot.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jitdot.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'self' https://erp.jitdot.com
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(), geolocation=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jitdot.com/mcp Verified 200
http (plaintext) http://jitdot.com/mcp HTTPS enforced 301 https://jitdot.com/mcp
MCP tools · 5 exposed · ~1,249 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_stock ~76

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

NameTypeReqDescription
codesarrayyes짓닷코드 1~10개
NameTypeReqDescription
as_ofstringyes–
itemsarrayyes–
not_foundarrayyes–
noticestringyes–
sourcestringyes–
terms_urlstringyes–

No examples provided.

get_design_files ~150

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

NameTypeReqDescription
codestringyes짓닷코드(jitdot code). 예: BTAJ8899
NameTypeReqDescription
codestringyes–
display_namestringyes–
filesarrayyes–
notestringyes–
sourcestringyes–
terms_urlstringyes–

No examples provided.

get_materials ~111

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

NameTypeReqDescription
codesarrayyes짓닷코드 1~10개
NameTypeReqDescription
as_ofstringyes–
itemsarrayyes–
not_foundarrayyes–
noticestringyes–
price_notestringyes–
sourcestringyes–
terms_urlstringyes–

No examples provided.

list_filters ~243

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

NameTypeReqDescription
categorystring–분류(category): 타일(tile) · 마루(wood flooring) · 카펫타일(carpet tile) · LVT · 포보(Forbo linoleum) · 욕실도기(bathroom fixtures: 양변기 · 세면기 · 소변기 · 수전 · 샤워기 · 액세서리 세트 · 거울 · 거울장 · 욕실 천장(SMC)) · 벽재(wall finishes: 벽…
NameTypeReqDescription
as_ofstringyes–
categoryarrayyes–
finisharrayyes–
materialarrayyes–
scopestring|nullyes–
sizearrayyes–
sourcestringyes–
terms_urlstringyes–

No examples provided.

search_materials ~669

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

NameTypeReqDescription
categorystring–분류(category): 타일(tile) · 마루(wood flooring) · 카펫타일(carpet tile) · LVT · 포보(Forbo linoleum) · 욕실도기(bathroom fixtures: 양변기 · 세면기 · 소변기 · 수전 · 샤워기 · 액세서리 세트 · 거울 · 거울장 · 욕실 천장(SMC)) · 벽재(wall finishes: 벽…
finishstring–마감(finish): 무광(matte) · 유광(glossy) · 반광(semi-gloss)
has_sketchupboolean–스케치업 .skm 을 받을 수 있는 자재만(SketchUp material available)
in_stock_onlyboolean–재고 있는 자재를 먼저 채우고, 모자라면 재고 확인 필요 자재를 뒤에 붙인다. 품절은 뺀다
limitinteger––
materialstring–재질(material). list_filters 가 돌려준 값만. 예: 포세린 · 도기질 · 원목 · 마모륨
pageinteger––
querystring–표시명 · 색 이름에서 찾을 낱말(keywords). 예: 콘크리트룩 그레이 · 테라조 · 양변기
sizestring–가로x세로(size in mm). 순서는 상관없다. 예: 600x600 · 300x600
NameTypeReqDescription
as_ofstringyes–
itemsarrayyes–
limitintegeryes–
next_pageinteger|nullyes–
noticestringyes–
pageintegeryes–
price_notestringyes–
queryobjectyes–
sourcestringyes–
terms_urlstringyes–
totalintegeryes–

No examples provided.

Install

How do I install the 짓닷 자재 찾기 MCP server?

짓닷 자재 찾기 is a hosted endpoint at https://jitdot.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · jitdot.com

# add to Claude Code
claude mcp add --transport http com-jitdot-catalog 'https://jitdot.com/mcp'
Common questions

What is the 짓닷 자재 찾기 MCP server?

짓닷 자재 찾기 is an MCP server listed in the public MCP registry as com.jitdot/catalog. 짓닷(jitdot.com)에 공개된 타일 · 마루 · LVT 등 인테리어 마감재를 규격 · 재질 · 마감으로 찾는 읽기 전용 카탈로그. This page covers its hosted endpoint (https://jitdot.com/mcp).

Is the 짓닷 자재 찾기 MCP server safe to use?

짓닷 자재 찾기 scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the 짓닷 자재 찾기 MCP server expose?

짓닷 자재 찾기 exposes 5 tools: search_materials, get_materials, get_design_files, check_stock, list_filters. Their descriptions and schemas cost roughly 1,249 tokens of context every time the server is loaded.

Does the 짓닷 자재 찾기 MCP server require authentication?

No. We connected to 짓닷 자재 찾기 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 짓닷 자재 찾기 MCP server still maintained?

짓닷 자재 찾기 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.