_ registry / mcp streamable-http · checked 2h ago

myfss

https://myfss.eocpa.kr

Registry code: 77396a077f24f8cd

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://myfss.eocpa.kr/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is myfss live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is myfss free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does myfss have?
5 tools: get_usage_stats, search_documents, list_recent, list_tags, get_document.
Is myfss safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.9%

90 days 99.1%· all time 99.1%

latency
826ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 429 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search korean accounting supervision documents
  • read a regulator document
  • list recent regulator documents
takes → gives
text → text, data
tools
5 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 auth-required 5 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_usage_stats reads auth-required 30d ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "days": {
          "type": "number",
          "default": 30,
          "description": "최근 N일 윈도 (0이면 전체 기간, 기본 30)"
        }
      }
    }
    arguments 11 lines
  • search_documents reads auth-required 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "dept": {
          "type": "string",
          "description": "담당부서명 부분일치 (예: '회계감리')"
        },
        "board": {
          "enum": [
            "press",
            "guidance",
            "modelnotes",
            "manual",
            "trend",
            "extaudit",
            "icfr",
            "education",
            "sanction_case",
            "sanction_corp",
            "fsc_press"
          ],
          "type": "string",
          "description": "게시판 필터"
        },
        "limit": {
          "type": "number",
          "default": 15,
          "description": "최대 결과 수 (기본 15)"
        },
        "query": {
          "type": "string",
          "description": "검색 키워드 (공백 구분, 예: '전환사채 콜옵션')"
        },
        "nature": {
          "enum": [
            "감리·조사결과",
            "제도개정",
            "지침·모범사례",
            "실태·통계",
            "행사·안내",
            "기타"
          ],
          "type": "string",
          "description": "문서 성격 필터"
        },
        "offset": {
          "type": "number",
          "default": 0,
          "description": "페이지네이션 오프셋"
        },
        "source": {
          "enum": [
            "fss",
            "fsc"
          ],
          "type": "string",
          "description": "발행기관 필터 (fss=금융감독원, fsc=금융위원회)"
        },
        "topics": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "주제 태그 필터 (하나라도 일치, list_tags의 topics 값)"
        },
        "date_to": {
          "type": "string",
          "description": "YYYY-MM-DD 이전"
        },
        "date_from": {
          "type": "string",
          "description": "YYYY-MM-DD 이후"
        }
      }
    }
    arguments 76 lines
  • list_recent reads auth-required 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "board": {
          "enum": [
            "press",
            "guidance",
            "modelnotes",
            "manual",
            "trend",
            "extaudit",
            "icfr",
            "education",
            "sanction_case",
            "sanction_corp",
            "fsc_press"
          ],
          "type": "string",
          "description": "게시판 필터"
        },
        "limit": {
          "type": "number",
          "default": 20,
          "description": "최대 결과 수 (기본 20)"
        }
      }
    }
    arguments 28 lines
  • list_tags reads auth-required 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • get_document reads auth-required 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ntt_id"
      ],
      "properties": {
        "ntt_id": {
          "type": "number",
          "description": "search_documents/list_recent가 반환한 ntt_id"
        },
        "max_chars": {
          "type": "number",
          "default": 60000,
          "description": "본문 최대 길이(자)"
        },
        "offset_chars": {
          "type": "number",
          "default": 0,
          "description": "본문 시작 오프셋 (긴 문서 이어읽기)"
        }
      }
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 77396a077f24f8cd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/77396a077f24f8cd/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/77396a077f24f8cd/badge.svg)](https://brick.blue/agent/77396a077f24f8cd?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on eocpa.kr 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.