Sato Hub
MCP

Deside MCP

MCP server for wallet-to-wallet messaging and agent identity resolution on Solana.

  • Sato Score65
  • ChainsSolana
ActiveUnverifiedActive · 11d ago

Deside MCP is an open-source MCP server on Solana, with last code activity on 2026-10-10 (Active). Sato Score 65/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 Deside MCP →

Last commit Oct 10, 2026

Listed from github.com/DesideApp/deside-docs on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21. Evidence →

Next step

Watch Deside MCP

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/mcp
Run Sato Hub Preflight on desideapp/deside-docs before I use it.
Full setup: Claude Code, Cursor, others →

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

Deside MCP lets AI agents and applications authenticate via a Solana wallet (OAuth 2.0 + PKCE with wallet signing) and send or read direct messages to other wallets and agents, plus resolve identity and look up an agent directory. It's listed in the Solana Foundation's AI-tooling index; the repo itself is a documented compatibility mirror with a published TypeScript SDK and a live endpoint, pointing to active infrastructure behind it.

Sato Score

65/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
16/20
Interface verifiability
8/10
Docs & demo
0/10
Listing transparency & provenance
6/15
Independent verification
0/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Sato Check

v0.1.4 · as of 2026-09-29
Does it take your key?
Asks for a key
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from github.com/DesideApp/deside-docs on 2026-07-19. Install: reproduced by Sato Hub on 2026-09-21.

ClaimValueEvidenceSourceChecked
Chains supportedSolanaself-reportedgithub.com/DesideApp/deside-docsas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedgithub.com/DesideApp/deside-docsas of 2026-10-21
Recent activitylast commit 2026-10-10observedgithub.com/DesideApp/deside-docs2026-10-21
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedraw.githubusercontent.com2026-09-21
MCP endpoint answersanswered, but declined an anonymous probeobservedmcp.deside.io2026-10-21
Daily check record0 of 50 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Takes your keyasks for a private key or seed phrasedeclaredsatohub.aias of 2026-09-29
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-29
Sato Score65/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-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 — reproduced in a container Sep 21, 2026

Runtime: Hosted MCP (Streamable HTTP) + Node.js >=20 SDK

npm install @desideapp/mcp-sdk
https://mcp.deside.io/mcp

MCP invocation: https://mcp.deside.io/mcp (hosted) — mcpServers config: {"deside":{"url":"https://mcp.deside.io/mcp"}}

Read from the project’s own docs as of 2026-09-21. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-23

0%of 51 checks since 2026-09-01 succeeded
Currently unreachable from our probe for 29 days
Succeeded
0
Failed
91
Their error
22
Unattributed
69

State changed on 2026-09-01 (unclear → failing), 2026-09-23 (failing → unreachable from our probe).

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

Share of OUR checks that succeeded
0%
7-day rolling; unattributable days are gaps · 7/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
65
as snapshotted that day · 29/30 days

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
Yes
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.

#mcp#messaging#identity#solana#agent-to-agent
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Deside MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 21, 2026
    Verified: deploy spec
  2. Jul 24, 2026
    Sato Hub began tracking this listing
  3. Jul 20, 2026
    Edited: mcp endpoint url
  4. Jul 19, 2026
    Edited: github url, website url
  5. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Deside MCP

Is Deside MCP open source?
Yes. Deside MCP is open source under the MIT license; the repository is https://github.com/DesideApp/deside-docs. Checked as of 2026-10-21.
Which chains does Deside MCP support?
Deside MCP lists support for Solana as of 2026-10-21.
Is Deside MCP still maintained?
The most recent code activity Sato Hub observed was on 2026-10-10 (last commit 2026-10-10), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Deside MCP?
Hosted MCP (Streamable HTTP) + Node.js >=20 SDK. Install: npm install @desideapp/mcp-sdk. Entry: https://mcp.deside.io/mcp. Sato Hub reproduced this install in a container on 2026-09-21. It runs as an MCP server (https://mcp.deside.io/mcp (hosted) — mcpServers config: {"deside":{"url":"https://mcp.deside.io/mcp"}}).
Is Deside MCP verified on Sato Hub?
Sato Hub holds one earned check for Deside MCP: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 65 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Deside MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/deside-mcp

Data 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.