io.github.arpe-io/lakexpress-mcp

MCPcommunity
v0.1.6io.github.arpe-ioUnknownUpdated 5mo agoGitHub

MCP server for LakeXpress — automated database-to-cloud data pipeline as Parquet

A Model Context Protocol (MCP) server for LakeXpress — a database to Parquet export tool with sync management and data lake publishing. 14 subcommands supported: logdb management, config management, sync execution, status, and cleanup 5 source databases: SQL Server, PostgreSQL, Oracle, MySQL, MariaDB 6 log databases: SQL Server, PostgreSQL, MySQL, MariaDB, SQLite, DuckDB 6 storage backends:…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
5mo agoLast update
Package
Authorio.github.arpe-io
LicenseUnknown
Version0.1.6
Sourcemcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
DependenciesNot audited
Tool surface
Security scan✓ Cleanv0.1.6 · 2mo ago
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

A Model Context Protocol (MCP) server for LakeXpress — a database to Parquet export tool with sync management and data lake publishing. 14 subcommands supported: logdb management, config management, sync execution, status, and cleanup 5 source databases: SQL Server, PostgreSQL, Oracle, MySQL, MariaDB 6 log databases: SQL Server, PostgreSQL, MySQL, MariaDB, SQLite, DuckDB 6 storage backends: Local, S3, S3-compatible, GCS, Azure ADLS Gen2, OneLake 7 publish targets: Snowflake, Databricks, Fabric,…

Keywords
mcp