MyKIFRS
REMOTE · MYKIFRS.EOCPA.KR · SCANNED SEP 22
Full-text search over K-IFRS/K-GAAP standards and KASB accounting Q&A for Korean accountants
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2379 tokens (~396/item across 6 items; 6 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MyKIFRS MCP server?
MyKIFRS is a hosted endpoint at https://mykifrs.eocpa.kr/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 · mykifrs.eocpa.kr
claude mcp add --transport http kr-eocpa-mykifrs 'https://mykifrs.eocpa.kr/mcp'
{
"mcpServers": {
"kr-eocpa-mykifrs": {
"url": "https://mykifrs.eocpa.kr/mcp"
}
}
} {
"servers": {
"kr-eocpa-mykifrs": {
"type": "http",
"url": "https://mykifrs.eocpa.kr/mcp"
}
}
} [mcp_servers.kr-eocpa-mykifrs] url = "https://mykifrs.eocpa.kr/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kr-eocpa-mykifrs": {
"type": "remote",
"url": "https://mykifrs.eocpa.kr/mcp",
"enabled": true
}
}
} openclaw mcp add kr-eocpa-mykifrs --url 'https://mykifrs.eocpa.kr/mcp' --transport streamable-http
mcp_servers:
kr-eocpa-mykifrs:
url: "https://mykifrs.eocpa.kr/mcp" {
"McpServers": {
"kr-eocpa-mykifrs": {
"Transport": "http",
"Url": "https://mykifrs.eocpa.kr/mcp"
}
}
} assistant mcp add kr-eocpa-mykifrs -t streamable-http -u 'https://mykifrs.eocpa.kr/mcp'
{
"mcpServers": {
"kr-eocpa-mykifrs": {
"type": "http",
"url": "https://mykifrs.eocpa.kr/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- Tool “get_paragraph” rewrote its description, which is the text the model reads security
- Tool “get_qna” rewrote its description, which is the text the model reads security
- Tool “search_qnas” rewrote its description, which is the text the model reads security
- Server version: 0.11.1 → 0.11.2 functional
- Server version: 0.11.0 → 0.11.1 functional
- Server version: 0.10.1 → 0.11.0 functional
- “get_qna” added an optional parameter “qna_key” cosmetic
- “get_qna” reworded the description of “doc_number” cosmetic
- “get_qna” made “doc_number” optional cosmetic
- 13 Sept 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.
- 11 Sept 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.
- 9 Sept 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.
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 22 Sept 2026 · Probed https://mykifrs.eocpa.kr/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mykifrs.eocpa.kr | CN=YE1,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5b6c676caca0a5a70db7f77ca1ba3055576 |
| SANs: mykifrs.eocpa.kr | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mykifrs.eocpa.kr. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| kr. | present | 64641 | 13 | Verified |
| eocpa.kr. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mykifrs.eocpa.kr/mcp | Verified | 200 | |
| http (plaintext) | http://mykifrs.eocpa.kr/mcp | HTTPS enforced | 301 | https://mykifrs.eocpa.kr/mcp |
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 →
get_paragraph 기준서 문단 원문 ~393
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.
| Name | Type | Req | Description |
|---|---|---|---|
| context | number | – | 앞뒤로 포함할 항목 수 (기본 2) |
| unique_key | string | yes | 문단 키 (예: '1116-33') |
No output schema declared.
No examples provided.
get_qna 질의회신 전문 ~415
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 번호.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_number | string | – | 질의회신 문서번호 — qna_key 를 주지 않을 때 필수 |
| qna_key | string | – | 행 식별자 "{source}:{id}" (search_qnas 의 qna_key, 예: legacy:6009) — 번호가 비었거나 중복일 때 |
No output schema declared.
No examples provided.
get_usage_stats 사용량 통계 ~353
MyKIFRS MCP의 get_usage_stats 도구는 이 MCP 서버의 도구 사용량 통계를 반환합니다. [Purpose] - Per-tool usage·latency (avg/percentiles)·error rate·daily trend. [Usage] 1. "최근 30일 사용량" → (인자 없음) 2. "지난 7일만" → days=7 3. "전체 기간" → days=0 [Response] - Both tiers: { visibility, period:{days, since, until}, overview:{total_calls, unique_users, errors, error_rate, p50_ms, p90_ms, p99_ms}, by_tool:[{tool, calls, errors, error_rate, avg_ms, p99_ms, users}], by_day:[{day, calls}] } - visibility="public" adds `note`; period.days = "all" when days=0. - visibility="operator" adds users:[{user, is_owner, calls, distinct_tools, first_seen, last_seen, tools:[{tool, calls, avg_ms}]}] and top_targets:[{target, tool, calls, users}]. [Rules] - Tier by requester: admin token·local stdio → "operator", else "public". - users·top_targets exist only at operator tier — absence ≠ 0. - `user` is a truncated SHA-256 of the 접속 토큰 — not a person. stdio calls (no hash) never appear. - Timings = server-side handler time (no network).
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | 최근 N일 윈도 (0이면 전체 기간, 기본 30) |
No output schema declared.
No examples provided.
list_standards 수록 기준서 카탈로그 ~312
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(재무보고를 위한 개념체계) · kgaap(일반기업회계기준) · audit(감사기준서) · icfr(내부회계관리제도) · esg(KSSB 지속가능성 공시기준) · translation(번역본) · special(특수분야). [Rules] - Lists 수집 성공(crawl_status='ok') 기준서 only — an absent 기준서 means "미수집", not "존재하지 않음". - category is a free-form string, not an enum: an unknown value returns count=0, not an error.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 카테고리로 필터 (생략 시 전체) |
No output schema declared.
No examples provided.
search_qnas 질의회신 전문검색 ~456
MyKIFRS MCP의 search_qnas 도구는 회계기준원·금융감독원·신속처리질의·IFRS 해석위원회 질의회신 3,669건을 전문검색합니다. [Purpose] - Official 회신 for practice issues the 기준서 text alone cannot settle. - For 회신 tied to a 문단, get_paragraph's related_qnas is more precise. [Usage] 1. "전환사채 콜옵션 회계처리 질의회신" → query="전환사채 콜옵션" 2. "리스료 재측정 회신 30건" → query="리스료 재측정", limit=30 [Response] - { hits, results:[{source, qna_key, doc_number, date, title, rel_stds, org, snippet}] } - source = 수록 세대 ("v2" 현행 / "legacy" 구 QnA), NOT the 회신 기관. - org = 회신 기관: 회계기준원 / 금융감독원 / 신속처리질의 / IFRS 해석위원회 논의결과 ("구 QnA" = unmapped legacy 유형). - rel_stds is raw HTML: <span data-std="1109" data-id="6.1.1"> → unique_key "1109-6.1.1". [Rules] - Tokens ≥3 chars → FTS (AND, rank); 1~2 chars → LIKE. - Never present `source` as the 회신 기관 — use `org`. - Strip HTML in rel_stds; build 문단 키 from data-std/data-id. - qna_key ("{source}:{id}") is get_qna's single-row handle — use it when doc_number is "" or duplicated. legacy 회신 are mostly 2000~2011 (구 기업회계기준) — check `date` before citing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 최대 결과 수 (기본 10) |
| query | string | yes | 검색 키워드 (공백 구분) |
No output schema declared.
No examples provided.
search_standards 기준서 전문검색 ~450
MyKIFRS MCP의 search_standards 도구는 K-IFRS·일반기업회계기준·감사기준서·내부회계관리제도·ESG(KSSB) 기준서 본문을 전문검색합니다. [Purpose] - Find the 기준서 문단 grounding a treatment ("사용권자산 손상 is which 문단?"). - For a hit's 원문·문맥, pass its unique_key to get_paragraph. [Usage] 1. "사용권자산 손상 관련 기준" → query="사용권자산 손상" 2. "1116호 안에서만 리스료 재측정" → query="리스료 재측정", std_num=1116 3. "수익 인식 5단계 문단 30개까지" → query="수익 인식 단계", limit=30 [Response] - { hits, results:[{std_num, std_title, category, unique_key, snippet}] } - unique_key = "{std_num}-{문단번호}" (e.g. "1116-33", "1109-6.1.1", "2-2.7") — feed to get_paragraph. - snippet marks matches with ⟦…⟧ and elides with "…". - Empty query returns { error: "검색어가 비어 있음" }. [Rules] - Tokens of ≥3 chars go to FTS (AND-joined, rank-ordered); 1~2 char tokens become LIKE filters. Short-token-only queries work but are ordered by std_num, not relevance. - Body 문단 only (item_type='paragraph') — 제목 rows are excluded, so a hit is always body text. - snippet is a fragment, never the whole 문단 — do not quote it as 기준서 원문.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 최대 결과 수 (기본 10) |
| query | string | yes | 검색 키워드 (공백 구분) |
| std_num | number | – | 특정 기준서로 한정 (예: 1116) |
No output schema declared.
No examples provided.
What is the MyKIFRS MCP server?
MyKIFRS is an MCP server listed in the public MCP registry as kr.eocpa/mykifrs. Full-text search over K-IFRS/K-GAAP standards and KASB accounting Q&A for Korean accountants. This page covers its hosted endpoint (https://mykifrs.eocpa.kr/mcp).
Is the MyKIFRS MCP server safe to use?
MyKIFRS scores 80 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 MyKIFRS MCP server expose?
MyKIFRS exposes 6 tools: search_standards, search_qnas, get_paragraph, get_qna, list_standards, get_usage_stats. Their descriptions and schemas cost roughly 2,379 tokens of context every time the server is loaded.
Does the MyKIFRS MCP server require authentication?
Yes. MyKIFRS asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the MyKIFRS MCP server still maintained?
MyKIFRS is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.