MCP server for Blueprint Agentic Staking — native Solana staking infrastructure for AI agents
MCP server for Blueprint Agentic Staking — native Solana staking infrastructure for AI agents. The solentic mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
26 MCP tools wrapping the Blueprint REST API. One-shot tools (stake, unstake, withdraw) handle the full lifecycle in a single call — the secret key is sent to the Blueprint server over HTTPS for in-memory signing and is never stored or logged. Verify via verify_code_integrity. Advanced tools (create_stake_transaction, etc.) return unsigned transactions for agents that prefer local signing.
Everything the assistant can do here goes through one of these:
stake — Stake SOL — one call, confirmed signature returnedunstake — Deactivate stake — one call, confirmedwithdraw — Withdraw SOL — one call, confirmedget_validator_info — Validator profile, commission, active stake, APYget_staking_apy — Live APY breakdown (base + Jito MEV)get_performance_metrics — Vote success, uptime, skip rate, epoch creditsget_infrastructure — Server hardware specs (both servers)generate_wallet — Local wallet generation code (JS, Python, CLI)check_balance — SOL balance for any walletcheck_stake_accounts — List stake accounts for a walletcheck_withdraw_ready — Per-account withdrawal readiness with ETAsimulate_stake — Project staking rewards with compound interest@mbrassey/solentic-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Solentic MCP's toolset — stake, unstake, withdraw and 11 more — is a fair guide to whether it matches your workflow. It is maintained by blueprint-infrastructure; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| stake | Stake SOL — one call, confirmed signature returned |
| unstake | Deactivate stake — one call, confirmed |
| withdraw | Withdraw SOL — one call, confirmed |
| get_validator_info | Validator profile, commission, active stake, APY |
| get_staking_apy | Live APY breakdown (base + Jito MEV) |
| get_performance_metrics | Vote success, uptime, skip rate, epoch credits |
| get_infrastructure | Server hardware specs (both servers) |
| generate_wallet | Local wallet generation code (JS, Python, CLI) |
| check_balance | SOL balance for any wallet |
| check_stake_accounts | List stake accounts for a wallet |
| check_withdraw_ready | Per-account withdrawal readiness with ETA |
| simulate_stake | Project staking rewards with compound interest |
| get_staking_summary | Complete portfolio dashboard (single call) |
| get_epoch_timing | Current Solana epoch progress and timing |
{
"mcpServers": {
"solentic": {
"url": "https://solentic.theblueprint.xyz/mcp"
}
}
}Configuration as documented by the project. Restart the client after saving.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.