The author of this package has not provided a project description
Metadata
Release files for vicsia-outlook-mcp 0.1.6
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 | |
|---|---|---|---|---|
| vicsia_outlook_mcp-0.1.6.tar.gz | 24.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vicsia_outlook_mcp-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 41.9 kB
Release files / vicsia_outlook_mcp-0.1.6.tar.gz
| Download URL | vicsia_outlook_mcp-0.1.6.tar.gz |
|---|---|
| Size | 24.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eae9458e9124667a82cc835d932222ddd904f670e4e7450e935888dad1039814
|
|
BLAKE2b-256 checksum How to use checksums |
6e3be977d32773ccf02c4ec714def20dbc6030686009716e0259268ca97d61c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Release files / vicsia_outlook_mcp-0.1.6-py3-none-any.whl
| Download URL | vicsia_outlook_mcp-0.1.6-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
caee316fc4cdd93c11fabe2e34a06a61a759e97561153f98ec0140432bacb99c
|
|
BLAKE2b-256 checksum How to use checksums |
58572ffbe012e3b91b7f7be9ecc7a07199bdb317e8f8ce58e3fd209731b90e4b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.8
|
Security for vicsia-outlook-mcp 0.1.6
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.