io.github.intenttext/intenttext-mcp
NPM · @INTENTTEXT/MCP-SERVER · SCANNED SEP 25
Parse, validate, query, and render IntentText (.it) documents for AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 107 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 196 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 724 tokens (~80/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_template" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.intenttext/intenttext-mcp server?
io.github.intenttext/intenttext-mcp runs locally as an npm package, launched with npx -y @intenttext/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @intenttext/mcp-server
claude mcp add intenttext-intenttext-mcp -- npx -y @intenttext/mcp-server
{
"mcpServers": {
"intenttext-intenttext-mcp": {
"command": "npx",
"args": [
"-y",
"@intenttext/mcp-server"
]
}
}
} {
"servers": {
"intenttext-intenttext-mcp": {
"command": "npx",
"args": [
"-y",
"@intenttext/mcp-server"
]
}
}
} codex mcp add intenttext-intenttext-mcp -- npx -y @intenttext/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"intenttext-intenttext-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@intenttext/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add intenttext-intenttext-mcp --command npx --arg -y --arg @intenttext/mcp-server
mcp_servers:
intenttext-intenttext-mcp:
command: "npx"
args: ["-y", "@intenttext/mcp-server"] {
"McpServers": {
"intenttext-intenttext-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@intenttext/mcp-server"
]
}
}
} assistant mcp add intenttext-intenttext-mcp -t stdio -c npx -a -y @intenttext/mcp-server
{
"mcpServers": {
"intenttext-intenttext-mcp": {
"command": "npx",
"args": [
"-y",
"@intenttext/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/@intenttext/mcp-server@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 107 packages
| Packages resolved | 107 |
|---|---|
| Deprecated | 1 |
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
diff_documents ~76
Compare two versions of an IntentText document and return a semantic diff. Shows which blocks were added, removed, or modified between versions. More meaningful than a line diff — tells you what changed in the document's structure.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | yes | The updated IntentText source |
| before | string | yes | The original IntentText source |
No output schema declared.
No examples provided.
document_to_source ~73
Convert an IntentText JSON document back to .it source format. Use this when you have a document stored as JSON (e.g. from a database) and need to display or edit it as .it text.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | An IntentText document JSON object (as produced by parse_intent_text) |
No output schema declared.
No examples provided.
extract_workflow ~71
Extract the execution graph from an IntentText workflow document. Returns steps in topological order, dependency relationships, parallel batches, and gate positions. Use this to understand how to execute a workflow before running it.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | IntentText source containing workflow blocks (step:, decision:, gate:, etc.) |
No output schema declared.
No examples provided.
merge_template ~99
Merge an IntentText template (containing {{variable}} placeholders) with a data object. Returns the merged .it source with all variables resolved. Use this to generate documents from templates.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | JSON object with values to substitute into the template |
| render | string | – | Optionally render the merged result. Default: none (returns .it source) |
| template | string | yes | IntentText template source with {{variable}} placeholders |
No output schema declared.
No examples provided.
parse_intent_text ~90
Parse an IntentText (.it) source string into a structured JSON document. Returns the complete document with metadata and typed blocks array. Use this when you have raw .it text and need to inspect or process its structure.
| Name | Type | Req | Description |
|---|---|---|---|
| safe | boolean | – | If true, never throw — returns warnings instead of errors. Default: true |
| source | string | yes | The IntentText source string to parse |
No output schema declared.
No examples provided.
query_document ~149
Query an IntentText document for specific blocks by type, content, or properties. Returns matching blocks as JSON. Use this to extract tasks, steps, decisions, or any other block type from a document.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Substring to search for in block content (case-insensitive) |
| limit | number | – | Maximum number of results to return |
| section | string | – | Only return blocks within this section (substring match on section title) |
| source | string | yes | IntentText source string |
| type | string | – | Block type to filter by (e.g. 'task', 'step', 'gate'). Comma-separated for multiple types: 'step,gate,decision' |
No output schema declared.
No examples provided.
render_html ~44
Render an IntentText source string to styled HTML. Returns a complete HTML string ready to display in a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | IntentText source string (.it format) |
No output schema declared.
No examples provided.
render_print ~50
Render an IntentText document to print-optimised HTML with @media print CSS. Applies font: and page: block settings. Suitable for PDF generation.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | IntentText source string |
No output schema declared.
No examples provided.
validate_document ~72
Validate an IntentText document for semantic correctness beyond syntax. Checks for broken step references, missing required properties, unresolved variables, and workflow logic errors. Returns a list of errors and warnings. Always call this after generating a workflow document to catch issues before execution.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | yes | IntentText source string to validate |
No output schema declared.
No examples provided.
What is the io.github.intenttext/intenttext-mcp server?
io.github.intenttext/intenttext-mcp is listed in the public MCP registry as io.github.intenttext/intenttext-mcp. Parse, validate, query, and render IntentText (.it) documents for AI agents. This page covers its npm package (@intenttext/mcp-server).
Is the io.github.intenttext/intenttext-mcp server safe to use?
io.github.intenttext/intenttext-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.intenttext/intenttext-mcp server expose?
io.github.intenttext/intenttext-mcp exposes 9 tools: parse_intent_text, render_html, render_print, merge_template, validate_document, and 4 more. Their descriptions and schemas cost roughly 724 tokens of context every time the server is loaded.
Is the io.github.intenttext/intenttext-mcp server still maintained?
io.github.intenttext/intenttext-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.intenttext/intenttext-mcp server under?
io.github.intenttext/intenttext-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.