Sato Hub
MCP

Tari MCP Servers

Official Minotari wallet and node MCP servers for local agent access to Tari blockchain data and transactions.

  • Sato Score66
ActiveSelf-ReportedActive · today

Tari MCP Servers is an open-source MCP server by Tari Project, with last code activity on 2026-10-14 (Active). Latest release on 2026-10-13. Sato Score 66/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Tari MCP Servers →

Last commit Oct 14, 2026 · Last release Oct 13, 2026 (v6.2.0-pre.1) · ★ 500

Listed from github.com/tari-project/tari on 2026-07-13. Install: failed on 2026-09-21. Evidence →

Website ↗GitHub ↗

Next step

Watch Tari MCP Servers

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 tari-project/tari 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

The Tari Project ships two official Model Context Protocol servers inside its core repo: Minotari MCP Wallet, giving agents read-only wallet data access plus constrained transaction capabilities, and Minotari MCP Node, exposing chain metadata, peer info, and network state. Both bind locally by default with permission separation, rate limiting, audit logging, and optional confirmation for value transfers. A builder runs these alongside a local Minotari node/wallet to let an agent query or operate on Tari from an MCP client.

Sato Score

66/100· Medium

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

Maintenance & liveness
35/35
Code transparency
19/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
9/15
Independent verification
3/10
View verification & embed badge →History →How the Sato Score works

Evidence — listed vs checked · what the words mean

Listed from github.com/tari-project/tari on 2026-07-13. Install: failed on 2026-09-21.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reportedgithub.com/tari-project/tarias of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedgithub.com/tari-project/tarias of 2026-10-15
Recent activitylast release 2026-10-13 · last commit 2026-10-14observedgithub.com/tari-project/tari2026-10-15
Install worksdid not complete at the entry stepa measurement of the documented path, often a stale README — not a judgement of the softwareobservedgithub.com/tari-project/tari2026-09-21
Website answersanswered (HTTP 200)observedgithub.com/tari-project/tari2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asself-hosted, local, docker, binaryconfidence 0.85self-reportedgithub.com/tari-project/tarias of 2026-09-21
Sato Score66/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

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 Sep 21, 2026 and the entry step did not complete — the commands below are the project's own, and they may simply have moved on

Runtime: rust

entry: entry probe failed: error: could not find `Cargo.toml` in `/app` or any parent directory
ran: d="$(ls -d /app/*/ 2>/dev/null | head -1)"; cd /app/tari 2>/dev/null || { [ -n "$d" ] && cd "$d"; } || cd /app || exit 1; cargo build --quiet

git clone https://github.com/tari-project/tari.git
cd tari
cargo build --release -p minotari_mcp_wallet
minotari_mcp_wallet --mcp-enabled

You supply: A running minotari_console_wallet --enable-grpc (and a synced Tari node) — the MCP server proxies to it, it is not a standalone binary

MCP invocation: minotari_mcp_wallet --mcp-enabled (local HTTP at 127.0.0.1:8081; minotari_mcp_node also present for node-level queries)

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-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

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. 46 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. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
66
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
Unknown
Agent types
MCP Server, Wallet
Open source
Yes
Deploys as
self-hosted, local, docker, binary
Last checked
2026-10-15

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#tari#minotari#wallet#self-hosted

Where Tari MCP Servers fits

WalletsData

Related concepts: How Agents Use Wallets, What Are Onchain Agents?, What Are MCPs? The Standard Way to Give Agents Tools

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from Tari MCP Servers, pulled from its GitHub and X.

Releasetari-project/tari2d ago

tari v6.2.0-pre.1

What's Changed fix(ledger): sign device sender-offset keys only through the reviewed metadata instruction by @SWvheerden in #8104 fix(key_manager): low-impact hardening from the key manager security analysis by @SWvheerden in #8106 fix(common_sqlite)!: owner-only database files, WAL set in create_pool, per-database profiles by @SWvheerden in #8107 fix(comms): bound memory held for stalled yamux pe

GitHub ↗
Releasetari-project/tari2d ago

tari v6.2.0-pre.0

What's Changed fix(jellyfish): reject non-monotonic versions in batch_put_value_set by @SWvheerden in #8092 fix: refuse to sign offline transactions that leave no change output by @SWvheerden in #8093 fix(jellyfish)!: remove public-API panics, bound traversal, check store integrity by @SWvheerden in #8094 feat(jellyfish)!: make the JMT hash scheme an explicit parameter by @SWvheerden in #8096 fix:

