ParquetHarmonize

io.github.tfitzgerwitnessPublished by GitHub account tfitzgerwitnessv0.1.0Updated Oct 27, 2026

Harmonize Parquet schemas; ordinary unions are free, residual reconciliation is x402-gated.

VerifiedStreamable HTTPWeb executableFiles & StorageData & Analytics

Overview

AI-generated overview

Remote MCP server with one tool that merges 2–8 base64-encoded Parquet files into a harmonized schema, with paid reconciliation for incompatible schemas.

What you can do
  • Harmonize Parquet files: submit 2 to 8 base64-encoded Parquet files and get a schema-harmonized result.
  • Handle ordinary compatible unions at no cost.
  • Reconcile residual schema differences, which requires an x402 payment of 0.03 USDC on Base.
When to use it
Useful when an assistant has several Parquet files with differing schemas and needs them combined into one consistent dataset, especially when the differences are simple compatible unions. Consider it only if you are willing to pay in USDC for the harder reconciliation cases.
Requirements
A remote streamable HTTP endpoint; no local package or runtime is needed. No authentication, environment variables or headers are declared. Parquet files must be supplied base64-encoded. For residual schema reconciliation, an x402 payment of 0.03 USDC on the Base network is required.
Before you install
The tool can incur real spending: residual schema reconciliation costs 0.03 USDC on Base via x402, so a wallet and funds are involved. Files are sent base64-encoded to a third-party remote service, so avoid submitting sensitive data. No authentication is declared, so anyone reaching the endpoint can call it.

Installation

In SourceWeft

  1. Open ParquetHarmonize in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.tfitzgerwitness%2Fparquetharmonize/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "parquetharmonize": {
      "type": "http",
      "url": "https://parquetharmonize-v01-x402-262046248169.northamerica-northeast2.run.app/mcp"
    }
  }
}

Tools

1

harmonize_parquet

ParquetHarmonize

Harmonize 2-8 base64-encoded Parquet files. Ordinary compatible unions are free. Residual schema reconciliation requires an x402 payment of 0.03 USDC on Base.

Parametersfiles_base64required

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.