# MyKIFRS (remote · mykifrs.eocpa.kr)

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

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `mykifrs.eocpa.kr`: 81/100 (this document), [markdown](https://verifymcp.io/servers/kr-eocpa-mykifrs/mykifrs.md), [page](https://verifymcp.io/servers/kr-eocpa-mykifrs/mykifrs)

## Channel facts

- Endpoint: `https://mykifrs.eocpa.kr/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.11.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http kr-eocpa-mykifrs 'https://mykifrs.eocpa.kr/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kr-eocpa-mykifrs": {
      "url": "https://mykifrs.eocpa.kr/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kr-eocpa-mykifrs": {
      "type": "http",
      "url": "https://mykifrs.eocpa.kr/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kr-eocpa-mykifrs]
url = "https://mykifrs.eocpa.kr/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kr-eocpa-mykifrs": {
      "type": "remote",
      "url": "https://mykifrs.eocpa.kr/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kr-eocpa-mykifrs --url 'https://mykifrs.eocpa.kr/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kr-eocpa-mykifrs:
    url: "https://mykifrs.eocpa.kr/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kr-eocpa-mykifrs": {
      "Transport": "http",
      "Url": "https://mykifrs.eocpa.kr/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kr-eocpa-mykifrs -t streamable-http -u 'https://mykifrs.eocpa.kr/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 81, +1)

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

### 2026-09-22 (score 80, +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.

### 2026-09-20 (score 79, +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.

### 2026-09-18 (score 78, +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.

### 2026-09-15 (score 77, +1)

- [security] 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
- [functional] 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
- [cosmetic] “get_qna” added an optional parameter “qna_key”
- [cosmetic] “get_qna” reworded the description of “doc_number”
- [cosmetic] “get_qna” made “doc_number” optional

### 2026-09-13 (score 76, +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.

### 2026-09-11 (score 75, +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.

### 2026-09-09 (score 74, +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.

## MCP tools (6)

### `search_standards` (~450 tokens)

기준서 전문검색

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 기준서 원문.

Input parameters:

- `limit` (number): 최대 결과 수 (기본 10)
- `query` (string, required): 검색 키워드 (공백 구분)
- `std_num` (number): 특정 기준서로 한정 (예: 1116)

### `search_qnas` (~456 tokens)

질의회신 전문검색

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.

Input parameters:

- `limit` (number): 최대 결과 수 (기본 10)
- `query` (string, required): 검색 키워드 (공백 구분)

### `get_paragraph` (~393 tokens)

기준서 문단 원문

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.

Input parameters:

- `context` (number): 앞뒤로 포함할 항목 수 (기본 2)
- `unique_key` (string, required): 문단 키 (예: '1116-33')

### `get_qna` (~415 tokens)

질의회신 전문

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 번호.

Input parameters:

- `doc_number` (string): 질의회신 문서번호 — qna_key 를 주지 않을 때 필수
- `qna_key` (string): 행 식별자 "{source}:{id}" (search_qnas 의 qna_key, 예: legacy:6009) — 번호가 비었거나 중복일 때

### `list_standards` (~312 tokens)

수록 기준서 카탈로그

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.

Input parameters:

- `category` (string): 카테고리로 필터 (생략 시 전체)

### `get_usage_stats` (~353 tokens)

사용량 통계

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).

Input parameters:

- `days` (number): 최근 N일 윈도 (0이면 전체 기간, 기본 30)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kr-eocpa-mykifrs/mykifrs#diagnostics

## Score history

- 2026-09-24: 81
- 2026-09-23: 80
- 2026-09-22: 80
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 75
- 2026-09-11: 75
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73

## Common questions

### 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 81 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mykifrs.eocpa.kr/mcp
- Authorisation metadata: https://mykifrs.eocpa.kr/.well-known/oauth-protected-resource/mcp
- Website: https://eocpa.kr/mykifrs
- Changelog RSS feed: https://verifymcp.io/servers/kr-eocpa-mykifrs/mykifrs.xml
- Changelog JSON feed: https://verifymcp.io/servers/kr-eocpa-mykifrs/mykifrs.json
- HTML version of this page: https://verifymcp.io/servers/kr-eocpa-mykifrs/mykifrs