Skip to content

MyKIFRS MCP server

kr.eocpa/mykifrseocpa.krstreamable-httpv0.20.2Scanned

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

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the MyKIFRS MCP server can do

The MyKIFRS MCP server is published by eocpa.kr, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.20.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • get_materialMyKIFRS MCP의 get_material 도구는 회계기준원·공인회계사회 자료와 외부 기관 고시의 전문(상세 본문과 첨부 파싱 본문)을 반환합니다.No findings

    Why it is in this group

    • The name "get_material" says "get": a word for reading.
    Description, as the server wrote it
    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 고시 원문.

    Annotations the server declares

    • title: 회계기준원·공인회계사회 자료 전문
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_paragraphMyKIFRS MCP의 get_paragraph 도구는 기준서 문단 전문을 앞뒤 문맥과 함께 반환합니다.No findings

    Why it is in this group

    • The name "get_paragraph" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: 기준서 문단 원문
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_qnaMyKIFRS MCP의 get_qna 도구는 질의회신 전문을 반환합니다.No findings

    Why it is in this group

    • The name "get_qna" says "get": a word for reading.
    Description, as the server wrote it
    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, url, 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 번호.

    Annotations the server declares

    • title: 질의회신 전문
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_standardsMyKIFRS MCP의 list_standards 도구는 수록된 기준서 카탈로그를 반환합니다.No findings

    Why it is in this group

    • The name "list_standards" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: 수록 기준서 카탈로그
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_materialsMyKIFRS MCP의 search_materials 도구는 회계기준원·공인회계사회의 보조 자료(공개초안·제·개정 공표·제정개정과제·협의회 사례·가치평가 자료 등)를 전문검색합니다.No findings

    Why it is in this group

    • The name "search_materials" says "search": a word for reading.
    Description, as the server wrote it
    MyKIFRS MCP의 search_materials 도구는 회계기준원·공인회계사회의 보조 자료(공개초안·제·개정 공표·제정개정과제·협의회 사례·가치평가 자료 등)를 전문검색합니다. [Purpose] - Supporting (2-tier) material: 질의회신 정비목록, 공개초안·제·개정 공표, K-IFRS 주요용어, 제정개정과제, KICPA 전·당기 협의회 사례, 가치평가 자료실 (위험 프리미엄·IVS). - 1-tier is in the core tools: 기준서·감사인증·윤리기준·고시 원문 → search_standards; 회신·정착지원TF·품질관리실장 회의 → search_qnas. [Usage] 1. "1028호 공정가치선택권 공개초안" → query="공정가치선택권", board="ed" 2. "위험회피회계 사후이행검토 과제" → query="위험회피회계", board="project" 3. "시장위험 프리미엄" → query="시장위험 프리미엄", board="valuation" [Response] - { hits, results:[{material_key, board, category, date, title, url, snippet}] } - board codes: listed in the board parameter's description. date null = 과제 페이지. url = 원문 page. [Rules] - Tokens ≥3 chars → FTS (AND, rank). All 1~2 chars → the joined/spaced phrase first ("리스변경"·"리스 변경"), else LIKE (AND, newest first). - Supporting only, never 회신 — where it conflicts with 기준서·회신·1-tier, follow those. - Read the full text with get_material(material_key).

    Annotations the server declares

    • title: 회계기준원·공인회계사회 보조 자료 검색
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_qnasMyKIFRS MCP의 search_qnas 도구는 질의회신과 정착지원TF·품질관리실장 회의자료를 한 목록으로 전문검색합니다.No findings

    Why it is in this group

    • The name "search_qnas" says "search": a word for reading.
    Description, as the server wrote it
    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, url, date, title, rel_stds, org, snippet} → get_qna; kind "tf"·"qc" = 정착지원TF·품질관리실장 회의 {material_key, category, date, title, url, 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] - Every token must appear (substring, in 제목 or 본문); 제목 hits 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.

    Annotations the server declares

    • title: 질의회신·실무 해석 전문검색
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_standardsMyKIFRS MCP의 search_standards 도구는 기준서 문단과 감사인증·윤리기준·고시 원문을 한 목록으로 전문검색합니다.No findings

    Why it is in this group

    • The name "search_standards" says "search": a word for reading.
    Description, as the server wrote it
    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"), url, snippet} → get_paragraph; kind "assure"·"ext_std" {material_key, category, date, title, url, snippet} → get_material. [Rules] - One 쟁점 differs by family (K-IFRS vs 일반기업회계기준 vs 중소기업) — confirm category·std_title fits the entity before citing; narrow with category. - Every token must appear (substring, in 본문 or 섹션 제목). 섹션 제목 hits and 본문 outrank 결론도출근거·적용사례. - snippet (⟦…⟧ marks) is a fragment — quote get_paragraph/get_material text.

    Annotations the server declares

    • title: 기준서·기준 원문 전문검색
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:23 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff
  2. Tools1 changed.~1 changedView diff
  3. Tools2 added, 3 changed.+2 added~3 changedView diff
  4. Tools5 changed.~5 changedView diff

Install

Pinned to version 0.20.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http mykifrs https://mykifrs.eocpa.kr/mcp --header 'x-eocpa-token: <your-x-eocpa-token>'
claude mcp add --transport http mykifrs https://mykifrs.eocpa.kr/mcp --header 'x-eocpa-token: <your-x-eocpa-token>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__mykifrs__search_standards",
      "mcp__mykifrs__search_qnas",
      "mcp__mykifrs__get_paragraph",
      "mcp__mykifrs__get_qna",
      "mcp__mykifrs__list_standards",
      "mcp__mykifrs__search_materials",
      "mcp__mykifrs__get_material"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mykifrs. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/kr.eocpa/mykifrs/verify?hash=2c94c78d13d32c046cfa07611382722cc2e76788c4e05f0f4f53d072db463ee7" | jq -e '.changed == false'

Pinned hash 2c94c78d13d3, from Nov 20, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/kr.eocpa/mykifrs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for kr.eocpa/mykifrs
[![Anlyon Radar](https://radar.anlyon.com/badge/kr.eocpa/mykifrs.svg)](https://radar.anlyon.com/servers/kr.eocpa/mykifrs)

Source: MCP Registry. Synced Nov 20, 2026, 05:18 UTC.

MyKIFRS MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the MyKIFRS MCP server safe?

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the MyKIFRS MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the MyKIFRS MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MyKIFRS MCP server have?

7 tools: 7 read. search_standards, search_qnas, get_paragraph, get_qna, list_standards, search_materials and get_material.

Does the MyKIFRS MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MyKIFRS MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the MyKIFRS MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.