io.github.SebastianMaciel/jsx-notation
NPM · JSX-NOTATION · SCANNED SEP 20
JSXN encoder/decoder — compact notation for React/Next.js files, optimized for LLMs
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
- 32 of 111 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 206 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1198 tokens (~299/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.SebastianMaciel/jsx-notation MCP server?
io.github.SebastianMaciel/jsx-notation runs locally as an npm package, launched with npx -y jsx-notation. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · jsx-notation
claude mcp add sebastianmaciel-jsx-notation -- npx -y jsx-notation
{
"mcpServers": {
"sebastianmaciel-jsx-notation": {
"command": "npx",
"args": [
"-y",
"jsx-notation"
]
}
}
} {
"servers": {
"sebastianmaciel-jsx-notation": {
"command": "npx",
"args": [
"-y",
"jsx-notation"
]
}
}
} codex mcp add sebastianmaciel-jsx-notation -- npx -y jsx-notation
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sebastianmaciel-jsx-notation": {
"type": "local",
"command": [
"npx",
"-y",
"jsx-notation"
],
"enabled": true
}
}
} openclaw mcp add sebastianmaciel-jsx-notation --command npx --arg -y --arg jsx-notation
mcp_servers:
sebastianmaciel-jsx-notation:
command: "npx"
args: ["-y", "jsx-notation"] {
"McpServers": {
"sebastianmaciel-jsx-notation": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"jsx-notation"
]
}
}
} assistant mcp add sebastianmaciel-jsx-notation -t stdio -c npx -a -y jsx-notation
{
"mcpServers": {
"sebastianmaciel-jsx-notation": {
"command": "npx",
"args": [
"-y",
"jsx-notation"
]
}
}
} 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.
- 18 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.
- 16 Sept 26 −2
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → pass ▲ functional
- 7 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
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 20 Sept 2026 · Analysed npm/jsx-notation@0.1.6
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 111 packages
| Packages resolved | 111 |
|---|---|
| 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 →
decode_jsxn Decode JSXN to code ~136
Decodes JSXN compact notation back into standard JSX/TSX or HTML source code. Use "snippet" mode for JSXN body fragments (just the template). Use "file" mode for complete JSXN files with imports, types, hooks, etc. Use format "html" to decode to HTML output.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The JSXN notation to decode |
| format | string | – | "jsx" for JSX/TSX (default), "html" for HTML output |
| mode | string | – | "file" for complete files with imports/hooks/logic, "snippet" for JSXN body fragments |
No output schema declared.
No examples provided.
encode_jsxn Encode code to JSXN ~143
Encodes raw JSX/TSX source code or HTML into JSXN compact notation (~40% fewer tokens). Use "snippet" mode for JSX fragments (just the template). Use "file" mode for complete React/Next.js files with imports, types, hooks, etc. Use format "html" to encode HTML source.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The JSX/TSX/HTML source code to encode |
| format | string | – | "jsx" for JSX/TSX (default), "html" for HTML source |
| mode | string | – | "file" for complete files with imports/hooks/logic, "snippet" for JSX-only fragments |
No output schema declared.
No examples provided.
read_jsxn Read file as JSXN ~139
Reads a React/Next.js file (.jsx, .tsx, .js, .ts), HTML file (.html), or SVG file (.svg) from disk and returns its JSXN-compressed representation (~40% fewer tokens). Use this instead of reading JSX/TSX files directly when you need to understand component structure, props, and rendering logic. For full files with imports/hooks/logic, the file-level encoding is used automatically. For .html and .svg files, the HTML encoder is used.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute or relative path to the .jsx/.tsx/.js/.ts/.html/.svg file to encode |
No output schema declared.
No examples provided.
write_jsxn Write JSXN as file ~780
Decodes JSXN notation and writes the resulting JSX/TSX or HTML to a file on disk. Creates parent directories if needed. Writes to .jsx/.tsx/.js/.ts/.html/.svg files. For .html and .svg files, decodes with HTML format (class attrs, void elements, SVG self-closing, etc.). ## JSXN Format Reference JSXN is a compact notation for React/Next.js code that saves ~40% tokens. ### File-level headers - `@I module: default Name, x, y` → `import Name, { x, y } from "module"` - `@I "styles.css"` → `import "styles.css"` - `@T module: Type1` → `import type { Type1 } from "module"` ### Directives - `"use client"` / `"use server"` → passed through as-is ### Types - `Name { field: Type }` → `interface Name { field: Type }` - `Name = Type | Other` → `type Name = Type | Other` ### Function blocks - `export default Name(params)` → function signature - `@state count = 0` → `const [count, setCount] = useState(0)` - `@ref inputRef = null` → `const inputRef = useRef(null)` - `name = useHook(args)` → `const name = useHook(args)` - `variable = expr` → `const variable = expr` - `let variable = expr` → preserved as `let` - `---` → separator; everything after is the JSX return body ### JSX body notation - **Alias headers** (optional): `@C Button=B`, `@P onClick=k`, `@S items-center=ic` - **Elements**: `tag.class1.class2#id {prop:val, flag} "text"` or `(expr)` - **Implicit div**: `.className` (div is omitted when it has selectors) - **Nesting**: 1-space indentation per level - **Fragments**: `_` → `<>...</>` - **Conditionals**: `?cond > Element` → `{cond && (<Element />)}` - **Ternaries**: `?cond > A | B` → `{cond ? (<A />) : (<B />)}` - **Maps**: `*items > Element` → `{items.map(item => (<Element />))}` - **Text nodes**: `"Hello"` → raw text - **Expressions**: `(expr)` → `{expr}` - **Props**: `{key:value}` string for HTML attrs, `{key:expr}` expression otherwise - **Boolean props**: `{disabled}` → `disabled` - **Spread**: `{...props}` → `{...props}` - **Self-closing**: element with no chi…
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The JSXN notation to decode and write |
| path | string | yes | Target file path (.jsx, .tsx, .js, .ts, .html, or .svg) |
No output schema declared.
No examples provided.
What is the io.github.SebastianMaciel/jsx-notation MCP server?
io.github.SebastianMaciel/jsx-notation is an MCP server listed in the public MCP registry as io.github.SebastianMaciel/jsx-notation. JSXN encoder/decoder, compact notation for React/Next.js files, optimized for LLMs. This page covers its npm package (jsx-notation).
Is the io.github.SebastianMaciel/jsx-notation MCP server safe to use?
io.github.SebastianMaciel/jsx-notation scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.SebastianMaciel/jsx-notation MCP server expose?
io.github.SebastianMaciel/jsx-notation exposes 4 tools: read_jsxn, encode_jsxn, decode_jsxn, write_jsxn. Their descriptions and schemas cost roughly 1,198 tokens of context every time the server is loaded.
Is the io.github.SebastianMaciel/jsx-notation MCP server still maintained?
io.github.SebastianMaciel/jsx-notation is still listed as active in the MCP registry. We last reached this channel on 20 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.SebastianMaciel/jsx-notation MCP server under?
io.github.SebastianMaciel/jsx-notation declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.