Context7
ส่งคู่มือการใช้ไลบรารีและเฟรมเวิร์กรุ่นล่าสุดให้ AI อ่านก่อนตอบ ช่วยให้โค้ดที่ AI เขียนไม่ใช้คำสั่งเก่าที่เลิกใช้แล้ว
คำอธิบายจากผู้ทำ (ภาษาอังกฤษตามต้นฉบับ)
Korean public procurement law: rule-engine rulings, statutes search, live court precedents
สามเรื่องนี้ไม่รวมเป็นคะแนนเดียว เพราะความเห็น การวัด และความนิยม เป็นคนละเรื่องกัน
ตัวนี้ยังไม่ได้เรียบเรียงเป็นภาษาไทย ด้านล่างคือข้อเท็จจริงที่เราอ่านจาก registry
เลือกโปรแกรม AI ที่คุณใช้ แล้วคัดลอกค่าตั้งไปวาง
ต้องเตรียมก่อน
คุณใช้แอปไหน
เลือกแอปด้านบน เราจำไว้ให้ ครั้งหน้าปุ่มจะขึ้นว่า “ติดตั้งลง …”
ใช้ได้ทั้ง Claude บนเว็บ แอปคอมพิวเตอร์ และมือถือ:
https://contract.sallim.app/mcp?via=officialพิมพ์คำสั่งนี้ใน Terminal
claude mcp add --transport http contract-compass 'https://contract.sallim.app/mcp?via=official'วางในไฟล์ .cursor/mcp.json ของโปรเจกต์ หรือ ~/.cursor/mcp.json
{
"mcpServers": {
"contract-compass": {
"url": "https://contract.sallim.app/mcp?via=official"
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
วางในไฟล์ .vscode/mcp.json ของโปรเจกต์
{
"servers": {
"contract-compass": {
"type": "http",
"url": "https://contract.sallim.app/mcp?via=official"
}
}
}เบราว์เซอร์จะถามก่อนเปิดแอป จากนั้นแอปแสดงค่าตั้งให้ตรวจแล้วกดยืนยัน ช่อง key เว้นว่างไว้ให้คุณใส่เอง
ChatGPT ต่อได้เฉพาะ server ที่อยู่บนอินเทอร์เน็ต:
https://contract.sallim.app/mcp?via=officialชื่อเมนูอาจต่างกันเล็กน้อยตามแพ็กเกจและรุ่นของแอป
ตัวเลือกเก็บในคุกกี้บนเครื่องนี้ ไม่ต้องมีบัญชี
ค่าตั้งนี้สร้างจากข้อมูลใน registry ของผู้ทำ ถ้าไม่ตรงกับ README ให้เชื่อ README
ชื่อและคำอธิบายเครื่องมือตามที่ server ตอบมาเมื่อ 6 พ.ย. 2569 ผู้ทำเป็นคนเขียน ไม่ใช่เรา แสดงเป็นข้อความล้วน
decide_contract_method계약방법 결정론 판정 — 룰엔진이 적용 가능한 계약방법 후보와 법령 근거를 반환. 상대방 지위(소기업·여성기업 등)를 안 넣었는데 그 지위로만 열리는 수의 후보가 있으면 `vendor_conditional_candidates`로 따로 온다 — 지위를 추정하지 말고 사용자에게 확인하라. `law_currency`는 이 판정이 기대는 법령(공기업이면 계약사무규칙 포함 — `laws_checked`)의 현행 여부다(2026-10-15). `status`가 "verified"가 아니면 `note_curr
search_law법령 조문 검색 — 키워드 또는 조문번호로 조문 스니펫 반환(상위 top_k건). **법령(법률·시행령·시행규칙·별표)만 본다 — 계약예규는 여기 없다.** 공사계약일반조건·정부 입찰·계약 집행기준·예정가격작성기준·용역계약일반조건 같은 예규는 search_references에 있다. 설계변경·물가변동· 기성·준공·지체·계약보증처럼 **계약 집행 실무 질문은 정답의 과반이 예규다**(실측 2026-11-01: 조달청 실무자 질의 306건 중 52%가 예규만 인용) — 그런 질문은 search_ref
search_references공공계약 코퍼스 통합 검색 — 법령+계약예규+조달청·행안부 세부기준+실무가이드. LLM 미사용. search_law가 법령 조문 전용인 것과 달리 예규·적격심사 세부기준·실무가이드까지 검색한다. 낙찰하한율·적격심사 배점·실무 절차 등 법령 본문 밖 질문에 사용하라. AI 생성 없이 검색 근거 원문만 반환한다(백엔드 LLM 예산 미차감). 국가·지방 자료를 함께 찾는다. 질의에 지방·지자체 표시가 없을 때 지방 자료(지방계약법령·지자체 예규)를 빼도록 설정된 배포에서는 뺀 수를 `local_excl
search_cases판례·법령해석례 검색 — law.go.kr 실시간 조회(항상 현행). LLM 미사용. 분쟁·처분취소·해석 다툼("~해도 되나", "~취소될 수 있나")에 조문만으로 부족할 때 쓰라. 본문은 get_case(kind, case_id)로 이어서 조회. **응답은 무엇으로 몇 건을 봤는지까지 말한다**(2026-08-29). `search_scope`가 "title"이면 사건명·안건명만, "body"면 본문까지 본 것이다. `searched`에 시도한 질의·범위·law.go.kr 총계(`total_cn
get_case판례/해석례 본문 조회 — 판시사항·판결요지·참조조문(판례) 또는 질의요지·회답·이유(해석례). 응답의 `source_url`은 국가법령정보센터 원문 주소다 — 판례·해석례를 인용할 때는 **이 링크를 함께 제시하라**(감사·보고서에서 근거를 되짚을 수 있어야 한다). **`error:"case_body_unavailable"`이면 `source_url`은 null이고 `existence_verified`는 false다**(2026-09-04). 이건 "본문만 없다"가 아니다 — 우리는 ①본문 미
get_law_article법령 조문 원문 조회 — 6,000자를 넘으면 잘라서 주고 `truncated`로 공시한다. **긴 조문은 잘린다(2026-10-15).** 원문이 6,000자를 넘으면 `truncated: true`와 `content_total_chars`(원문 총 글자수)·`content_shown_chars`·`paragraphs_shown`· `paragraphs_omitted`·`paragraph_cut`·`truncation_note`가 온다. 그때 content는 조문 전체가 아니다 — 생략된 항을
get_law_article_asof**특정 시점에 시행 중이던** 조문 원문 조회 (law.go.kr 연혁 라이브). get_law_article은 항상 현행이다. 과거 사건에 현행 조문을 적용하면 조용히 틀린 답이 된다 — 계약 체결·입찰공고·처분 시점이 과거이면 **반드시 이 도구를 쓰라**: - "2023년에 체결한 계약인데 지체상금률이 맞나" - "재작년 부정당업자 제재가 당시 기준으로 적법했나" - 감사·분쟁·소송 대응(적용법령은 행위시법이 원칙) 응답 필드: effective_date 그 시점에 시행 중이던 판의 시행일
estimate_delay_penalty지체상금(국가·공기업)·지연배상금(지방) 산정 — 법정 요율·기준금액·30% 한도를 결정론 적용. **국가와 지방은 요율이 다르다**(물품 0.75/1000 ↔ 0.8/1000, 용역 1.25/1000 ↔ 1.3/1000) — org_type을 반드시 사용자에게 확인해서 넣어라. 법정 용어도 다르다(국가=지체상금, 지방=지연배상금). **이 도구는 지체일수를 정하지 않는다.** 준공검사 소요기간·검사 불합격 재검사 기간· 발주기관 귀책 일수 같은 것은 사실 판단이다 — delay_days/excl
delay_exemption_guide지체일수에서 **빼는(불산입) 사유** 지도 — estimate_delay_penalty가 정하지 않는 부분. "이 지연은 우리 책임이 아닌데 지체상금을 물어야 하나", "동절기 공사중지 기간도 지체일수인가", "관급자재가 늦게 와서 늦어졌다" 같은 질문에 쓰라. **이 도구는 해당 여부를 판정하지 않는다.** 일반조건 문언 자체가 "계약담당공무원이 인정할 때"를 요건으로 두므로 판단은 발주기관 몫이다. 도구가 주는 것은 셋이다 — ①예규에 있는 사유 목록과 원문 인용 ②각 사유가 인정되려면 **
check_price_adjustment물가변동 계약금액 조정(에스컬레이션) 요건 판정 + 산식 적용 — 이행단계 Phase 3. "자재값이 올랐는데 계약금액을 올려받을 수 있나", "90일 지났나", "단품 조정 되나"에 쓰라. **이 도구는 조정률을 산정하지 못한다.** 품목조정률·지수조정률은 산출내역서와 지수·단가 원천(한국은행 생산자물가지수 등)으로 계산하는 값인데 이 서버는 그 데이터를 갖고 있지 않다 — 그러니 `adjustment_rate_pct`는 **사용자·발주기관이 산정한 값**을 받아 쓰고, 안 주면 요건 ②를 `m
report_issue사용자가 **오류 제보·개선 요청·문의를 운영자에게 전해 달라고 했을 때만** 쓴다. 쓰는 때: 사용자가 "이 조문 인용이 틀렸으니 신고해 줘", "운영자에게 알려 줘", "이런 질문도 답하게 해 달라고 전해 줘"처럼 제보·요청을 부탁했을 때. 보내기 전에 무엇이 전달되는지 사용자에게 알린다. 사용자가 오류·불만·개선 희망·기관 도입 같은 이용 문의·후원 의사를 말했지만 전달을 부탁하지는 않았다면, 부르지 말고 "운영자에게 전해 드릴까요?"를 한 줄로 물어 동의할 때만 부른다(거절·무반응이면 다시
เราตรวจจากข้อมูลที่ใครก็เปิดดูได้ ยังไม่ได้อ่านโค้ด ข้อที่ไม่เกี่ยวกับตัวนี้ไม่นับในตัวหาร · ตรวจเมื่อ 6 พ.ย. 2569
ชื่อใน registry ยืนยันโดเมน sallim.app แล้ว (registry ตรวจความเป็นเจ้าของโดเมน)
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ยังไม่ได้อ่านข้อมูล repo จาก GitHub
ตอบกลับใน 518 ms (HTTP 200)
ไม่ต้องล็อกอิน
อ่านคำอธิบายเครื่องมือ 11 ตัวแล้ว ไม่พบคำสั่งแอบแฝงถึง AI
เทียบกับทุก server ที่ยังใช้งานในหมวดนี้ทั้งทะเบียน ดาวนับเฉพาะเมื่อผู้ลงทะเบียนเป็นเจ้าของ repo
จากการตรวจเบื้องต้นของเรา ผ่าน 3 จาก 3 ข้อที่ตรวจได้ เรายังไม่ได้อ่านโค้ด ก่อนใส่กุญแจหรือ token ให้ดูว่า server ขอสิทธิ์อะไร และเลือกกุญแจที่ทำได้เท่าที่จำเป็น
registry ไม่ได้ระบุว่าต้องใช้กุญแจ แต่บางตัวจะขอให้ล็อกอินตอนใช้ครั้งแรก
รันบนคลาวด์ของผู้ทำ ต่อผ่านอินเทอร์เน็ตได้เลย ไม่ต้องลงโปรแกรม แต่ข้อมูลที่ส่งให้จะผ่านเซิร์ฟเวอร์ของผู้ทำ
repo บน GitHub มีการแก้โค้ดล่าสุด – และส่งรุ่นล่าสุด (1.85.0) เข้า registry วันนี้
โปรแกรมที่รองรับ MCP เช่น Claude Desktop, Claude Code, Cursor และ VS Code ตัวนี้ต่อผ่าน URL จึงใช้กับโปรแกรมที่รับ remote MCP ได้ เช่น ChatGPT ที่เปิดโหมดนักพัฒนา
ในหมวดเดียวกันมี Context7, Codebase Memory, Exa
server หมวดเดียวกันจากผู้ทำคนอื่น เรียงตามดาว
อ่านการ์ด:★ ดาว GitHubiสามเสา: รีวิว · ผลตรวจ · การใช้งานiอัปเดต = วันที่ส่งรุ่นล่าสุดเข้า registryi
ส่งคู่มือการใช้ไลบรารีและเฟรมเวิร์กรุ่นล่าสุดให้ AI อ่านก่อนตอบ ช่วยให้โค้ดที่ AI เขียนไม่ใช้คำสั่งเก่าที่เลิกใช้แล้ว
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
ส่วนนี้คัดจาก repo ของผู้ทำตามต้นฉบับ PopNx MCP ไม่ได้ตรวจหรือรับรองเนื้อหา ตัด HTML รูปภาพ และสคริปต์ออกแล้ว ลิงก์จะพาออกนอกเว็บ
Korean public procurement law MCP server & web service — a deterministic rule
engine for contract-method decisions (94 rules encoded directly from statutes), a
searchable corpus of Korean procurement statutes/regulations/adjudication tables,
and live court precedents & authoritative interpretations from law.go.kr.
All MCP tools are LLM-free: your AI client does the reasoning, this server
provides verifiable legal grounds. Remote endpoint:
https://contract.sallim.app/mcp
공공계약 방법 결정 도우미 — 국가계약법·지방계약법 등 공공계약 법령을 기반으로, 발주하려는 계약(공사·용역·물품)에 적용 가능한 계약방법(입찰·수의계약·제한경쟁 등)과 법령 근거를 결정론적으로 안내하는 오픈소스 웹서비스 + MCP 서버입니다.
⚠️ 면책: 이 서비스는 정보 제공 목적이며 법적 자문·유권해석이 아닙니다.
적격심사 통과점수·낙찰하한율·각종 한도는 발주기관별 세부기준과 법령 개정에 따라
다를 수 있으므로, 실제 발주 전 반드시 소속 기관 계약 부서와 현행 법령을 확인하세요.
원격 엔드포인트(Streamable HTTP): `https://contract.sallim.app/mcp` 무료: IP당 50콜/일 (전 도구) · 유료 키: 한도 상향 — 요금 안내
아래 표는 라이브 서버의 `tools/list` 응답에서 그대로 뽑은 것입니다(실측 2026-08-18, 11종 전수). MCP 디렉토리·크롤러가 이 저장소를 정적으로 읽을 때 도구 이름을 찾는 자리이므로, 서버의 실제 도구 목록과 1:1로 유지합니다(불일치는 회귀로 취급). 누구나 직접 재현할 수 있습니다:
curl -s -X POST https://contract.sallim.app/mcp \
-H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
| 도구 | 설명 | LLM |
|---|---|---|
decide_contract_method | 룰엔진 결정론 판정 — 계약방법 후보·법령 근거·적격심사 파라미터 | ✗ |
search_law | 법령 조문 검색(키워드·조문번호·부분매치·시맨틱 폴백) | ✗ |
get_law_article | 조문 원문 전체 조회 (현행) — 법률 자체의 미정비 인용은 notes로 경고 | ✗ |
get_law_article_asof | 특정 시점에 시행 중이던 조문 — 과거 계약·처분·감사 대응(행위시법) | ✗ |
search_references | 전 코퍼스 통합 검색 — 계약예규·조달청/행안부 적격심사 세부기준(별표)·실무가이드 | ✗ |
search_cases | 판례·법령해석례 검색 (law.go.kr 실시간 — 항상 현행) | ✗ |
get_case | 판시사항·판결요지·참조조문 / 질의요지·회답·이유 본문 | ✗ |
estimate_delay_penalty | 지체상금·지연배상금 산정 — 법정 요율·기준금액·30% 한도 결정론 적용(국가/지방 요율이 다르다) | ✗ |
delay_exemption_guide | 지체일수 불산입(면책) 사유 지도 — 예규 사유·확인할 사실·기재부/행안부 회신 선례 | ✗ |
check_price_adjustment | 물가변동 계약금액 조정 — 90일·3%·단품 문턱(국가 15%/지방 10%) 판정 + 조정금액·선금공제 산식 | ✗ |
report_issue | 오류·개선 제보(오인용·개정 미반영 등) — 운영 검토 파이프라인 직결 | ✗ |
클라이언트 설정:
# Claude Code
claude mcp add --transport http contract-compass https://contract.sallim.app/mcp
// Cursor (.cursor/mcp.json) — Streamable HTTP 직접 지원
{ "mcpServers": { "contract-compass": { "url": "https://contract.sallim.app/mcp" } } }
// Claude Desktop (claude_desktop_config.json) — mcp-remote 경유
{ "mcpServers": { "contract-compass": { "command": "npx", "args": ["-y", "mcp-remote", "https://contract.sallim.app/mcp"] } } }
ChatGPT: Settings → Connectors → Developer mode에서 위 URL을 커넥터로 추가.
설치했으면 AI에게 이렇게 물어 30초 안에 확인하세요 — *"국가기관이 2,000만원짜리 물품을 사려는데 어떤 계약방법을 쓸 수 있어? 근거 조문도."* 소액수의계약과 국가계약법 시행령 제26조 제1항 제5호가 나오면 정상입니다.
도구 명세·아키텍처·한도 정책 상세는 docs/MCP.md 참조.
이 서버가 무엇을 맞히고 무엇을 못 맞히는지는 evaluation.xml에 공개돼 있습니다(20문항, 답은 전부 실측값). 지어낸 문항은 없습니다 — 미검증 문항은 회귀 검사를 거짓 실패시키기 때문입니다.
기계 검증은 결정론 회귀 하네스가 합니다. LLM을 쓰지 않아 비용 없이 재현됩니다:
python3 tools/mcp_regression.py --endpoint https://contract.sallim.app/mcp
각 케이스는 과거에 실제로 발견·수리된 결함의 회귀입니다(삭제된 조문을 근거처럼 반환하던 문제, 지자체 판정에 국가 수치가 섞이던 문제 등). 무료 티어는 IP당 50콜/일이고 이 스위트가 28콜을 쓰므로 하루 1회가 한계입니다.
금액구간별 계약방법·수의계약 사유·용어 가이드 페이지(/g/)의 생성·검증·배포 절차는 docs/PROGRAMMATIC_SEO.md 참조 — 룰셋에서 파생 생성하므로 페이지를 수기 편집하지 말 것. 로컬 stdio 실행: python3 mcp/server.py (등록: codex mcp add contract-compass -- python3 /path/to/mcp/server.py)
backend/ FastAPI — 룰엔진·RAG·LLM 연동 (frontend/dist 정적 서빙 포함, :8402)
frontend/ React + TypeScript (Vite) — 위저드 UI mcp/ MCP 서버 — stdio(로컬) / Streamable HTTP(:8403, 원격) · 무LLM 도구 11종 edge/ Cloudflare Worker (contract-edge) — 장애 폴백 게이트 · law API 엣지 캐시 rules/ 계약 룰셋 JSON (contract_rules·law_registry 등) ← 결정론 핵심 tools/ 법령·예규·별표 수집/인덱싱 파이프라인 (law.go.kr Open API) · 가이드 페이지 생성기 etl/ PDF/DOCX → 청크 → ChromaDB 파이프라인 docs/ MCP 명세 · 장애 전환 런북 · 가이드 페이지 파이프라인 scripts/ 스탠바이 동기화 · 반출 전 기밀 검사 tests/ 단위·회귀 테스트 + Ask 질문뱅크
# 1) 백엔드 의존성 (+ MCP 서버까지 쓰려면 mcp/requirements.txt 추가)
pip install -r backend/requirements.txt
cd frontend && npm install && npm run build && cd ..
cp .env.example .env
python3 -m uvicorn backend.main:app --host 0.0.0.0 --port 8402
법령 챗봇·근거 검색을 쓰려면 공개 코퍼스를 인덱싱합니다:
# 법령 XML을 tools/laws/ 에 준비(law.go.kr Open API — tools/lib/lawgo.py 헬퍼 참조) 후 인덱싱
python3 tools/index_laws.py # → law_articles 컬렉션
python3 tools/fetch_admin_rules.py && python3 tools/parse_admin_rules.py python3 tools/index_admin_rules.py # → admin_rules 컬렉션
python3 tools/fetch_law_tables.py
python3 tools/reindex_qa.py # → public_guides 컬렉션
python3 tools/build_bm25_index.py
코퍼스가 없으면 위저드(룰엔진)는 정상 동작하고, RAG 검색 결과만 비어 있습니다. 판례·법령해석례 조회는 코퍼스와 무관하게 law.go.kr Open API 키(LAW_API_KEY)만 있으면 동작합니다.
MIT