Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MyFSS

REMOTE · MYFSS.EOCPA.KR · SCANNED SEP 22

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

Available components

+4 this week 80 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • 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. 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

remote · myfss.eocpa.kr

# add to Claude Code
claude mcp add --transport http kr-eocpa-myfss 'https://myfss.eocpa.kr/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "kr-eocpa-myfss": {
      "url": "https://myfss.eocpa.kr/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "kr-eocpa-myfss": {
      "type": "http",
      "url": "https://myfss.eocpa.kr/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add kr-eocpa-myfss --url 'https://myfss.eocpa.kr/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  kr-eocpa-myfss:
    url: "https://myfss.eocpa.kr/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "kr-eocpa-myfss": {
      "Transport": "http",
      "Url": "https://myfss.eocpa.kr/mcp"
    }
  }
}
# add to Vellum
assistant mcp add kr-eocpa-myfss -t streamable-http -u 'https://myfss.eocpa.kr/mcp'
// mcp.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 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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 12 Sept 26 +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.

  • 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
Diagnostics

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://myfss.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=myfss.eocpa.kr CN=YE1,O=Let's Encrypt,C=US 3 Sept 2026 2 Dec 2026 ECDSA 256 ECDSA-SHA384 588083124f13d2dc3751cf50141afda1ff0
SANs: myfss.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 myfss.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://myfss.eocpa.kr/mcp Verified 200
http (plaintext) http://myfss.eocpa.kr/mcp HTTPS enforced 301 https://myfss.eocpa.kr/mcp
MCP tools · 5 exposed · ~1,810 tokens

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 →

Tool Tokens
get_document ~369

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.

NameTypeReqDescription
max_charsnumber본문 최대 길이(자)
ntt_idnumberyessearch_documents/list_recent가 반환한 ntt_id
offset_charsnumber본문 시작 오프셋 (긴 문서 이어읽기)

No output schema declared.

No examples provided.

get_usage_stats ~352

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

NameTypeReqDescription
daysnumber최근 N일 윈도 (0이면 전체 기간, 기본 30)

No output schema declared.

No examples provided.

list_recent ~264

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.

NameTypeReqDescription
boardstring게시판 필터
limitnumber최대 결과 수 (기본 20)

No output schema declared.

No examples provided.

list_tags ~249

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_documents ~576

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.

NameTypeReqDescription
boardstring게시판 필터
date_fromstringYYYY-MM-DD 이후
date_tostringYYYY-MM-DD 이전
deptstring담당부서명 부분일치 (예: '회계감리')
limitnumber최대 결과 수 (기본 15)
naturestring문서 성격 필터
offsetnumber페이지네이션 오프셋
querystring검색 키워드 (공백 구분, 예: '전환사채 콜옵션')
sourcestring발행기관 필터 (fss=금융감독원, fsc=금융위원회)
topicsarray주제 태그 필터 (하나라도 일치, list_tags의 topics 값)

No output schema declared.

No examples provided.

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