Sato Hub
MCP

Santiment MCP

Official OAuth-backed Santiment MCP for on-chain, social, and financial crypto metrics.

  • Sato Score65
  • ChainsMultichain
ActiveSelf-Reported

Santiment MCP is a MCP server by Santiment, with no code activity tracked. Sato Score 65/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 Santiment MCP →

No code activity tracked

Listed from santiment.net on 2026-07-13. Install: not attempted. Evidence →

Next step

Watch Santiment MCP

One email if what we observe changes — its endpoint stops answering, 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 https://api.santiment.net/mcp 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

Santiment MCP is the official hosted connector to Santiment's Sanbase platform, offering timeseries access to 30+ metrics across 500+ assets: price/volume/volatility, on-chain activity, developer activity, and social-sentiment data. Agents authenticate via OAuth 2.0 with PKCE against a Santiment account, so a builder plugs it in for market-screening or sentiment-monitoring agents. Free accounts get core metrics; paid tiers unlock deeper on-chain and advanced metrics.

Sato Score

65/100· Medium

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

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

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Evidence — listed vs checked · what the words mean

Listed from santiment.net on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedacademy.santiment.netas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedsantiment.netas of 2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedacademy.santiment.netas of 2026-07-20
MCP endpoint answersanswered — 8 tools listedobservedapi.santiment.net2026-10-15
Daily check record44 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asHosted API (Remote MCP, OAuth 2.0 PKCE)confidence 0.90self-reportedacademy.santiment.netas of 2026-07-14
Works withClaude.ai, Claude Desktop, Claude Code CLI, ChatGPTconfidence 0.90self-reportedacademy.santiment.netas of 2026-07-14
Sato Score65/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 — as documented by the project, not run by us

Runtime: Hosted MCP endpoint (no local install)

claude mcp add santiment --transport http https://api.santiment.net/mcp
Remote MCP server URL https://api.santiment.net/mcp (add as custom connector; name "Santiment")

You supply: Santiment account; OAuth 2.0 authorization-code flow with PKCE on first use (no keys in config)

Add to CursorAdd to VS Code
claude mcp add --transport http satohub-santiment-mcp https://api.santiment.net/mcp

A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

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

Tool inventory — 8 tools, probed live 2026-10-15

  • assets_by_metric_tool — A powerful metrics-based project filtering and sorting tool that works with cryptocurrency assets based on their metrics and allows for ordered, paginated results. The tool allows for filtering asset
  • combined_trends_tool — Combined trends tool that fetches trending words, stories, and documents in parallel. This tool provides a unified view of all trending data - words with their documents and stories - in a single res
  • fetch_insights_tool — Fetch full text content for specific santiment crypto insights IDs
  • fetch_metric_data_tool — Fetch metric timeseries for one metric and one or many slugs, or for a text search term. Defaults: last 30 days (time_period="30d"), interval="1d". Pass `text` instead of `slugs` to get a social met
  • insight_discovery_tool — List Santiment insights (analyst-written crypto articles) published in a lookback window. Returns metadata only — id, title, tags, author, link, published_at, prediction — never the article body. ##
  • metrics_and_assets_discovery_tool — Catalog lookup: which metrics and which crypto assets (slugs) Santiment supports, and whether a given metric exists for a given asset. Returns names and metadata only — it never returns metric values
  • show_chart — Render a Santiment chart with an asset's price (OHLC) plus an optional overlay metric in a second pane. The widget that consumes this tool is built on the Santiment chart library (lightweight-charts u
  • trending_stories_tool — Fetch current trending crypto stories with sentiment analysis ## When to use vs `combined_trends_tool` Prefer this tool when only stories are needed: it is the cheap, fast path and has no per-tool r
Answers a handshake
yes · 2026-10-15
Answers a call
not asked — no tool is named as a read (list_/get_/search_)

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

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

100%of 45 checks since 2026-09-01 succeeded
Currently responding for 64 days
Succeeded
66
Failed
25
Their error
0
Unattributed
25

State changed on 2026-07-19 (responding → unclear), 2026-08-13 (unclear → 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. 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. The rate above leaves those checks out; the counts include them.

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
8
from the server's own tools/list · 29/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
Multichain
Agent types
MCP Server, Data Provider
Open source
Unknown
Pricing
Free tier for core metrics; paid tiers for full on-chain depth and advanced metrics
Deploys as
Hosted API (Remote MCP, OAuth 2.0 PKCE)
Works with
Claude.ai, Claude Desktop, Claude Code CLI, ChatGPT
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.

#sentiment-data#on-chain-metrics#market-data#oauth#mcp
See something inaccurate or outdated?Submit a correction →

Listing History

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

  1. Aug 13, 2026
    Sato Score tier: Low → Medium
    Score 25 → 62.
  2. Jul 20, 2026
    Edited: mcp endpoint url
  3. Jul 20, 2026
    Edited: deploy spec
  4. Jul 19, 2026
    Edited: mcp endpoint url
  5. Jul 18, 2026
    Sato Hub began tracking this listing
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Santiment MCP

Is Santiment MCP open source?
Unknown. Sato Hub has not found a public repository or a license statement for Santiment MCP as of 2026-10-15.
Which chains does Santiment MCP support?
Santiment MCP lists support for Multichain as of 2026-10-15.
Is Santiment MCP still maintained?
Sato Hub tracks no commit or release for Santiment MCP; it cannot say whether it is maintained.
How do I install or run Santiment MCP?
Hosted MCP endpoint (no local install). Install: claude mcp add santiment --transport http https://api.santiment.net/mcp. Entry: Remote MCP server URL https://api.santiment.net/mcp (add as custom connector; name "Santiment"). This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://api.santiment.net/mcp (Streamable HTTP, OAuth)).
Is Santiment MCP verified on Sato Hub?
Sato Hub holds one earned check for Santiment MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, 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. "Santiment MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/santiment-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.