Triplex schema contracts MCP server
Commit Oct 30, 2026Infer and validate schema contracts for local CSV, TSV, and JSON Lines files without network access.
Also known as triplexanalytics/triplex, triplex-mcp
- Stars
- 0
- Tools
- 2
- Downloads, 30 days
- —
- Latest version
- 0.48.1
- Last commit
- Oct 30, 2026
- License
- Apache-2.0
What is Triplex schema contracts MCP?
Triplex schema contracts is an MCP server. Infer and validate schema contracts for local CSV, TSV, and JSON Lines files without network access. It exposes 2 tools, such as schema_infer, schema_validate.
Summary generated from the project's README
About Triplex schema contracts MCP server
Triplex schema contracts provides a way for coding agents to analyze and verify data structures within local files. This MCP server operates entirely through stdio transport, meaning it runs as a local process on your machine. It does not require a network connection, external servers, or configuration files to function, ensuring that all data processing stays within your existing trust boundary.
Developers can use this server to interact with CSV, TSV, and JSON Lines files. The server provides two primary tools: schema_infer, which generates a schema contract from a local file path, and schema_validate, which checks a file against an existing .triplex.yaml contract. Because the tools are read-only, they allow an AI client to understand data formats without modifying the underlying source files.
What you can do with it
- 1Local data analysisUse the server to process files without sending any data over a network.
Written from the project's README. Every use case is checked against a quote from it.
Triplex schema contracts MCP tools 2
Detected from the READMEschema_inferschema_validate
| schema_infer | — | |
| schema_validate | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabletriplexanalytics/triplex is public and reachablegithub.com/triplexanalytics/triplex ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-30github.com/triplexanalytics/triplex ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model2 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubtriplex-mcp
MCP (Model Context Protocol) server over SchemaCast, stdio transport only.
A coding agent (Claude Code or any other MCP client)
launches this as a local process and talks to it over its own stdin/stdout,
same trust boundary as apps/triplex-cli: no network, no server, nothing
here reads bytes over the wire.
Tools
schema_infer(path, sample_rows?): infers a schema contract from a local file (triplex_schemacast::infer_schema_from_path).schema_validate(schema_path, input_path, sample_rows?): checks a local file against a.triplex.yamlcontract (triplex_schemacast::validate_path).
Both are read-only and take a local file path. anonymize isn't exposed
yet.
Run
cargo install triplex-mcp
triplex-mcp
From a checkout of this repository: cargo run -p triplex-mcp.
Speaks newline-delimited JSON-RPC 2.0 on stdin/stdout. Point an MCP client's stdio transport at this binary. No flags, no config file.
Build/test
Ordinary workspace crate: cargo build -p triplex-mcp, cargo test -p triplex-mcp, cargo clippy -p triplex-mcp --all-targets. Covered by the
root cargo test --workspace/CI already; there is no separate Makefile target.
MCP registry
The official MCP registry lists servers by name and points MCP clients to the package to install; for this server, that package is this crate on crates.io. The registry confirms that the crate belongs to the entry by reading the line below in the published README, so it has to stay:
mcp-name: io.github.triplexanalytics/triplex-mcp
Triplex schema contracts MCP questions
What tools does Triplex schema contracts MCP provide?
It exposes 2 tools, including schema_infer, schema_validate.