chemdb-common
Shared library for chemistry database MCP servers. Provides SQLAlchemy models, sync utilities, and CLI tools used by grandmofty-mcp and catapult-mcp.
Features
- Pydantic models — typed schemas for MOFs, reactions, isotherms
- SQLAlchemy ORM — SQLite and PostgreSQL support
- Sync framework — pull data from remote APIs (mofdb-client, Zenodo, Materials Project)
- CLI —
chemdbcommand for database management
Installation
uv pip install -e .
# With PostgreSQL support:
uv pip install -e ".[postgres]"
Usage
chemdb sync # sync all data sources
chemdb stats # show database statistics
Dependencies
- pydantic — data validation
- sqlalchemy — ORM
- typer — CLI framework
- httpx — HTTP client for API calls
License
LGPL-3.0-or-later — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for chemdb-common 0.2.2
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 | |
|---|---|---|---|---|
| chemdb_common-0.2.2.tar.gz | 11.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| chemdb_common-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.2 kB
Release files / chemdb_common-0.2.2.tar.gz
| Download URL | chemdb_common-0.2.2.tar.gz |
|---|---|
| Size | 11.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e363eef152ace00ad3751e67e47d2836a5e91212d691a25b89fd81cea55bb71
|
|
BLAKE2b-256 checksum How to use checksums |
20ef168a7c0f162fd22eb2bebcb311f1ed10c2cc3ad5c07148ca34fdb3c2e563
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 7, 2026.
Transparency logRelease files / chemdb_common-0.2.2-py3-none-any.whl
| Download URL | chemdb_common-0.2.2-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4d68c412d76fa9c04da279a6c1c16317953de701b20a5804b23b1a17631cad53
|
|
BLAKE2b-256 checksum How to use checksums |
50cea9716e1f0ecb022d24ea5126976da5b434e37ee903b86b4726d9e7a12a33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 7, 2026.
Transparency logSecurity for chemdb-common 0.2.2
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for chemdb_common-0.2.2.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 Apr 7, 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.