GitHub ↗
Releasetari-project/tari8d ago

tari v6.1.0

v6.1.0 (2026-10-07) What's Changed Features feat: rebootstrap peers when the DHT connection pool is starved in #8082 feat(sidechain): transaction commands carry their atom bytes in #8072 feat: display the TIP-004 backoff adjusted target difficulty in #8070 feat(sidechain): commit to a transaction merkle root from protocol version 1 in #8076 Bug Fixes fix: blame the block that failed in a reorg and

GitHub ↗
Releasetari-project/tari8d ago

tari v6.1.0-pre.1

What's Changed fix!: consensus limit on block body bytes by @SWvheerden in #8079 fix(grpc): bound the cost of GetTokensInCirculation by @SWvheerden in #8081 fix: narrow RandomX factory lock scope by @SWvheerden in #8080 feat: rebootstrap peers when the DHT connection pool is starved by @SWvheerden in #8082 feat(sidechain)!: transaction commands carry their atom bytes by @sdbondi in #8072 fix: name

GitHub ↗
Releasetari-project/tari10d ago

tari v6.1.0-pre.0

What's Changed fix: tari script hardening by @SWvheerden in #8065 fix(wallet): consistent address and memo sizing by @SWvheerden in #8068 feat: display the TIP-004 backoff adjusted target difficulty by @SWvheerden in #8070 fix!: tari_hashing audit remediation by @SWvheerden in #8071 fix!: update tari_crypto to 0.24 and return errors instead of Ok(false) from verification functions by @SWvheerden i

GitHub ↗
Releasetari-project/tari10d ago

tari v6.0.1

v6.0.1 (2026-10-05) What's Changed Features feat: harden mempool in #8055 feat: side-chain data consensus rules in #8067 feat(core): prove burn claims with a burn output proof instead of a kernel proof in #8054 feat(wallet): encode burn claim merkle proof as JSON instead of bincode in #8051 Bug Fixes fix: enforce decoder parity for bounded transaction types and validate every submission path in #8

GitHub ↗

Listing History

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

  1. Oct 13, 2026
    New release published
  2. Oct 9, 2026
    New release published
  3. Oct 8, 2026
    Crossed 500 GitHub stars
    499 → 500.
  4. Sep 21, 2026
    Auto-enriched: deployment options
  5. Jul 22, 2026
    19 releases tracked
    Showing the 2 most recent. Full release history is retained in the listing record.
  6. Jul 18, 2026
    Sato Hub began tracking this listing
  7. Jul 13, 2026
    Listed on Sato Hub

Compared with

Alternatives to Tari MCP Servers →

Appears in

Related Resources

Coinbase AgentKit

Active
Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain
Recent★ 1.3k

Hyperliquid

Active
VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid
Recent★ 506▸ Jun 2023

Model Context Protocol (MCP)

Active
Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown
Active★ 9.4k

Reference

QuestionsShowHide

Questions people ask about Tari MCP Servers

Is Tari MCP Servers open source?
Yes. Tari MCP Servers is open source under the BSD-3-Clause license; the repository is https://github.com/tari-project/tari. Checked as of 2026-10-15.
Which chains does Tari MCP Servers support?
Sato Hub has no confirmed chain list for Tari MCP Servers as of 2026-10-15; treat chain support as unknown.
Is Tari MCP Servers still maintained?
The most recent code activity Sato Hub observed was on 2026-10-14 (last commit 2026-10-14, last release 2026-10-13), 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 Tari MCP Servers?
rust. Install: git clone https://github.com/tari-project/tari.git && cd tari && cargo build --release -p minotari_mcp_wallet. Entry: minotari_mcp_wallet --mcp-enabled. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (minotari_mcp_wallet --mcp-enabled (local HTTP at 127.0.0.1:8081; minotari_mcp_node also present for node-level queries)).
Is Tari MCP Servers verified on Sato Hub?
No independent verification is on record for Tari MCP Servers; its verification status is "Self-Reported" and its Sato Score is 66 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Tari MCP Servers — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/tari-mcp

Data last refreshed 2026-10-15; 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.