io.github.blockpal1/stylobridge
OCI · GHCR.IO/BLOCKPAL1/STYLOBRIDGE:1.0.2 · 2 COMPONENTS · SCANNED SEP 20
Air-gapped Markdown/PDF to Word converter with brand templates and audit logging.
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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 181 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 918 tokens (~306/item across 3 items; 3 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 Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the io.github.blockpal1/stylobridge MCP server?
io.github.blockpal1/stylobridge runs locally as a container image, launched with docker run --rm -i ghcr.io/blockpal1/stylobridge:1.0.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/blockpal1/stylobridge:1.0.2
claude mcp add blockpal1-stylobridge -- docker run --rm -i ghcr.io/blockpal1/stylobridge:1.0.2
{
"mcpServers": {
"blockpal1-stylobridge": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/blockpal1/stylobridge:1.0.2"
]
}
}
} {
"servers": {
"blockpal1-stylobridge": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/blockpal1/stylobridge:1.0.2"
]
}
}
} codex mcp add blockpal1-stylobridge -- docker run --rm -i ghcr.io/blockpal1/stylobridge:1.0.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"blockpal1-stylobridge": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/blockpal1/stylobridge:1.0.2"
],
"enabled": true
}
}
} mcp_servers:
blockpal1-stylobridge:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/blockpal1/stylobridge:1.0.2"] {
"McpServers": {
"blockpal1-stylobridge": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/blockpal1/stylobridge:1.0.2"
]
}
}
} {
"mcpServers": {
"blockpal1-stylobridge": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/blockpal1/stylobridge:1.0.2"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 0
- Stability: 0.97 → pass security
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 oci/ghcr.io/blockpal1/stylobridge:1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
analyze_and_create_template ~225
Analyze a corporate document and create a reusable brand template for Word conversion. Give this tool any existing branded .docx file and it will extract the styling (fonts, colors, headers, table formats, logos) into a reusable template. All future documents converted with convert_to_docx will automatically match your corporate brand when this template is applied. USE THIS TOOL when the user wants to: - Make all documents look like an existing branded document - "Use the same styling as this doc" or "match this format" - Create a brand template from an existing Word document - Extract styling from a corporate document for reuse - Set up consistent branding for document conversion Args: source_docx: Path to an existing branded .docx document. template_name: Name for the new template (without .docx extension). Returns: Success message with the template name, or an error message.
| Name | Type | Req | Description |
|---|---|---|---|
| source_docx | string | yes | – |
| template_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
convert_to_docx ~516
Convert Markdown or PDF to a professionally styled Word (.docx) document. USE THIS TOOL whenever the user wants to: - Convert Markdown (.md) to Word / DOCX - Convert PDF to Word / DOCX - Create a Word document from text or a file - Export or save content as .docx - Generate a styled or branded Word document IMPORTANT — choosing content vs input_path: - ALWAYS prefer the content parameter. If you have markdown text in the conversation, or can read the file yourself, pass the text via content. This is the most reliable path. - Only use input_path for files already inside the StyloBridge workspace directory. Uploaded files, temp paths, and files outside the workspace will be REJECTED with "Access denied". - If the user uploaded a file: read it yourself first, then pass the text via content. Do NOT pass the upload path to input_path. Produces publication-ready output with styled headings, formatted tables (blue headers, alternating row shading), table of contents, and professional typography. Optionally applies a corporate brand template. If the user asks to match an existing document's style, first use analyze_and_create_template to create a template from that document, then pass it here as template_name. Use list_templates to see what brand templates are already available. Args: input_path: Only for files already in the StyloBridge workspace directory. Do NOT pass uploaded file paths or temp paths — they will fail. Use content instead. format: Source format — 'markdown' or 'pdf'. Defaults to 'markdown'. Only relevant when using input_path. content: PREFERRED. Pass markdown text directly — works for any content in the conversation or that you can read from a file. output_filename: Filename for the output document (default: 'document.docx'). Used when converting from conten…
| Name | Type | Req | Description |
|---|---|---|---|
| content | – | – | – |
| format | string | – | – |
| include_toc | boolean | – | – |
| input_path | – | – | – |
| output_filename | string | – | – |
| template_name | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_templates ~132
List available corporate brand templates for Word document conversion. USE THIS TOOL whenever the user wants to: - See what templates are available - Check which brand styles they can apply - Browse document templates before converting - Know what formatting options exist Returns all .docx brand templates that can be applied when converting documents with convert_to_docx. Each template enforces consistent corporate fonts, colors, logos, and page layouts across all generated Word documents. Requires an Enterprise license. Returns: JSON array of available template filenames, or an error message.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the io.github.blockpal1/stylobridge MCP server?
io.github.blockpal1/stylobridge is an MCP server listed in the public MCP registry as io.github.blockpal1/stylobridge. Air-gapped Markdown/PDF to Word converter with brand templates and audit logging. This page covers its container image (ghcr.io/blockpal1/stylobridge:1.0.2).
Is the io.github.blockpal1/stylobridge MCP server safe to use?
io.github.blockpal1/stylobridge scores 40 out of 100 on VerifyMCP. 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.blockpal1/stylobridge MCP server expose?
io.github.blockpal1/stylobridge exposes 3 tools: convert_to_docx, list_templates, analyze_and_create_template. Their descriptions and schemas cost roughly 873 tokens of context every time the server is loaded.
Is the io.github.blockpal1/stylobridge MCP server still maintained?
io.github.blockpal1/stylobridge 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.