IBTCC 공기업 경쟁률 조회
REMOTE · IBTCC.KR · SCANNED SEP 21
한국 공공기관(공기업) 채용 경쟁률을 기관명으로 조회합니다. 알리오(ALIO) 공시 데이터 기반으로 최근 채용 건별 1차 지원자 수와 1차 경쟁률을 반환합니다.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 306 tokens (~153/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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
claude mcp add --transport http kr-ibtcc-competition-ratio 'https://ibtcc.kr/api/mcp'
{
"mcpServers": {
"kr-ibtcc-competition-ratio": {
"url": "https://ibtcc.kr/api/mcp"
}
}
} {
"servers": {
"kr-ibtcc-competition-ratio": {
"type": "http",
"url": "https://ibtcc.kr/api/mcp"
}
}
} [mcp_servers.kr-ibtcc-competition-ratio] url = "https://ibtcc.kr/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kr-ibtcc-competition-ratio": {
"type": "remote",
"url": "https://ibtcc.kr/api/mcp",
"enabled": true
}
}
} openclaw mcp add kr-ibtcc-competition-ratio --url 'https://ibtcc.kr/api/mcp' --transport streamable-http
mcp_servers:
kr-ibtcc-competition-ratio:
url: "https://ibtcc.kr/api/mcp" {
"McpServers": {
"kr-ibtcc-competition-ratio": {
"Transport": "http",
"Url": "https://ibtcc.kr/api/mcp"
}
}
} assistant mcp add kr-ibtcc-competition-ratio -t streamable-http -u 'https://ibtcc.kr/api/mcp'
{
"mcpServers": {
"kr-ibtcc-competition-ratio": {
"type": "http",
"url": "https://ibtcc.kr/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- Schema quality: pass → fail ▼ functional
- New tool “lookup_pass_cut” functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +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.
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 21 Sept 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 | 16 Aug 2026 | 14 Nov 2026 | RSA 2048 | SHA256-RSA | 52fca5a2497f13ac2dffee785a49d957ec3 |
| 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. | present | 64641 | 13 | Verified |
| ibtcc.kr. | absent | 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; 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; img-src 'self' data: blob: https:; frame-src https://www.youtube.com https://www.youtube-nocookie.com https://sharer.kakao.com https://js.tosspayments.com; frame-ancestors 'none'; |
| 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 |
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 →
lookup_competition_ratio ~120
한국 공공기관(공기업) 채용 경쟁률을 기관명으로 조회합니다. 알리오(ALIO) 공시 데이터 기반으로, 해당 기관의 최근 채용 건별 1차 지원자 수와 1차 경쟁률을 반환합니다.
| Name | Type | Req | Description |
|---|---|---|---|
| institution | string | yes | 기관명 (예: 한국전력공사, 국민연금공단, 한국철도공사) |
| limit | integer | – | 반환할 최근 채용 건수 (기본 3건, 최대 10건) |
No output schema declared.
No examples provided.
lookup_pass_cut ~186
한국 공공기관(공기업) 합격자들의 실제 스펙(토익 점수·학점·자격증 개수)을 기관명으로 조회합니다. 사용자 제보 기반 집계 데이터로, 직무별 토익 중앙값·범위·학점 중앙값·자격증 개수 중앙값과 표본 수를 반환합니다. 경쟁률(지원자 수)이 아니라 "합격하려면 어느 정도 스펙이 필요한지"를 알고 싶을 때 사용하세요.
| Name | Type | Req | Description |
|---|---|---|---|
| institution | string | yes | 기관명 (예: 한국전력공사, 국민연금공단, 한국철도공사) |
| job_role | string | – | 직무명으로 좁혀서 조회 (예: 사무, 전기, 행정직). 생략하면 해당 기관의 전체 직무를 반환. |
No output schema declared.
No examples provided.
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 2 tools: lookup_competition_ratio, lookup_pass_cut. Their descriptions and schemas cost roughly 306 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.