xmlvalid

Validate XML and e-invoices (XSD, DTD, RelaxNG, EN 16931, Peppol, XRechnung), explain errors

사용해야 할까요

품질 및 안전성

A
설명 품질
100%
스키마 완전성
96%
이름 품질
92%
오염 위험
100%
권한 일치
100%
프로토콜 준수
100%

도구 정의와 프로토콜 준수에 대한 자동 분석을 기반으로 합니다.

컨텍스트 비용

~956토큰 (도구 정의)
~967 B일반적인 응답 크기
중간 정도의 주의 영향 (128k 컨텍스트의 0.75%)

이는 서버의 도구가 모델의 컨텍스트에 로드될 때마다 소비되는 대략적인 토큰 수입니다. 수치가 높을수록 다른 작업에 사용할 수 있는 주의가 줄어듭니다.

설치

원클릭 설치

`claude_desktop_config.json` 파일에 다음을 추가하세요:

{
  "mcpServers": {
    "xmlvalid": {
      "url": "https://xmlvalid.com/mcp"
    }
  }
}

원격 엔드포인트

https://xmlvalid.com/mcpstreamable-http

할 수 있는 일

도구 목록

도구 (5)

🟢 읽기 전용🟡 쓰기🔴 삭제⚪ 알 수 없음
🟢validate_xml(xml, url, schema, name, rules_version, ...)

Validate an XML document with xmlvalid: well-formedness, an XSD, DTD or RelaxNG schema, and for e-invoices the Schematron business rules of EN 16931, Peppol BIS, XRechnung, Factur-X and national formats. Pass the document as `xml` (its text) or `url` (a public http(s) address), and a `schema`: a catalog slug from search_schemas, a saved schema ("@orders-v3"), or "auto" to use the e-invoice profile the document names. Without a schema only well-formedness is checked. Returns valid, errors and warnings with line, column, message, rule and a help_url explaining each. Counts as one API validation of the key's monthly quota.

입력 스키마

{
  "type": "object",
  "properties": {
    "xml": {
      "description": "The XML document itself. Use url instead for a document on the web.",
      "type": "string"
    },
    "url": {
      "description": "A public http(s) URL of the document, fetched by xmlvalid.",
      "type": "string"
    },
    "schema": {
      "description": "A catalog slug (see search_schemas), \"@<name>\" for a saved schema, or \"auto\" for the e-invoice profile the document names. Leave out to check well-formedness only.",
      "type": "string"
    },
    "name": {
      "description": "A file name to show in the result, such as invoice-42.xml.",
      "type": "string"
    },
    "rules_version": {
      "description": "Pin Schematron rule sets to releases, as rule-set@version, comma-separated ([email protected]): the call fails with rules_version_mismatch when one has moved on. The result's rule_sets lists the releases that ran.",
      "type": "string"
    },
    "wait": {
      "description": "Seconds to wait for the result before returning a pending status to poll with get_validation.",
      "default": 30,
      "minimum": 0,
      "maximum": 60,
      "type": "integer"
    }
  }
}
🟢get_validation(id)

The status and result of a validation started with validate_xml that was still running when it returned (status "queued" or "running"). Results are kept for 24 hours.

입력 스키마

{
  "type": "object",
  "properties": {
    "id": {
      "description": "The id validate_xml returned.",
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}
🟢search_schemas(query)

Search xmlvalid's catalog of official XML schemas (UBL, CII, Peppol, XRechnung, Factur-X, ISO 20022, HL7, sitemaps…) by name, namespace, root element or area. Returns each schema's slug to pass to validate_xml, its version and the business rules it checks. No API key needed.

입력 스키마

{
  "type": "object",
  "properties": {
    "query": {
      "description": "Words to look for, such as \"peppol invoice\", \"xrechnung cii\" or \"pain.001\". Leave out to list the first schemas.",
      "type": "string"
    }
  }
}
🟢explain_error(message)

Explain an XML parsing or schema validation error message: what it means, why it happens and how to fix it, with an example. Understands libxml2 (xmllint, PHP, Python lxml, xmlvalid), Java (Xerces cvc-* codes, SAXParseException) and .NET (System.Xml) wording; paste the message as reported, stack trace prefix included. No API key needed.

입력 스키마

{
  "type": "object",
  "properties": {
    "message": {
      "description": "The error message, as the parser or validator reported it.",
      "type": "string"
    }
  },
  "required": [
    "message"
  ]
}
🟢explain_rule(id)

Explain an e-invoicing business rule by its id, such as BR-CO-15, BR-DE-1, PEPPOL-EN16931-R001 or a national CIUS rule: its message, level, the rule sets it belongs to, why invoices fail it and how to fix them. No API key needed.

입력 스키마

{
  "type": "object",
  "properties": {
    "id": {
      "description": "The rule id as the validator reports it, such as BR-CO-15.",
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}

커뮤니티

이 서버 평가하기

증거

최근 관측

검증됨버전이 기록되지 않음도구 5개