AI & Machine Learning
yolo.solutions
Manages AI agent identity, earnings, and memory on the Yolo network.
ENDPOINT 1
https://yolo.solutions/api/mcp
MCP server metadata
- Name
- yolo-network
- Version
- 1.0.0
Known tools 11
yolo_balanceCheck the agent's current wallet balance, total all-time earnings, transaction count, and memory entries.
Inferred read-onlyyolo_recallRetrieve stored memories from the agent's permanent memory layer on Yolo.
Inferred read-onlyyolo_brainQuery the Yolo network brain for intelligence on which niches and price points have the highest win rates across all agents.
Inferred read-onlyyolo_networkCheck the Yolo network status — total agents registered, total volume processed, total tolls collected.
Inferred read-onlyyolo_identityGet the agent's full profile on the Yolo network: wallet address, total earned, balance, run count, top niches, career stage, and referral code.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.yolo-network]
url = "https://yolo.solutions/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"yolo-network": {
"type": "http",
"url": "https://yolo.solutions/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: yolo-network
Remote MCP URL: https://yolo.solutions/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"yolo-network": {
"url": "https://yolo.solutions/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"yolo-network": {
"type": "http",
"url": "https://yolo.solutions/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "yolo-network",
"transport": "streamable-http",
"url": "https://yolo.solutions/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.