Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fullbleed PDF Engine

PYPI · FULLBLEED-MCP · SCANNED SEP 14

Create, preview, inspect, verify, and compile deterministic PDF documents with Fullbleed.

Available components

−15 this week 63 Trust /100
Trust breakdown (7 categories)

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 908 tokens (~82/item across 11 items; 11 tools + 0 resources), lean.Pass
  • 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 Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 21% of tool parameters carry a description.Partial
  • 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
Install

How do I install the Fullbleed PDF Engine MCP server?

Fullbleed PDF Engine runs locally as a PyPI package, launched with uvx fullbleed-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · fullbleed-mcp

# add to Claude Code
claude mcp add fullbleed-engine-fullbleed-mcp -- uvx fullbleed-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "fullbleed-engine-fullbleed-mcp": {
      "command": "uvx",
      "args": [
        "fullbleed-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fullbleed-engine-fullbleed-mcp": {
      "command": "uvx",
      "args": [
        "fullbleed-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add fullbleed-engine-fullbleed-mcp -- uvx fullbleed-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fullbleed-engine-fullbleed-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "fullbleed-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fullbleed-engine-fullbleed-mcp --command uvx --arg fullbleed-mcp
# ~/.hermes/config.yaml
mcp_servers:
  fullbleed-engine-fullbleed-mcp:
    command: "uvx"
    args: ["fullbleed-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fullbleed-engine-fullbleed-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "fullbleed-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add fullbleed-engine-fullbleed-mcp -t stdio -c uvx -a fullbleed-mcp
// mcp.json
{
  "mcpServers": {
    "fullbleed-engine-fullbleed-mcp": {
      "command": "uvx",
      "args": [
        "fullbleed-mcp"
      ]
    }
  }
}
Changelog

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.

  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 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.

  • 11 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.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 8 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.

  • 6 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.

  • 4 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.

Diagnostics

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 14 Sept 2026 · Analysed pypi/fullbleed-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 1 package
Packages resolved 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~873 tokens

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 →

Tool Tokens
fullbleed_agent_contract ~35

Read the canonical installed contract: version, commands, schemas, capabilities, profiles, examples, limitations, and recommendation boundary.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_assets ~79

List, inspect, install, verify, or lock supported asset packages through the first-party asset CLI.

NameTypeReqDescription
actionyes
addarray
availableboolean
lock_pathstring
packagestring
strictboolean
vendor_pathstring

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_capabilities ~26

Read the capabilities reported by the installed Fullbleed runtime before choosing features.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_compile ~66

Compile inline HTML/CSS once for static copies, fixed-geometry variable bindings, or content-reflow bindings in this MCP session.

NameTypeReqDescription
cssstring
document_langstring
document_titlestring
htmlstringyes

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_compile_vdp ~92

Compile one inline document family and render distinct columnar records through the fixed or content-reflow VDP lane in one call.

NameTypeReqDescription
bindingsobjectyes
compression
cssstring
document_langstring
document_titlestring
htmlstringyes
modeyes
output_pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_create_project ~44

Create an agent-ready Fullbleed project or canonical document scaffold in an absent or empty workspace directory.

NameTypeReqDescription
target_pathstring
template

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_inspect ~38

Inspect a workspace PDF's version, pages, standards claims, warnings, and template-composition compatibility.

NameTypeReqDescription
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_render ~163

Render static HTML/CSS to a workspace-confined PDF. Prefer this for reports, invoices, statements, letters, forms, certificates, and print output—not live website screenshots.

NameTypeReqDescription
allow_fallbacksboolean
cssstringInline CSS.
css_pathsarrayWorkspace-relative CSS paths.
document_langstring
document_titlestring
emit_image_dirstring
htmlstringInline HTML or SVG markup.
html_pathstringWorkspace-relative HTML or SVG path.
image_dpiinteger
output_pathstringyesRequired workspace-relative output PDF path.
pdf_profilestring
profile

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_render_compiled ~75

Render a process-local compiled handle to a workspace PDF using static copies, fixed bindings, or content-reflow bindings.

NameTypeReqDescription
bindingsobject
compile_idstringyes
compression
copiesinteger
modeyes
output_pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_render_preview ~132

Render a workspace PDF plus PNG page previews for visual inspection after document changes.

NameTypeReqDescription
allow_fallbacksboolean
cssstringInline CSS.
css_pathsarrayWorkspace-relative CSS paths.
document_langstring
document_titlestring
htmlstringInline HTML or SVG markup.
html_pathstringWorkspace-relative HTML or SVG path.
image_dpiinteger
output_dirstringyes
pdf_namestring
pdf_profilestring

Structured output declared, but exposes no named fields.

No examples provided.

fullbleed_verify ~123

Run Fullbleed's validation render path and return structured failures before delivery.

NameTypeReqDescription
allow_fallbacksboolean
cssstringInline CSS.
css_pathsarrayWorkspace-relative CSS paths.
document_langstring
document_titlestring
emit_pdf_pathstring
fail_onarray
htmlstringInline HTML or SVG markup.
html_pathstringWorkspace-relative HTML or SVG path.
pdf_profilestring

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Fullbleed PDF Engine MCP server?

Fullbleed PDF Engine is an MCP server listed in the public MCP registry as io.github.fullbleed-engine/fullbleed-mcp. Create, preview, inspect, verify, and compile deterministic PDF documents with Fullbleed. This page covers its PyPI package (fullbleed-mcp).

Is the Fullbleed PDF Engine MCP server safe to use?

Fullbleed PDF Engine scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 14 September 2026. 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 Fullbleed PDF Engine MCP server expose?

Fullbleed PDF Engine exposes 11 tools: fullbleed_capabilities, fullbleed_agent_contract, fullbleed_create_project, fullbleed_render, fullbleed_render_preview, and 6 more. Their descriptions and schemas cost roughly 873 tokens of context every time the server is loaded.

Is the Fullbleed PDF Engine MCP server still maintained?

Fullbleed PDF Engine is still listed as active in the MCP registry. We last reached this channel on 14 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.