# IBTCC 공기업 경쟁률 조회 (remote · ibtcc.kr)

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

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

## Components

- remote · `ibtcc.kr`: 82/100 (this document), [markdown](https://verifymcp.io/servers/kr-ibtcc-competition-ratio/api-mcp.md), [page](https://verifymcp.io/servers/kr-ibtcc-competition-ratio/api-mcp)

## Channel facts

- Endpoint: `https://ibtcc.kr/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 82/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 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.

### Claude

```bash
claude mcp add --transport http kr-ibtcc-competition-ratio 'https://ibtcc.kr/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kr-ibtcc-competition-ratio": {
      "url": "https://ibtcc.kr/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kr-ibtcc-competition-ratio": {
      "type": "http",
      "url": "https://ibtcc.kr/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kr-ibtcc-competition-ratio]
url = "https://ibtcc.kr/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kr-ibtcc-competition-ratio": {
      "type": "remote",
      "url": "https://ibtcc.kr/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kr-ibtcc-competition-ratio --url 'https://ibtcc.kr/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kr-ibtcc-competition-ratio:
    url: "https://ibtcc.kr/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kr-ibtcc-competition-ratio": {
      "Transport": "http",
      "Url": "https://ibtcc.kr/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kr-ibtcc-competition-ratio -t streamable-http -u 'https://ibtcc.kr/api/mcp'
```

### Other

```json
{
  "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.

## 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-20 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 82, +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.

### 2026-09-17 (score 81, +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.

### 2026-09-15 (score 80, +1)

- [functional regression] Schema quality: pass → fail
- [functional] New tool “lookup_pass_cut”

### 2026-09-14 (score 79, +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.

### 2026-09-12 (score 78, +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.

### 2026-09-10 (score 77, +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.

### 2026-09-07 (score 76, +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.

## MCP tools (2)

### `lookup_competition_ratio` (~120 tokens)

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

Input parameters:

- `institution` (string, required): 기관명 (예: 한국전력공사, 국민연금공단, 한국철도공사)
- `limit` (integer): 반환할 최근 채용 건수 (기본 3건, 최대 10건)

### `lookup_pass_cut` (~186 tokens)

한국 공공기관(공기업) 합격자들의 실제 스펙(토익 점수·학점·자격증 개수)을 기관명으로 조회합니다. 사용자 제보 기반 집계 데이터로, 직무별 토익 중앙값·범위·학점 중앙값·자격증 개수 중앙값과 표본 수를 반환합니다. 경쟁률(지원자 수)이 아니라 "합격하려면 어느 정도 스펙이 필요한지"를 알고 싶을 때 사용하세요.

Input parameters:

- `institution` (string, required): 기관명 (예: 한국전력공사, 국민연금공단, 한국철도공사)
- `job_role` (string): 직무명으로 좁혀서 조회 (예: 사무, 전기, 행정직). 생략하면 해당 기관의 전체 직무를 반환.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kr-ibtcc-competition-ratio/api-mcp#diagnostics

## Score history

- 2026-09-21: 82
- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 79
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 73
- 2026-09-01: 73
- 2026-08-31: 72
- 2026-08-30: 72
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 70
- 2026-08-26: 70
- 2026-08-25: 68
- 2026-08-24: 68
- 2026-08-23: 67

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

## Links

- Remote endpoint: https://ibtcc.kr/api/mcp
- Repository: https://github.com/jojunho74/hometest
- Changelog RSS feed: https://verifymcp.io/servers/kr-ibtcc-competition-ratio/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kr-ibtcc-competition-ratio/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kr-ibtcc-competition-ratio/api-mcp