Use in your browser

Validate your TEI edition

Check a hosted or pasted TEI P5 edition against its RNG grammar with jing and the beyond-schema Schematron layer with Saxon, and read the exact rule and location behind every finding. Compare a baseline and a revised edition to see what changed.

Guest includes 50 lifetime app requests. Create a free account for 100 app requests each calendar month. One allowance across every app, in your browser and your agent.One allowance across every app, in your browser and your agent. Manage usage

TEI Document Check

Connect agent

Guest access is available after setup. Full account linking verified by PowMCP: Claude only.

Edition check

Validate one TEI P5 edition against its RNG grammar and the beyond-schema Schematron layer.

A base TEI-All check usually finishes in under ten seconds. Applying a declared project schema adds a live schema fetch, so the sample run usually takes twenty to thirty seconds.

TEI document source

Only the active source is sent. You can switch without losing what you entered.

Publicly fetchable with no login.

Declared project schema (optional)

Applied only when the declared schema is hosted on www.tei-c.org or dracor.org. The base TEI-All grammar and Schematron layer run either way.

Allowed range: 1–1000 · whole numbers

Most severe first. Left empty, up to 400 are returned.

Add TEI Document Check to your agent

Connect this app on its own. Add other PowMCP apps whenever your agent needs another job done.

Open the apps workspace A glowing app tile clicking into a slot on a dark agent device, with the PowMCP app box behind it

Connect directly

Choose your agent. Each button opens a new tab with only this app's endpoint ready to add.

Use another agent

Copy one ready-to-send prompt for any agent that supports remote MCP connections.

Manual endpoint, JSON, and terminal commands

For clients that require manual configuration, use this app-only endpoint, its JSON entry, or one terminal command.

ChatGPT: enable Developer mode in Settings → Security and login, then add this MCP endpoint from the Plugins page. Availability depends on your account and workspace policy. PowMCP has not yet verified ChatGPT account linking. OpenAI setup guide

https://powmcp.com/humanities-text-check/mcp
{
  "mcpServers": {
    "powmcp-humanities-text-check": {
      "type": "http",
      "url": "https://powmcp.com/humanities-text-check/mcp"
    }
  }
}

Terminal agents add this app with one command:

Claude Code
claude mcp add --transport http powmcp-humanities-text-check https://powmcp.com/humanities-text-check/mcp
Codex CLI
codex mcp add powmcp-humanities-text-check --url https://powmcp.com/humanities-text-check/mcp
Gemini CLI
gemini mcp add --transport http powmcp-humanities-text-check https://powmcp.com/humanities-text-check/mcp

Manage, disable, or remove this connection in your agent's own MCP settings. PowMCP does not label an external connection as installed without confirmation from that client.

Proof

What it does

Check a hosted or pasted public TEI edition against BOTH its RNG grammar and the beyond-schema XPath2 Schematron layer, with exact rule and location evidence

Validate one public TEI P5 XML document against its base RNG grammar (jing) AND the embedded TEI-All Schematron constraint layer (pointer-target existence and ordering, date and calendar consistency, co-occurrence and cardinality rules the grammar cannot express) evaluated by Saxon over the ISO Schematron XSLT2 skeleton, optionally applying the file's own allowlistedproject ODD schema, or compare two same-identity editions under the same applied project-schema canonical, with a clear grammar-and-Schematron-versus-scholarly-correctness boundary.

Category
Developer Tools

Request cost1 completed result

Guests get 50 lifetime app requests. Free accounts get 100 each calendar month.

Tools in this app

01

TEI Document Conformance Check

document_check

Validates one public TEI P5 XML document (fetched from a public HTTP(S) URL or pasted inline) against BOTH its base RNG grammar (jing, pinned tei_all.rng) AND the embedded TEI-All XPath2 Schematron constraint layer (Saxon-HE 10.9J over the ISO Schematron XSLT2 skeleton): pointer/date/co-occurrence/cardinality rules the grammar cannot express. By default (projectSchema auto) it also fetches and applies the file's own declared <?xml-model?> project ODD schema when its host is allowlisted (www.tei-c.org, dracor.org). Supply exactly one of url or body. Returns pass/fail as distinct rngValid, schematronClean, and overall conforms booleans, whether the project schema was applied and its resolved source, severity counts (rng-error / assert-failure / report-hit), bounded per-finding evidence (layer, rule test, message, and document location by element or line), a structural inventory (root, declared <?xml-model?> href, teiHeader presence, element and pointer counts), and distinguished absence states (not-xml vs not-tei; rng-invalid vs schematron-invalid; project-schema not-declared / host-not-allowlisted / unresolved / nonconformant). Use for one-document conformance and diagnosis: 'is this TEI valid', 'does it conform', 'what encoding errors does it have', 'find the broken cross-references and date problems the plain schema misses'. A conforms result means only that the bytes satisfied the RNG grammar and the Schematron layer at the named engine and schema versions; it never judges whether the transcription is accurate, the edition is scholarly correct, or the encoding choices are appropriate. A base grammar check returns in ~1-2s; a full base+project-schema run takes a little longer because of the live schema fetch. Always state whether the project schema was applied.

02

TEI Two-Edition Conformance Compare

document_compare

Runs the identical bounded validation against exactly two TEI editions and, only when both are well-formed TEI with the same applied project-schema canonical and a shared declared document identity (root xml:id or publicationStmt idno), reports which grammar errors and Schematron findings regressed (present in B, not A) or were resolved (present in A, not B), ranking by measured automated conformance only. Supply two inputs, each as a public HTTP(S) TEI URL (urlA/urlB) or a pasted TEI body (bodyA/bodyB). Select this whenever the user gives two TEI editions and asks what conformance changed: a re-encoding pass or the same edition before and after a fix. The tool reports a pair as not comparable when either input is not well-formed TEI, their applied project-schema canonicals differ, or shared document identity cannot be established; in that case it returns per-document summaries and a truthful comparability note, leaves regressions and resolved empty, and omits the cross-document ranking. For comparable inputs it returns the regressed and resolved findings keyed by layer, rule, and location plus a conformance ranking. It explicitly reports when findings or the difference table were truncated. The ranking orders automated conformance only: fewer findings never means an edition is a truer, better, or more scholarly transcription. It never judges transcription accuracy, scholarly correctness, or encoding appropriateness. Each document runs under the same ~16 MB download / ~8 MB paste limits and a shared deadline.

TEI Document Check questions

Scope and boundaries for TEI Document Check.

01What can I check with TEI Document Check?

Check the hosted DraCor TEI for Goethe's Faust with projectSchema set to auto, so the base TEI-All RNG and Schematron layers run and an allowlisted declared xml-model schema can also be applied; pasted TEI XML is accepted as an alternative source.

02How should I read the result?

Start with conforms and projectSchema.applied and state: conforms means well-formed TEI passed the base RelaxNG and Schematron layers plus any project schema that was actually applied. Fix the first grammar or assertion finding and rerun; an undeclared, disallowed, or unresolved project schema means only the base profile was checked, and truncated findings are incomplete. Compare revisions only when comparable confirms the same applied schema and shared declared document identity.

03What are its limits?

Project schemas are fetched only from the supported TEI or DraCor hosts, and the base profile still runs when none is applied. Conformance does not judge transcription accuracy, scholarly correctness, or semantic appropriateness; comparison requires matching applied schema identity and a shared declared document identity before diffing or ranking.