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.

XBOSS

REMOTE · API.XDATA.KR

국세, 4대보험, 세금계산서, 급여 데이터를 MCP 도구로 제공하는 XBOSS 공식 서버. 무료 요금제, 카드 등록 없음.

Available components

70 Trust /100

Last scanned (17 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

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 Security81
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 235791 tokens (~582/item across 405 items; 405 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 Management20
  • Stability observed for 6 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 Safety50
  • Injection-marker check failed: the server instructions contains an instruction to conceal the call from the user, the text "Do not tell the user", at byte 7564 of that field. See how to fix → Fail
  • All 25 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 406 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
  • Authorization
  • 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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 +1
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 0
    • Schema quality: good → excellent functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Nov 26 67

    First indexed and scored.

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 21 Nov 2026 · Probed https://api.xdata.kr/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xdata.kr CN=WR3,O=Google Trust Services,C=US 5 Nov 2026 3 Feb 2027 RSA 2048 SHA256-RSA ab3cb13db3fe747609d1361b0b17c808
SANs: xdata.kr, www.xdata.kr, console.xdata.kr, admin.xdata.kr, api.xdata.kr
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.xdata.kr. — Not signed

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

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://api.xdata.kr/.well-known/oauth-protected-resource/mcp", error_description="XBOSS login required", scope="mcp:tools:list mcp:tools:call"

Bearer resource_metadata="https://api.xdata.kr/.well-known/oauth-protected-resource/mcp", error_description="XBOSS login required", scope="mcp:tools:list mcp:tools:call"

Protected resource metadata

Document https://api.xdata.kr/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://api.xdata.kr/mcp
Authorisation server https://api.xdata.kr

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.xdata.kr/mcp Verified 200
http (plaintext) http://api.xdata.kr/mcp Inconclusive 405
MCP tools · 405 exposed · ~232,571 tokens partial

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
work24__subsidy__application__withdraw ~527

No description provided.

NameTypeReqDescription
account_link_idstring––
business_management_nostring––
confirmbooleanyes–
confirmation_tokenstring––
programme_keystringyes–
receipt_nostringyes–

No output schema declared.

No examples provided.

work24__subsidy__application__workplace_save ~539

No description provided.

NameTypeReqDescription
account_link_idstring––
applicant_base_addressstring––
applicant_detail_addressstring––
applicant_zipstring––
application_quarterinteger––
application_yearinteger––
business_management_nostring––
manager_emailstring––
manager_mobile1string––
manager_mobile2string––
manager_namestring––
manager_phone1string––
manager_phone2string––
payment_account_holderstring––
payment_account_nostring––
payment_bank_namestring––
programme_keystringyes–

No output schema declared.

No examples provided.

work24__subsidy__diagnosis__search ~732

No description provided.

NameTypeReqDescription
account_link_idstring––
application_yearinteger––
business_management_nostring––
output_formatsarray––
programme_keysarray––
request_idempotency_keystring––

No output schema declared.

No examples provided.

xdata__content__read ~217

No description provided.

NameTypeReqDescription
content_artifact_refstringyes–

No output schema declared.

No examples provided.

xdata__job__result ~628

No description provided.

NameTypeReqDescription
job_idstring––
pack_run_idstring––
recovery_receiptstring––

No output schema declared.

No examples provided.

Install

How do I install the XBOSS MCP server?

XBOSS is a hosted endpoint at https://api.xdata.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 · api.xdata.kr

# add to Claude Code
claude mcp add --transport http kr-xdata-xboss-mcp 'https://api.xdata.kr/mcp'
Common questions

What is the XBOSS MCP server?

XBOSS is an MCP server listed in the public MCP registry as kr.xdata/xboss-mcp. 국세, 4대보험, 세금계산서, 급여 데이터를 MCP 도구로 제공하는 XBOSS 공식 서버. 무료 요금제, 카드 등록 없음. This page covers its hosted endpoint (https://api.xdata.kr/mcp).

Is the XBOSS MCP server safe to use?

XBOSS scores 70 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.

Does the XBOSS MCP server require authentication?

Yes. XBOSS 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 XBOSS MCP server still maintained?

XBOSS is still listed as active in the MCP registry. We last reached this channel on 21 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 XBOSS MCP server?

VerifyMCP ran 12 checks on XBOSS, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about XBOSS: HTTPS. 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.