Server definition

Hash: sha256:d744c674d5e57620766c117407aa8ed5a951d5d11fec95a0ad21e3e54fc4d198
What it is: What a remote MCP server returned when asked what it offers: 5 tools

The blob, as servednamed by its sha256

{
  "instructions": "Use these tools to compare an older baseline OPC UA NodeSet2 XML document with a newer candidate revision. Use audit_nodeset_compatibility when both complete XML documents fit in one request. For large documents, create one temporary upload for each revision, append chunks in original order, then call audit_uploaded_nodesets. Results are static release-compatibility findings, not runtime interoperability or safety certification.",
  "tools": [
    {
      "description": "Append the next unmodified text chunk to a temporary NodeSet2 upload created by begin_nodeset_upload. Pass upload_id exactly as returned by begin_nodeset_upload and chunk as the next consecutive XML text segment; send every chunk in original order without overlap, omission or reformatting. On success the result returns status=OK, upload_id and cumulative received_chars; UNKNOWN_UPLOAD_ID or UPLOAD_TOO_LARGE indicates the upload cannot continue. This tool only stages XML in temporary memory and does not parse or compare it yet.",
      "inputSchema": {
        "properties": {
          "chunk": {
            "title": "Chunk",
            "type": "string"
          },
          "upload_id": {
            "title": "Upload Id",
            "type": "string"
          }
        },
        "required": [
          "upload_id",
          "chunk"
        ],
        "title": "append_nodeset_chunkArguments",
        "type": "object"
      },
      "name": "append_nodeset_chunk",
      "outputSchema": null
    },
    {
      "description": "Compare two complete OPC UA NodeSet2 XML documents when both fit in a single request. Pass old_nodeset_xml as the full baseline revision and new_nodeset_xml as the full candidate revision. The deterministic report returns result (COMPATIBLE, REVIEW_REQUIRED, BREAKING, or INSUFFICIENT_INPUT), old_node_count, new_node_count, issue_count, a summary keyed by change code, and issues containing code, severity, node_id and detail. Examples include NODE_ADDED, NODE_REMOVED, DATA_TYPE_CHANGED and reference changes. For large XML documents use begin_nodeset_upload + append_nodeset_chunk for each revision, then audit_uploaded_nodesets instead.",
      "inputSchema": {
        "properties": {
          "new_nodeset_xml": {
            "title": "New Nodeset Xml",
            "type": "string"
          },
          "old_nodeset_xml": {
            "title": "Old Nodeset Xml",
            "type": "string"
          }
        },
        "required": [
          "old_nodeset_xml",
          "new_nodeset_xml"
        ],
        "title": "audit_nodeset_compatibilityArguments",
        "type": "object"
      },
      "name": "audit_nodeset_compatibility",
      "outputSchema": null
    },
    {
      "description": "Compare two large NodeSet2 XML revisions after both have been fully staged with begin_nodeset_upload and append_nodeset_chunk. Pass old_upload_id for the baseline revision and new_upload_id for the candidate revision. This call consumes both upload IDs, so do not reuse them afterward. The report has the same shape as audit_nodeset_compatibility: result (COMPATIBLE, REVIEW_REQUIRED, BREAKING, or INSUFFICIENT_INPUT), old/new node counts, issue_count, summary by change code, and issues with code, severity, node_id and detail. Use the direct audit tool instead when both complete XML documents fit in a single request.",
      "inputSchema": {
        "properties": {
          "new_upload_id": {
            "title": "New Upload Id",
            "type": "string"
          },
          "old_upload_id": {
            "title": "Old Upload Id",
            "type": "string"
          }
        },
        "required": [
          "old_upload_id",
          "new_upload_id"
        ],
        "title": "audit_uploaded_nodesetsArguments",
        "type": "object"
      },
      "name": "audit_uploaded_nodesets",
      "outputSchema": null
    },
    {
      "description": "Start one temporary in-memory upload for a large NodeSet2 XML document. Call this once for the old baseline and once for the new candidate when the complete XML documents are too large for audit_nodeset_compatibility. It returns upload_id and max_total_chars. Append that document's chunks in original order with append_nodeset_chunk. Uploads expire after 15 minutes and the service allows at most four active uploads; this tool stores only temporary process memory and does not modify an external system.",
      "inputSchema": {
        "properties": {},
        "title": "begin_nodeset_uploadArguments",
        "type": "object"
      },
      "name": "begin_nodeset_upload",
      "outputSchema": null
    },
    {
      "description": "Return bounded service metadata for OPC UA NodeSet Compatibility Gate. Use this only to discover deployment stage, deterministic static-analysis scope, production availability and payment status; do not use it to compare NodeSets. The result contains product, stage, deterministic, payment_enabled, production_enabled and scope fields.",
      "inputSchema": {
        "properties": {},
        "title": "nodeset_compatibility_statusArguments",
        "type": "object"
      },
      "name": "nodeset_compatibility_status",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:d744c674d5e57620766c117407aa8ed5a951d5d11fec95a0ad21e3e54fc4d198 | sha256sum