Home / MCP registry index / io.github.blueprint-infrastructure/solentic
Blueprint Agentic Staking (Solentic)
io.github.blueprint-infrastructure/solentic in the official MCP registry.
Endpoint https://solentic.theblueprint.xyz/mcp. Source: github.com/blueprint-infrastructure/solentic-mcp.
The registry describes it as: Native Solana staking for AI agents. 26 MCP tools, one-shot signing, webhooks.
We read its 29 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
stake unstake withdraw get_validator_info get_staking_apy get_performance_metrics create_stake_transaction create_unstake_transaction withdraw_stake check_stake_accounts check_withdraw_ready get_verification_links generate_wallet check_balance submit_transaction get_infrastructure verify_transaction verify_code_integrity simulate_stake get_staking_summary donate get_epoch_timing check_address_type register_webhook list_webhooks delete_webhook set_staking_policy get_staking_policy delete_staking_policy
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-blueprint-infrastructure-solentic)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.