mcpbeat Sign in

MyKIFRS MCP Server

answering

MyKIFRS is answering right now. Last checked 9 min ago. It exposes 7 tools.

Full-text search over K-IFRS/K-GAAP standards, Q&A and KASB/KICPA material for Korean accountants

Uptime history 56 days of history · worst day 99%
56 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
542 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 41

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 September 2026. No other catalogue keeps this.

27 Oct 5 tool descriptions were rewritten10 times that day get_material, list_standards, search_materials and 2 more
27 Oct 4 tools changed the parameters they ask for5 times that day get_material, search_materials, search_qnas and 1 more
27 Oct a tool changed version3 times that day
25 Oct 2 tools appeared get_material, search_materials
25 Oct 2 tool descriptions were rewritten list_standards, search_qnas
25 Oct a tool changed version2 times that day
23 Oct 5 tools changed the parameters they ask for get_paragraph, get_qna, list_standards and 2 more
23 Oct a tool changed version2 times that day
16 Oct a tool disappeared get_usage_stats
16 Oct a tool changed version
and 18 more, back to 15 September 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add mykifrs --transport http https://mykifrs.eocpa.kr/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mykifrs.eocpa.kr/mcp
~/.codex/config.toml
[mcp_servers.mykifrs]
url = "https://mykifrs.eocpa.kr/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mykifrs": {
      "url": "https://mykifrs.eocpa.kr/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mykifrs": {
      "type": "http",
      "url": "https://mykifrs.eocpa.kr/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

standards
list_standards
MyKIFRS MCP의 list_standards 도구는 수록된 기준서 카탈로그를 반환합니다. [Purpose] - Which 기준서 are in the corpus, and which numbers feed search_standards' std_num filter. [Usage] 1. "수록된 기준서 전부" → (인자 없음) 2. "감사기준서만" → category="audit" 3. "내부회계관리제도 관련" → category="icfr" [Response] - { count, standards:[{std_num, title, category}] } - category values: kifrs(한국채택국제회계기준) · interpretation(해석서) · concept(재무보고를 위한 개념체계) · translation(번역본) · kgaap(일반기업회계기준) · special(특수분야) · audit(감사기준서) · icfr(내부회계관리제도) · sme(중소기업회계기준) · nonprofit(비영리조직회계기준) · assurance(검토·인증업무 기준(목록만)) · other(기업회계기준 전문·적용의견서·회계감사실무지침·행동강령). [Rules] - Lists 수집 성공(crawl_status='ok') 기준서 only — an absent 기준서 means "미수집", not "존재하지 않음". - 감사인증·윤리기준 (검토·인증·품질관리 등)과 고시 원문 are outside this catalog — search_standards category="assure"·"ext_std". - category is a free-form string, not an enum: an unknown value returns count=0, not an error.
search_standards
MyKIFRS MCP의 search_standards 도구는 기준서 문단과 감사인증·윤리기준·고시 원문을 한 목록으로 전문검색합니다. [Purpose] - The 기준 grounding a treatment ("사용권자산 손상 is which 문단?"): 기준서 문단 (K-IFRS·일반기업·감사·내부회계· 중소·비영리) plus 감사인증·윤리기준 and 고시 원문 (공익법인·집합건물 회계처리기준 등). [Usage] 1. "사용권자산 손상 관련 기준" → query="사용권자산 손상" 2. "일반기업회계기준에서 리스 분류" → query="리스 분류", category="kgaap" 3. "1116호 안에서만 리스료 재측정" → query="리스료 재측정", std_num=1116 [Response] - { hits, results } by relevance; a matched assure·ext_std keeps ≥1 slot (limit ≥3). - kind "paragraph" {std_num, std_title, category, unique_key ("1116-33"·"1109-6.1.1"), snippet} → get_paragraph; kind "assure"·"ext_std" {material_key, category, date, title, snippet} → get_material. - Empty query → { error: "검색어가 비어 있음" }. [Rules] - One 쟁점 differs by family (K-IFRS vs 일반기업회계기준 vs 중소기업) — confirm category·std_title fits the entity before citing; narrow with category. - Tokens ≥3 chars → FTS (AND, rank); 1~2 → LIKE. 제목 rows excluded. - snippet (⟦…⟧ marks) is a fragment — quote get_paragraph/get_material text.
material
get_material
MyKIFRS MCP의 get_material 도구는 회계기준원·공인회계사회 자료와 외부 기관 고시의 전문(상세 본문과 첨부 파싱 본문)을 반환합니다. [Purpose] - Full text of one material_key (search_materials; search_standards kind assure·ext_std; search_qnas kind tf·qc). [Usage] 1. "tf:40689 전문" → material_key="tf:40689" 2. "길어서 잘렸는데 이어서" → material_key="tf:40689", offset_chars=60000 [Response] - { material_key, board, category, date, title, url, files:[{name, parsed}], body_total_chars, offset_chars, truncated, body } - body = 상세 본문 + 첨부마다 "[첨부] 파일명" 머리를 단 파싱 본문. A 첨부 opening "(이미지 PDF — OCR 전사본" was OCR-read — verify figures against url. - files[].parsed=false → 첨부 not extracted (zip·pptx 등) — point the user to url. - Miss → { error: "material_key 없음: …" } or { error: "material_key 형식 오류: …" }. [Rules] - truncated=true means offset_chars+max_chars < body_total_chars — raise offset_chars to continue; raising max_chars grows the whole response. - board: search_materials' board legend, plus tf 정착지원TF · qc 품질관리실장 회의 · assure 감사인증·윤리기준 · ext_std 고시 원문.
materials
search_materials
MyKIFRS MCP의 search_materials 도구는 회계기준원·공인회계사회의 보조 자료(질의회신 교육자료·공개초안·IASB 동향·연구보고서·협의회 사례·가치평가 자료 등)를 전문검색합니다. [Purpose] - Supporting (2-tier) material: 질의회신 교육·정비목록, 공개초안·IFRS 검토의견·제·개정 공표, IASB 동향, 연구보고서, 세미나·KAI Forum, 제정개정과제, KICPA 전·당기 협의회 사례, 가치평가 자료실 (위험 프리미엄·IVS). - 1-tier is in the core tools: 기준서·감사인증·윤리기준·고시 원문 → search_standards; 회신·정착지원TF·품질관리실장 회의 → search_qnas. [Usage] 1. "1028호 공정가치선택권 공개초안" → query="공정가치선택권", board="ed" 2. "2025 질의회신 교육 리스" → query="리스", board="edu" 3. "시장위험 프리미엄" → query="시장위험 프리미엄", board="valuation" [Response] - { hits, results:[{material_key, board, category, date, title, snippet}] } - board codes: listed in the board parameter's description. date null = 과제 페이지. [Rules] - Tokens ≥3 chars → FTS (AND, rank); 1~2 chars → LIKE (newest first). - Supporting only, never 회신 — where it conflicts with 기준서·회신·1-tier, follow those. - Read the full text with get_material(material_key).
paragraph
get_paragraph
MyKIFRS MCP의 get_paragraph 도구는 기준서 문단 전문을 앞뒤 문맥과 함께 반환합니다. [Purpose] - To quote a found 문단 exactly — a search snippet is never quotable evidence. - To check 조건절·예외 with neighbors. [Usage] 1. "1116호 33문단 원문" → unique_key="1116-33" 2. "앞뒤로 더 넓게" → unique_key="1116-33", context=5 [Response] - { standard:{std_num, title, category}, target, related_qnas:[doc_number], items:[…] } - items[]: { seq, item_type, unique_key, para_num, level, title, ref, content_text }; item_type "paragraph"=본문, "title"=제목. - related_qnas → get_qna. - Miss → { error: "문단 없음: {unique_key}", similar:[{unique_key, para_num}] } (≤5). [Rules] - unique_key = "{기준서번호}-{문단번호}"; 문단 numbers aren't digits-only (B58·6.1.1) — pass verbatim, never normalize. - Keys can carry a "-N" suffix ("1109-B2.7" misses, "1109-B2.7-1" hits — 12% of 문단). On a miss retry a `similar` candidate; never read it as "the 문단 does not exist". - context expands within one part — boundaries return fewer items; not an error. - Quote content_text, never a snippet.
qna
get_qna
MyKIFRS MCP의 get_qna 도구는 질의회신 전문을 반환합니다. [Purpose] - The 회신 full text for a doc_number (search_qnas, get_paragraph's related_qnas) or a qna_key (search_qnas). [Usage] 1. "2017-001 회신 전문" → doc_number="2017-001" 2. "legacy:6009 전문" → qna_key="legacy:6009" [Response] - { results:[{source, qna_key, doc_number, date, title, rel_stds, full_content, org}] } - Miss → { error: "문서번호 없음: {doc_number}", similar:[{source, qna_key, doc_number, title}] } (≤5 부분일치) or { error: "qna_key 없음: {qna_key}" }. - source / org / rel_stds: same meaning as in search_qnas. [Rules] - results is an array; doc_number is NOT unique ("GKQA03-100" → 2 rows). Never answer from the first row alone — pin one by qna_key. - qna_key = "{source}:{id}" exactly as returned; if both arguments are given, qna_key wins. - 번호 formats differ by series ("2021-G-KQA005" · "GKQA01-085" · "금감원사례-1") — pass the value as received, never alter case or separators. - On a miss, re-ask using `similar` rather than guessing another 번호.
qnas
search_qnas
MyKIFRS MCP의 search_qnas 도구는 질의회신과 정착지원TF·품질관리실장 회의자료를 한 목록으로 전문검색합니다. [Purpose] - 회신 and KASB 실무 해석 (정착지원TF·품질관리실장 회의) for issues the 기준서 alone cannot settle. - 문단-linked 회신 → get_paragraph related_qnas. [Usage] 1. "전환사채 콜옵션 회계처리 질의회신" → query="전환사채 콜옵션" 2. "1118호 영업손익 TF 논의까지 30건" → query="영업손익", limit=30 [Response] - { hits, results } by relevance; matched tf·qc keep ≥3 slots (≤limit/3). kind "qna" = 회신 {source, qna_key, doc_number, date, title, rel_stds, org, snippet} → get_qna; kind "tf"·"qc" = 정착지원TF·품질관리실장 회의 {material_key, category, date, title, snippet} → get_material. - org = 회신 기관 (회계기준원·금융감독원·신속처리질의·IFRS 해석위원회 논의결과·구 QnA); source = 수록 세대 (v2·legacy), never the 기관. - rel_stds is HTML — data-std + data-id → unique_key ("1109-6.1.1"). [Rules] - Tokens ≥3 chars → FTS (AND, rank); 1~2 chars → LIKE (회신 first). - kind tf·qc are 논의·회의 요약, not 회신 — never cite them as 질의회신. - qna_key pins one 회신 when doc_number is "" or duplicated. legacy 회신 (mostly 2000~2011, 구 기업회계기준) — check date.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_usage_stats
removed 16 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://mykifrs.eocpa.kr/mcp streamable-http answering 379 ms 9 min ago

Alternatives to MyKIFRS

same job, measured the same way
M
MyFSS
by eocpa

Full-text search over FSS/FSC accounting supervision documents for Korean accounting professionals

4 tools answering
Mem.Center
by mem

Read-only memory search and task context for AI clients. Requires a Mem.Center Pro account.

answering
Groupdocs Search MCP
by groupdocs-search

MCP server for GroupDocs.Search — index documents and run full-text search via AI agents.

local only
Lupa — local file search for your Mac
by under71

Search your Mac's files by name and by text inside documents. Local index, Korean-aware.

246 installs/wk local only
Lupa — local file search for your Mac
by paeyoungpark-web

Search your Mac's files by name and by text inside documents. Local index, Korean-aware.

local only
Limps
by paulbreuler

MCP planning server for AI agents — plan management, full-text search, and task lifecycle

173 installs/wk local only
SOAR Record Gateway
by lateos

SOAR security playbooks for AI agents: fetch, full-text search, and count. Metered via Stripe.

answering
Dreamwork
by dreamworkhq

Job search, application materials, and application tracking for AI assistants.

894 installs/wk 71 tools answering

MyKIFRS — questions

Answers built from our own checks of this server.

What can MyKIFRS do?
It exposes 7 tools, read directly from the server on our last check. Among them: get_material, get_paragraph, get_qna, list_standards, search_materials, search_qnas and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is MyKIFRS working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 542 ms. The bar chart above shows every period we have measured.
Did MyKIFRS ever remove tools?
Yes. get_usage_stats is no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect MyKIFRS?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does MyKIFRS need an API key?
No. MyKIFRS completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is MyKIFRS?
It answers our handshake in 542 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.