1 maintainer
Metadata
1 maintainer
Release files for mcp-server-imessage 0.0.4
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 | |
|---|---|---|---|---|
| mcp_server_imessage-0.0.4.tar.gz | 11.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_imessage-0.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 23.6 kB
Release files / mcp_server_imessage-0.0.4.tar.gz
| Download URL | mcp_server_imessage-0.0.4.tar.gz |
|---|---|
| Size | 11.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7300a548a5c553d72c4f5a39bddbf0a9dbe5319c782b8823b1577da3aa0e8210
|
|
BLAKE2b-256 checksum How to use checksums |
47db887839ab50f0fe470ee03dd41d36256a19aca34238d93a78f9262f6a9522
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Release files / mcp_server_imessage-0.0.4-py3-none-any.whl
| Download URL | mcp_server_imessage-0.0.4-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6b50fe21855c81e821ae8d560b5ef0263fd9c9058b2315781cafa1c7e0a00ac6
|
|
BLAKE2b-256 checksum How to use checksums |
d1ff2cfdc30e6d3e0e369b212ec7f431d345d2024753cd110f7d61d94d3e1997
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.16
|
Security for mcp-server-imessage 0.0.4
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
