carve-mcp

Official

by markup-carve

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Render Carve

carve_render

Read-only

Convert Carve documents to HTML, Markdown, plain text, or ANSI with loss reporting. Choose presets, extensions, and sanitization for safe, controlled rendering.

Instructions

Render Carve to HTML, Markdown, plain text, or ANSI terminal text, with loss reporting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`preset`	No	portable lowercases IDs and transliterates where possible; static-html is HTML-only.	default
`source`	Yes	Document source (maximum 1000000 UTF-8 bytes)
`target`	Yes
`extensions`	No	Opt-in extensions; semantic-spans is HTML-only.
`allowRawHtml`	No	Pass trusted raw HTML through on HTML output. Disabled by default.
`sanitizeUrls`	No	Report blocked authored URL schemes as render losses. A dangerous scheme is always blanked; this server never emits one.
`strictLosses`	No	Fail instead of returning output when a raw-format node would be dropped.
`asciiHeadingIds`	No	Heading ID policy; explicit values override the preset.
`maxRenderLosses`	No	Maximum detailed losses to return.
`smartTypography`	No	false is source; { quotes: false } keeps typed quotes only.
`lowercaseHeadingIds`	No	Lowercase generated heading IDs; explicit values override the preset.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`value`	Yes
`losses`	Yes
`truncated`	Yes
`totalLosses`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.1.8Oct 15, 2026

changedInput schema / properties / sanitizeUrls / description

Previous value: -"Block dangerous authored URL schemes. Keep enabled for untrusted input."New value: +"Report blocked authored URL schemes as render losses. A dangerous scheme is always blanked; this server never emits one."

addedInput schema / properties / smartTypography / anyOf

Added value: +[
+  {
+    "enum": [
+      "glyph",
+      "source"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "quotes": {
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  }
+]

changedInput schema / properties / smartTypography / description

Previous value: -"Render typographic glyphs or the punctuation the author typed."New value: +"false is source; { quotes: false } keeps typed quotes only."

removedInput schema / properties / smartTypography / enum
```
Removed value: -[
-  "glyph",
-  "source"
-]
```
removedInput schema / properties / smartTypography / type
```
Removed value: -"string"
```

Changed10 schema fields changedv0.1.2Sep 6, 2026

addedInput schema / properties / allowRawHtml

Added value: +{
+  "default": false,
+  "description": "Pass trusted raw HTML through on HTML output. Disabled by default.",
+  "type": "boolean"
+}

addedInput schema / properties / asciiHeadingIds

Added value: +{
+  "description": "Heading ID policy; explicit values override the preset.",
+  "enum": [
+    "off",
+    "fold",
+    "strict"
+  ],
+  "type": "string"
+}

addedInput schema / properties / extensions

Added value: +{
+  "default": [],
+  "description": "Opt-in extensions; semantic-spans is HTML-only.",
+  "items": {
+    "enum": [
+      "autolink",
+      "semantic-spans",
+      "wikilinks"
+    ],
+    "type": "string"
+  },
+  "maxItems": 3,
+  "type": "array"
+}

addedInput schema / properties / lowercaseHeadingIds

Added value: +{
+  "description": "Lowercase generated heading IDs; explicit values override the preset.",
+  "type": "boolean"
+}

addedInput schema / properties / maxRenderLosses

Added value: +{
+  "description": "Maximum detailed losses to return.",
+  "maximum": 10000,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / preset

Added value: +{
+  "default": "default",
+  "description": "portable lowercases IDs and transliterates where possible; static-html is HTML-only.",
+  "enum": [
+    "default",
+    "portable",
+    "static-html"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sanitizeUrls

Added value: +{
+  "default": true,
+  "description": "Block dangerous authored URL schemes. Keep enabled for untrusted input.",
+  "type": "boolean"
+}

addedInput schema / properties / smartTypography

Added value: +{
+  "description": "Render typographic glyphs or the punctuation the author typed.",
+  "enum": [
+    "glyph",
+    "source"
+  ],
+  "type": "string"
+}

addedInput schema / properties / strictLosses

Added value: +{
+  "default": false,
+  "description": "Fail instead of returning output when a raw-format node would be dropped.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "losses": {
+      "items": {},
+      "type": "array"
+    },
+    "totalLosses": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "value": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "value",
+    "losses",
+    "totalLosses",
+    "truncated"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 5, 2026

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the safe read-only profile (readOnlyHint=true, destructiveHint=false), so safety is covered. The description adds the non-obvious 'loss reporting' trait, but does not explain what a loss is or that strictLosses can turn one into a failure, leaving meaningful behavior to the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence that names the operation, the source resource, the four output targets, and the loss-reporting trait up front. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and 91% schema coverage plus safety annotations, most burden is carried by structured fields, and the description covers the output modes adequately. The gap is routing: for an 11-parameter tool amid many carve_* siblings, no indication of when to use this over carve_parse or carve_format is given.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 91%, so the schema already documents nearly every parameter (preset, extensions, sanitizeUrls, strictLosses, etc.). The description adds nothing parameter-specific, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Render) and resource (Carve) plus the concrete output formats it produces, which is more precise than a bare 'render'. It does not, however, distinguish itself from siblings like carve_parse or carve_format, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description names output formats but gives no when-to-use guidance, no prerequisites, and no comparison against the crowded sibling set (carve_parse, carve_format, carve_lint). An agent must guess when rendering is the right call versus parsing or formatting.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server