MCP Profile

MCP Documentation · Design reference · No live transport on this site

HEXT defines an optional MCP Profile for Model Context Protocol automation. This page documents the intended tool and resource surface for HEXT Standard 1.1. No MCP transport is deployed on hextai.com.

hextai.com implements the Discovery Profile (Server Card, llms.txt) and is WebMCP Ready — not WebMCP Native. Live transport is expected via the hext-mcp reference implementation.

Discovery

Pre-connection metadata is published at the MCP Server Card endpoint (SEP-2127, draft):

GET /.well-known/mcp/server-card.json

The card declares Discovery Profile resources only. Streamable HTTP transport (remotes) is empty until MCP Profile transport is deployed.

Registry catalog: /registry/catalog.json

Resources

resource://hext/document/{id}

Returns the HEXT document for the given object identity.

HTTPS equivalent (JSON projection): /object/{id}/document.json · Catalog: /registry/catalog.json

Tools

The following tools are specified for MCP Profile implementations. Not available on this site.

get_object(id)

Retrieve a crystallized knowledge object by Semantic Identity (URI, UUID, hash, or token).

// Response: Semantic XML or JSON projection
{
  "object": { "id": "rfc-nvp18", "type": "document.rfc" },
  "provenance": { ... },
  "ledger": [ ... ],
  "final_seal": { ... }
}

query(filter)

Graph-oriented semantic query (future). Not XPath. See Query Model.

query({ type: "document.rfc", lifecycle: "draft" })

validate(document)

Verify schema conformance, ledger chain, and state hash integrity.

validate(xmlDocument) → { status: "ok" | "malformed" | "tampered" }

render(document, format)

Project Semantic XML to HTML or other non-canonical formats.

render(xmlDocument, "html") → htmlString

canonicalize(document)

Normalize to Canonical XML and compute state hash.

canonicalize(xmlDocument) → { bytes: "...", state_hash: "sha256:..." }

REST API documentation → · Implementation Profiles →