Inclusio
No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked
Inclusio is an open-source publishing engine that emits accessible documents in formats including PDF/UA-2, WTPDF, and PDF/A-4f. It also supports C2PA, PAdES, and SLSA provenance, with CLI, package, and MCP server workflows for developers and publishers.
Inferred · not functionally tested
Overview
6 featuresPurpose: Producing accessible, standards-compliant documents with verifiable provenance across multiple output formats.
Inferred · not functionally tested
Audience: developers and publishers building accessible document workflows
Inferred · not functionally tested
Functions: data_extraction
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)
Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, api_only, self_hosted
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
Inclusio is an API design, testing & docs project. Inferred · not functionally tested: It focuses on producing accessible, standards-compliant documents with verifiable provenance across multiple output formats. Inferred · not functionally tested: Inclusio is an open-source project aimed at developers and publishers building accessible document workflows. Basis unknown · not verified: Inclusio is open source under the Open Source license. Basis unknown · not verified: It runs on the web, the command line, and API, and it can be self-hosted.
Behind Inclusio is Sébastien Rousseau. Inferred · not functionally tested: Key capabilities include PDF/UA-2 output, WTPDF output, and PDF/A-4f output. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- PDF/UA-2 output
- WTPDF output
- PDF/A-4f output
- Multi-format emission
- C2PA provenance
- PAdES signing
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
1What PulseGate has recorded for this listing
- Indexed10 Oct · 09:10 UTCio.github.sebastienrousseau/inclusio-mcp seen via MCP Registry (official)Source: MCP Registry (official) · Open
Frequently asked questions about Inclusio
- What is Inclusio?
- Inferred · not functionally tested: Inclusio focuses on producing accessible, standards-compliant documents with verifiable provenance across multiple output formats. It is catalogued under API design, testing & docs on PulseGate.
- Who is Inclusio for?
- Inferred · not functionally tested: Inclusio is an open-source project built for developers and publishers building accessible document workflows.
- Does Inclusio have a free plan?
- Basis unknown · not verified: Yes — Inclusio is open source under the Open Source license and free to use.
- What platforms does Inclusio run on?
- Basis unknown · not verified: Inclusio runs on the web, the command line, and API. It can also be self-hosted.
- Is Inclusio still maintained?
- Unverified. Inclusio has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
- What are alternatives to Inclusio?
- Similar projects tracked by PulseGate include MCP Stdio, oxml-mcp, and LeadHarbor MCP.MCP Stdiooxml-mcpLeadHarbor MCP
- Who develops Inclusio?
- Inclusio is developed by Sébastien Rousseau.
- Is Inclusio open source?
- Basis unknown · not verified: Yes — Inclusio is open source under the Open Source license.
Also in API design, testing & docs
Same category — not a similarity match