A previous release had provenance metadata, but this release does not. View details.
myai-mcp
MCP server for the MyAi decentralized AI inference network.
Gives any MCP-compatible agent (Claude Desktop, Cursor, etc.) access to:
myai_chat— run inference through the decentralized networkmyai_list_models— see what models are online right nowmyai_list_agents— browse active provider nodes and their hardwaremyai_network_stats— live network health and job activitymyai_wallet_balance— check MYAI token balance for any addressmyai_hire_agent— pin a job to a specific provider node
Install
uvx myai-mcp
Or with pip:
pip install myai-mcp
Claude Desktop config
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"myai": {
"command": "uvx",
"args": ["myai-mcp"],
"env": {
"MYAI_API_KEY": "your-api-key-here",
"MYAI_BASE_URL": "https://api.myaitoken.io"
}
}
}
}
Get an API key at myaitoken.io.
Example usage (once connected)
Ask Claude:
"Use myai_list_models to see what's available, then use myai_chat with qwen2.5-14b to summarize this document."
"Check the MyAi network stats and tell me how many providers are online."
"What's the MYAI balance for 0x454F85B685BBe6C1257b218eE40782d17dFacA9b?"
Links
- Provider guide — run a node and earn MYAI
- Agent registry — browse the live network
- Docs
- Discord
v0.2.0 — Zero-config
You can now uvx myai-mcp with no env vars. The MCP auto-issues a free-tier API key on first call (100 free completions per machine) and caches it at ~/.myai/key. Set MYAI_API_KEY to use your own key.
Metadata
Release files for myai-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| myai_mcp-0.2.0.tar.gz | 6.3 kB | Without provenance | Details for myai_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| myai_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for myai_mcp-0.2.0-py3-none-any.whl |
Total release size: 13.0 kB
Release files / myai_mcp-0.2.0.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | myai_mcp-0.2.0.tar.gz |
|---|---|
| Size | 6.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
22ec3943a2be4f23768febd7cf86770cec53828d76caf0857ff95d3759ad6631
|
|
BLAKE2b-256 checksum How to use checksums |
9dd466e4ba2f1def331f9bb862b4db24b470f948b5c9da63a53ae76c284c0dc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Release files / myai_mcp-0.2.0-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | myai_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
332e4e29ada461e9dff632f1c059efa692b23bd9c7ea2716fc08f2d5ae6debc3
|
|
BLAKE2b-256 checksum How to use checksums |
dce5b8db683e7fcd89cc5f7f2fd1ffb1cb8bdd146af11ca626aef97caf72e9d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.12
|
Security for myai-mcp 0.2.0
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.1.0 2 files With provenance
- Added 0.2.0 2 files Without provenance
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.