Styxis
Company
Knowledge

Styxis Labs · Open source · Local MCP

Truthound Local — reproducible data checks

Inspect actual CSV and Parquet results from the published Local MCP package, with synthetic input and a script to reproduce the checks.

The 2026-11-02 example runs published Truthound Core 3.3.1 through MCP stdio. Local plugin 0.1.7 uses the same Core version. The input is three synthetic rows and two columns, written as both CSV and Parquet.

Six calls completed: check_file, profile_file and scan_pii on each format. Both quality checks reported failure with two issues: one null check and one duplicate check. A completed execution does not mean the dataset passed.

Profiling reported three rows, two columns and 33.3% missing email values. PII screening reported an email finding with estimated count two, using the first 1,000 non-null values. This small fixture does not measure detection accuracy on other datasets.

The outside-directory call was denied, source files were unchanged, and raw synthetic email values were absent from returned results. Existing desktop directory grants were not changed. The linked receipt contains the actual bounded outputs.

Follow the reproducible example below to review the synthetic input and rerun the script. These are execution observations, not independent endorsements, performance comparisons or evidence of AI search recommendations. Registry publication and web indexing are separate states.

Verified with the published package

A three-row, two-column synthetic dataset was checked as CSV and Parquet. Six calls verified failed quality checks for nulls/duplicates, aggregate profiles and sampled email findings. An outside-directory call was denied and raw values were absent from results.

Execution evidence for Core 3.3.1; not a PII accuracy benchmark or an AI search visibility score.

Sources, installation and evidence

Evidence date:

Explore commercial Truthound Depot