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.

IBTCC 공기업 경쟁률 조회

REMOTE · IBTCC.KR

한국 공공기관(공기업) 채용 경쟁률을 기관명으로 조회합니다. 알리오(ALIO) 공시 데이터 기반으로 최근 채용 건별 1차 지원자 수와 1차 경쟁률을 반환합니다.

Available components

+8 this week 82 Trust /100

Last scanned (7 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 7 Nov 2026.

Category Project Management

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 Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 607 tokens (~121/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 3 Nov 26 +8
    • Stability: fail → pass ▲ security
  • 15 Oct 26 −8
    • Stability: pass → fail ▼ security
  • 4 Oct 26 82
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “lookup_pass_cut” was removed ▼ security
    • Schema quality: 153 → 121 ▲ functional
    • New tool “convert_exam_score” functional
    • New tool “get_my_roadmap_summary” functional
    • New tool “lookup_job_posting” functional
    • New tool “lookup_job_schedule” functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 7 Nov 2026 · Probed https://ibtcc.kr/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ibtcc.kr CN=YR1,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 RSA 2048 SHA256-RSA 5bac4017c4ad3f7c1462fb2afbdd8afefe1
SANs: ibtcc.kr
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ibtcc.kr. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
kr. DS published 64641 13 Verified
ibtcc.kr. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://cdn.tailwindcss.com https://cdn.jsdelivr.net https://cdn.plot.ly https://fonts.googleapis.com https://www.googletagmanager.com https://cdn.emailjs.com https://t1.kakaocdn.net https://developers.kakao.com https://js.tosspayments.com https://dapi.kakao.com https://t1.daumcdn.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://byzulmxcuhsrjdphmuym.supabase.co wss://byzulmxcuhsrjdphmuym.supabase.co https://www.google-analytics.com https://analytics.google.com https://region1.google-analytics.com https://api.emailjs.com https://cdn.jsdelivr.net https://kauth.kakao.com https://kapi.kakao.com https://ka.kakao.com https://talk-pillar.kakao.com https://api.anthropic.com https://api.tosspayments.com https://dapi.kakao.com; img-src 'self' data: blob: https:; frame-src https://www.youtube.com https://www.youtube-nocookie.com https://sharer.kakao.com https://js.tosspayments.co
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ibtcc.kr/api/mcp Verified 200
http (plaintext) http://ibtcc.kr/api/mcp HTTPS enforced 308 https://ibtcc.kr/api/mcp
MCP tools · 5 exposed · ~607 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
convert_exam_score ~125

G-TELP/오픽(OPIc)/토스(TOSS)-TOEIC 점수를 서로 환산합니다(점수대비표). 현재는 G-TELP·OPIc·TOSS → TOEIC 환산만 지원합니다(DB 조회 없는 순수 계산).

NameTypeReqDescription
exam_typestringyes환산할 원 시험 종류
scorestringyes원 점수/등급 (예: G-TELP는 "65", OPIc은 "IM2", TOSS는 "Lv5" 또는 등급문자)

No output schema declared.

No examples provided.

get_my_roadmap_summary ~124

로그인한 본인의 ibtcc.kr "1~3개월 합격 로드맵" 요약을 조회합니다. ibtcc.kr 마이페이지에서 발급받은 MCP 전용 연결 코드(mcp_로 시작)가 Authorization: Bearer 헤더로 전달되어야 합니다 (로그인 세션 토큰이 아닙니다 — 계정 전체가 아닌 로드맵 조회만 가능한 별도 코드입니다). 프리미엄 구독 중이고 로드맵을 생성한 사용자만 결과를 받을 수 있습니다.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_competition_ratio ~120

한국 공공기관(공기업) 채용 경쟁률을 기관명으로 조회합니다. 알리오(ALIO) 공시 데이터 기반으로, 해당 기관의 최근 채용 건별 1차 지원자 수와 1차 경쟁률을 반환합니다.

NameTypeReqDescription
institutionstringyes기관명 (예: 한국전력공사, 국민연금공단, 한국철도공사)
limitinteger–반환할 최근 채용 건수 (기본 3건, 최대 10건)

No output schema declared.

No examples provided.

lookup_job_posting ~127

한국 공공기관(공기업)의 채용 공고 메타정보(제목·직무·접수기간·지역·채용인원·상태·원문링크)를 기관명으로 조회합니다. 공공기관 채용공고 게시판(ibtcc.kr)에 등록된 공고 기준입니다.

NameTypeReqDescription
limitinteger–반환할 공고 건수 (기본 5건, 최대 10건)
org_namestringyes기관명 (예: 한전KPS, 한국토지주택공사)

No output schema declared.

No examples provided.

lookup_job_schedule ~111

한국 공공기관(공기업)의 채용 일정을 기업명으로 조회합니다. 접수 시작·마감 등 일정 이벤트를 날짜순으로 반환합니다. 오늘 이후 예정된 일정을 우선 반환하고, 없으면 최근 지난 일정을 반환합니다.

NameTypeReqDescription
companystringyes기업/기관명 (예: 한국전력공사, 국민연금공단)
limitinteger–반환할 일정 건수 (기본 5건, 최대 10건)

No output schema declared.

No examples provided.

Install

How do I install the IBTCC 공기업 경쟁률 조회 MCP server?

IBTCC 공기업 경쟁률 조회 is a hosted endpoint at https://ibtcc.kr/api/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 · ibtcc.kr

# add to Claude Code
claude mcp add --transport http kr-ibtcc-competition-ratio 'https://ibtcc.kr/api/mcp'
Common questions

What is the IBTCC 공기업 경쟁률 조회 MCP server?

IBTCC 공기업 경쟁률 조회 is an MCP server listed in the public MCP registry as kr.ibtcc/competition-ratio. 한국 공공기관(공기업) 채용 경쟁률을 기관명으로 조회합니다. 알리오(ALIO) 공시 데이터 기반으로 최근 채용 건별 1차 지원자 수와 1차 경쟁률을 반환합니다. This page covers its hosted endpoint (https://ibtcc.kr/api/mcp).

Is the IBTCC 공기업 경쟁률 조회 MCP server safe to use?

IBTCC 공기업 경쟁률 조회 scores 82 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 IBTCC 공기업 경쟁률 조회 MCP server expose?

IBTCC 공기업 경쟁률 조회 exposes 5 tools: lookup_competition_ratio, lookup_job_schedule, lookup_job_posting, convert_exam_score, get_my_roadmap_summary. Their descriptions and schemas cost roughly 607 tokens of context every time the server is loaded.

Does the IBTCC 공기업 경쟁률 조회 MCP server require authentication?

No. We connected to IBTCC 공기업 경쟁률 조회 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the IBTCC 공기업 경쟁률 조회 MCP server still maintained?

IBTCC 공기업 경쟁률 조회 is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the IBTCC 공기업 경쟁률 조회 MCP server?

VerifyMCP ran 12 checks on IBTCC 공기업 경쟁률 조회, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about IBTCC 공기업 경쟁률 조회: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.