bricksentry-mcp
The MCP server for bricksentry, the safety check for data changes in the AI era. This package only installs bricksentry with its MCP and Databricks extras and gives you one command, so agents can start the server with uvx:
uvx bricksentry-mcp --config /full/path/to/bricksentry.yml
Claude Code
claude mcp add bricksentry -- uvx bricksentry-mcp --config /full/path/to/bricksentry.yml
Claude desktop, Cursor and other clients (mcpServers config):
{
"mcpServers": {
"bricksentry": {
"command": "uvx",
"args": ["bricksentry-mcp", "--config", "/full/path/to/bricksentry.yml"]
}
}
}
Use a full path to bricksentry.yml: clients start the server from their own working folder. If an app can't find uvx, use its full path (which uvx).
bricksentry-mcp accepts the same options as bricksentry mcp, for example --transport streamable-http. Docs: bricksentry.org/docs/agents. License: Apache-2.0.
1 maintainer
Metadata
1 maintainer
Release files for bricksentry-mcp 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bricksentry_mcp-0.1.7.tar.gz | 5.6 kB | With provenance | Details for bricksentry_mcp-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bricksentry_mcp-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for bricksentry_mcp-0.1.7-py3-none-any.whl |
Total release size: 12.0 kB
Release files / bricksentry_mcp-0.1.7.tar.gz
| Download URL | bricksentry_mcp-0.1.7.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e229d0674760ac9811dc6f092a717676adef11d2c87cf655f547aeb39f8314b
|
|
BLAKE2b-256 checksum How to use checksums |
fbdbf79045a821721d117173f1bdefaaaf744ef64c7f16cb736f5b9b32bf4425
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logRelease files / bricksentry_mcp-0.1.7-py3-none-any.whl
| Download URL | bricksentry_mcp-0.1.7-py3-none-any.whl |
|---|---|
| Size | 6.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc16a090464af2566ab1d1ebd19750db4648940d352a4bd803eb2a19186b7205
|
|
BLAKE2b-256 checksum How to use checksums |
ed80ebe5b73f09b9ed4d35f42524dd19f2b5e7fc2005462a557a49c32a40389b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logSecurity for bricksentry-mcp 0.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for bricksentry_mcp-0.1.7.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 11, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
