Solentic
Zero-custody Solana staking MCP server with 26 tools for staking, unstaking, validator lookup, and APY data.
- Sato Score50
- ChainsSolana
Solentic is a partly open-source wallet infrastructure on Solana, with last code activity on 2026-06-14 (Quiet). Latest release on 2026-03-30. Sato Score 50/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
See how to install Solentic →Last commit Jun 14, 2026 · Last release Mar 30, 2026
Listed from glama.ai on 2026-07-19. Install: failed on 2026-10-15. Evidence →
Next step
Watch Solentic
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on blueprint-infrastructure/solentic-mcp before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Solentic wraps Blueprint's Agentic Staking API as an MCP server for Solana staking operations — stake, unstake, withdraw, validator info, APY, and epoch timing — plus unsigned-transaction builders so an agent can sign locally rather than delegating custody. Documentation is solid (tool tables, OpenAPI spec, Docker setup) but the project has minimal external adoption to date (zero stars/forks at time of review).
Sato Score
50/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 20/35
- Code transparency
- 12/20
- Interface verifiability
- 0/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 10/15
- Independent verification
- 2/10
Evidence — listed vs checked · what the words mean
Listed from glama.ai on 2026-07-19. Install: failed on 2026-10-15.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Solana | self-reported | solentic.theblueprint.xyz | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | glama.ai | as of 2026-10-21 |
| Recent activity | last release 2026-03-30 · last commit 2026-06-14 | observed | github.com/blueprint-infrastructure/solentic-mcp | 2026-10-21 |
| Install works | did not complete at the install stepa measurement of the documented path, often a stale README — not a judgement of the software | observed | github.com/blueprint-infrastructure/solentic-mcp | 2026-10-15 |
| Website answers | answered (HTTP 200) | observed | glama.ai | 2026-10-21 |
| Daily check record | 49 of 50 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Deploys as | remote (hosted endpoint), local (stdio)confidence 0.80 | self-reported | github.com/blueprint-infrastructure/solentic-mcp | as of 2026-07-27 |
| Docs | https://solentic.theblueprint.xyz/docsconfidence 0.90 | self-reported | github.com/blueprint-infrastructure/solentic-mcp | as of 2026-07-27 |
| Sato Score | 50/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — we ran this on Oct 15, 2026 and the install step did not complete — the commands below are the project's own, and they may simply have moved on
Runtime: Node.js (npx package) or hosted Streamable HTTP endpoint
install: install failed: npm error 404 Not Found - GET https://registry.npmjs.org/@mbrassey%2fsolentic-mcp - Not found | npm error 404 | npm error 404 '@mbrassey/solentic-mcp@*' is not in this registry. | npm error 404 | npm error 404 Note that you can also install from a | npm error 404 tarball, folder, http url, or git url.
ran: mkdir -p /app || exit 1; cd /app || exit 1; npm init -y >/dev/null 2>&1; npm install --no-fund --no-audit @mbrassey/solentic-mcp
entry: skipped (install failed)
ran: cd /app; d=/app/node_modules/@mbrassey/solentic-mcp; [ -d "$d" ] || d="$(npm root -g)/@mbrassey/solentic-mcp"; node --input-type=module -e "const fs=await import('node:fs');const dir=process.argv[1];let pj={};try{pj=JSON.parse(fs.readFileSync(dir+'/package.json','utf8'))}catch{}let bin=pj.bin;if(typeof bin==='string')bin={b:bin};const rel=bin&&Object.values(bin)[0];if(rel){const {spawnSync}=await import('node:child_process');const p=dir+'/'+rel;let h='';try{h=fs.readFileSync(p).subarray(0,128).toString('latin1')}catch{}const l1=h.slice(0,Math.max(0,h.indexOf(String.fromCharCode(10))));const na
npx @mbrassey/solentic-mcp
{"mcpServers": {"solentic": {"url": "https://solentic.theblueprint.xyz/mcp"}}}You supply: No client-side env vars documented for the hosted/stdio setup. RISK: the stake/unstake/withdraw tools accept a Solana secret key at call time, forwarded over HTTPS to the Blueprint server for in-memory signing (README states it is not stored/logged, but this is a private-key-handling flow).
MCP invocation: hosted https://solentic.theblueprint.xyz/mcp (Streamable HTTP) or npx @mbrassey/solentic-mcp (stdio, local build: npm install && npm run build && node dist/server.js)
Read from the project’s own docs as of 2026-10-15. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 89
- Failed
- 2
- Their error
- 0
- Unattributed
- 2
State changed on 2026-07-26 (responding → unclear), 2026-07-27 (unclear → responding), 2026-09-08 (responding → unreachable from our probe), 2026-09-09 (unreachable from our probe → responding).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.
Last 30 days — to 2026-10-21, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Solana
- Agent types
- MCP server
- Open source
- Partial
- Deploys as
- remote (hosted endpoint), local (stdio)
- Last checked
- 2026-10-21
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Solentic fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are Onchain Agents?
Listing History
Recorded changes to Solentic's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Oct 15, 2026Verified: deploy spec
- Jul 27, 2026Auto-enriched: docs url, deployment options
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Edited: description short
- Jul 19, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Coinbase AgentKit
ActiveCoinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.
Hyperliquid
ActiveOnchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.
Jupiter
ActiveSolana swap aggregator that routes trades across DEXs via a widely used API and SDKs.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Solentic
- Is Solentic open source?
- Partly. Some of Solentic is published as source (https://github.com/blueprint-infrastructure/solentic-mcp) and some is not. Checked as of 2026-10-21.
- Which chains does Solentic support?
- Solentic lists support for Solana as of 2026-10-21.
- Is Solentic still maintained?
- The most recent code activity Sato Hub observed was on 2026-06-14 (last commit 2026-06-14, last release 2026-03-30), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Solentic?
- Node.js (npx package) or hosted Streamable HTTP endpoint. Install: npx @mbrassey/solentic-mcp. Entry: {"mcpServers": {"solentic": {"url": "https://solentic.theblueprint.xyz/mcp"}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (hosted https://solentic.theblueprint.xyz/mcp (Streamable HTTP) or npx @mbrassey/solentic-mcp (stdio, local build: npm install && npm run build && node dist/server.js)).
- Is Solentic verified on Sato Hub?
- No independent verification is on record for Solentic; its verification status is "Unverified" and its Sato Score is 50 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Solentic — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/solenticData last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.