# MyFSS (remote · myfss.eocpa.kr)

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

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

## Components

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

## Channel facts

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

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

- **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**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1810 tokens (~362/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 MyFSS MCP server?

MyFSS is a hosted endpoint at https://myfss.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-myfss 'https://myfss.eocpa.kr/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "kr-eocpa-myfss": {
      "type": "http",
      "url": "https://myfss.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-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-16 (score 77, +1)

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

### 2026-09-14 (score 76, +1)

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

### 2026-09-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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.

### 2026-09-08 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (5)

### `search_documents` (~576 tokens)

회계·공시 자료 전문검색

MyFSS MCP의 search_documents 도구는 금융감독원(FSS)·금융위원회(FSC) 회계·공시 자료를 전문검색합니다.

[Purpose]
\- What 감독당국 checks — 심사·감리 지적사례·감독지침·모범사례 등 게시판 11종.
\- Filters alone (no query) sweep a topic.

[Usage]
1\. "전환사채 콜옵션 관련 감독원 자료" → query="전환사채 콜옵션"
2\. "작년 감리 지적사례 전부" → board="sanction_case", date_from="2025-01-01", date_to="2025-12-31"
3\. "내부회계관리제도 주제로 20건" → topics=["내부회계관리제도"], limit=20

[Response]
\- { total, showing, offset, note, results:[{ntt_id, date, board, source, title, nature, topics,
  depts, summary, url, snippet?}] }
\- total = 전체 건수, showing = 이번 페이지 — paginate with offset.
\- source: "fss"=금융감독원, "fsc"=금융위원회.
\- snippet marks matches with [ … ]; only when a query matched.

[Rules]
\- board is asymmetric: param = English key, response = 한글 라벨 — never feed it back.
\- topics·depts are joined strings (", " / " / "), not arrays — split first.
\- ≥3-char tokens → FTS (AND, rank); 1~2-char → LIKE. No query → 게시일 DESC, no snippet.
\- Corpus = 2010 onward (absent = 미수록); quote body via get_document, not summary·snippet.

Input parameters:

- `board` (string): 게시판 필터
- `date_from` (string): YYYY-MM-DD 이후
- `date_to` (string): YYYY-MM-DD 이전
- `dept` (string): 담당부서명 부분일치 (예: '회계감리')
- `limit` (number): 최대 결과 수 (기본 15)
- `nature` (string): 문서 성격 필터
- `offset` (number): 페이지네이션 오프셋
- `query` (string): 검색 키워드 (공백 구분, 예: '전환사채 콜옵션')
- `source` (string): 발행기관 필터 (fss=금융감독원, fsc=금융위원회)
- `topics` (array): 주제 태그 필터 (하나라도 일치, list_tags의 topics 값)

### `get_document` (~369 tokens)

문서 전문

MyFSS MCP의 get_document 도구는 문서 전문을 반환합니다 — 첨부 HWP를 마크다운으로 변환한 본문.

[Purpose]
\- To read and quote a found document — summary·snippet are never quoting grounds.

[Usage]
1\. "그 자료 본문 보여줘" → ntt_id=12345
2\. "길어서 잘렸는데 이어서" → ntt_id=12345, offset_chars=60000
3\. "앞부분만 짧게" → ntt_id=12345, max_chars=8000

[Response]
\- { ntt_id, date, board, source, title, nature, topics, depts, summary, url,
  attachments:[{file_name, ext, parsed}], body_total_chars, offset_chars, truncated, body }
\- truncated=true means offset_chars+max_chars < body_total_chars — raise offset_chars to continue.
\- Unknown id returns { error: "ntt_id {n} 없음" }.
\- body = "(본문 없음)" when nothing was parsed and no HTML 본문 exists.

[Rules]
\- body = parsed attachments (parsed=true) joined under "## 첨부: {file_name}" heads;
  with no attachment body it falls back to the detail-page HTML body (mostly FSC).
\- attachments with parsed=false are NOT in body — disclose the gap, never hide it.
\- Continue with offset_chars; raising max_chars grows the whole response.

Input parameters:

- `max_chars` (number): 본문 최대 길이(자)
- `ntt_id` (number, required): search_documents/list_recent가 반환한 ntt_id
- `offset_chars` (number): 본문 시작 오프셋 (긴 문서 이어읽기)

### `list_recent` (~264 tokens)

최신 문서 목록

MyFSS MCP의 list_recent 도구는 최신 문서 목록을 게시일 내림차순으로 반환합니다.

[Purpose]
\- Query-less skim of "what came out lately", optionally narrowed by 게시판.

[Usage]
1\. "최근 자료 뭐 있어" → (인자 없음 — limit=20)
2\. "감리 지적사례 최신 10건" → board="sanction_case", limit=10
3\. "금융위 보도자료 최신" → board="fsc_press"

[Response]
\- { results:[{ntt_id, date, board, source, title, nature, topics, depts, summary, url}] }
\- No total/offset — this tool has no pagination, and no snippet (there is no query).

[Rules]
\- board takes the English key while the response returns the 한글 라벨 — same asymmetry as
  search_documents; never feed the response board back as a parameter.
\- Sorted by 게시일(date) — retroactively registered old documents never surface as new.
\- For period/topic narrowing or larger volumes use search_documents.

Input parameters:

- `board` (string): 게시판 필터
- `limit` (number): 최대 결과 수 (기본 20)

### `list_tags` (~249 tokens)

검색 어휘 사전

MyFSS MCP의 list_tags 도구는 검색 필터에 넣을 수 있는 어휘를 반환합니다 — 주제 태그·문서 성격·게시판·주요 담당부서.

[Purpose]
\- Which values actually exist for search_documents' topics·nature·board·dept.
  Invented values return 0 rows, not an error — check here before a futile search.

[Usage]
1\. "어떤 주제로 검색할 수 있어?" → (인자 없음)

[Response]
\- { topics:[{name, n}], natures:[{name, n}], boards:[{key, label, n}], depts_top25:[{name, n}] }
\- n = 그 값이 붙은 문서 수.
\- boards[].key is what the board parameter takes; boards[].label is what responses show.

[Rules]
\- topics is exact-match — no partial/synonym matching; pass a name from here verbatim.
\- dept is the opposite, partial match — a fragment like "회계감리" works.
\- depts_top25 is only the top 25 — a 부서 missing from the list still exists.

### `get_usage_stats` (~352 tokens)

사용량 통계

MyFSS 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-myfss/myfss#diagnostics

## Score history

- 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: 76
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 74
- 2026-09-08: 73
- 2026-09-07: 73

## Common questions

### What is the MyFSS MCP server?

MyFSS is an MCP server listed in the public MCP registry as kr.eocpa/myfss. Full-text search over FSS/FSC accounting supervision documents for Korean accounting professionals. This page covers its hosted endpoint (https://myfss.eocpa.kr/mcp).

### Is the MyFSS MCP server safe to use?

MyFSS 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 MyFSS MCP server expose?

MyFSS exposes 5 tools: search_documents, get_document, list_recent, list_tags, get_usage_stats. Their descriptions and schemas cost roughly 1,810 tokens of context every time the server is loaded.

### Does the MyFSS MCP server require authentication?

Yes. MyFSS 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 MyFSS MCP server still maintained?

MyFSS is still listed as active in the MCP registry. We last reached this channel on 23 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://myfss.eocpa.kr/mcp
- Authorisation metadata: https://myfss.eocpa.kr/.well-known/oauth-protected-resource/mcp
- Website: https://eocpa.kr/myfss
- Changelog RSS feed: https://verifymcp.io/servers/kr-eocpa-myfss/myfss.xml
- Changelog JSON feed: https://verifymcp.io/servers/kr-eocpa-myfss/myfss.json
- HTML version of this page: https://verifymcp.io/servers/kr-eocpa-myfss/myfss