Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
Santiment is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Crypto market intelligence: social sentiment, on-chain, trending narratives & analyst insights.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http santiment-mcp https://api.santiment.net/mcp
# 2 — ask your agent for something these tools do
# assets_by_metric_tool, combined_trends_tool, fetch_insights_tool and 5 more
Santiment costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SAAll 1 server
santiment1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http santiment-mcp https://api.santiment.net/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 assets by a metric and sorting them according to that same metric in ascending or descending metric, or just to sort the assets by a metric without filtering. This tool allows you to discover projects tha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| aggregation | string | no | Method for aggregating metric data over the specified time period. Determines how multiple data points within the time window are combined into a single value for comparison. Common aggregation metho |
| from | string | yes | Start date/time for the analysis period. Defines the beginning of the time window for metric aggregation. Accepts ISO 8601 datetime strings (e.g., "2024-01-01T00:00:00Z") or relative time expressions |
| metric | string | yes | The metric to use for screening projects. This determines what aspect of each project will be analyzed. Common metrics include: 'price_usd', 'marketcap_usd', 'volume_usd', 'dev_activity', 'social_volu |
| operator | string | no | Comparison operator that determines how projects are filtered based on the metric and threshold. Absolute value operators (compare current values): - greater_than - Include projects where the aggre |
| page | integer | yes | Page number for paginated results. Used to retrieve specific pages when the result set is large. Starts from 1 (first page). Combine with page_size to control how many results are returned per page. U |
| page_size | integer | yes | Number of projects to return per page (max 100). Controls the size of each paginated response. |
| sort | string | yes | Sort order for the filtered results based on the aggregated metric values. - "asc" - Ascending order (lowest values first, e.g., cheapest prices first) - "desc" - Descending order (highest values firs |
| threshold | no | The numeric threshold value used for filtering projects. The meaning depends on the operator: For absolute operators (:greater_than, :less_than): - The actual metric value to compare against (e.g., 1 | |
| to | string | yes | End date/time for the analysis period. Defines the end of the time window for metric aggregation. Accepts ISO 8601 datetime strings (e.g., "2024-12-31T23:59:59Z") or relative time expressions (e.g., " |
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 response across all crypto projects. ## When to use vs trending_stories_tool This is a superset of trending_stories_tool: same stories, plus trending words, their context and AI-generated bull/bear
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_stories | boolean | no | Include trending stories in the response. Defaults to true. |
| include_words | boolean | no | Include trending words in the response. Defaults to true. |
| size | integer | no | Number of items per category to return (max 10). Defaults to 10. |
| time_period | string | no | Time period for trending data (e.g., '1h', '6h', '1d', '7d'). This parameter defines how far back to look for trending data. Only the 2 most recent trend periods are returned (1h periods up to '1d', 6 |
Fetch full text content for specific santiment crypto insights IDs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| insight_ids | yes | Array of santiment crypto insights IDs to fetch full content for (max 10) |
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 metric for any word or phrase (e.g. how often "sold" was mentioned), not just for an asset. Use this when the assets are already known and the values over time matter. For the opposite direction — "whic
| Parameter | Type | Required | Notes |
|---|---|---|---|
| interval | string | no | The interval between two data points in the timeseries data (e.g., '5m', '1h', '1d'). The format is: <number><suffix>, where: - <number> is an integer - <suffix> is one of: - m (minutes) - h (hou |
| metric | string | yes | Metric name to fetch (e.g., 'price_usd'). IMPORTANT: Before fetching data, verify metric names by calling the metrics_and_assets_discovery_tool first. Only metrics listed there are supported. Do not |
| slugs | array | no | Pass either slugs or text, not both. List of slug identifiers (e.g., ["bitcoin"], ["bitcoin", "ethereum"], etc.). Accepts at most 10 slugs at a time. Only metrics that have `supports_many_slugs |
| text | string | no | Pass either slugs or text, not both. A search term (word or phrase, e.g. "sold" or "etf approval") to compute the metric for, instead of an asset. Supported only by social metrics such as social_ |
| time_period | string | no | How far back in time to fetch the data for (e.g., '7d', '30d', '90d'). This parameter defines the range of metric data to fetch - from <time_period> time ago up until now. Defaults to 30d. |
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. ## When to use - The user asks what Santiment analysts have written or published recently. - As step 1 of a two-step read: discover ids here, then pass them to fetch_insights_tool for the full text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| time_period | string | no | Lookback window as <integer><unit>, unit one of s, m, h, d, w, y (e.g. '12h', '7d', '30d', '90d', '1y'). Insights published in now - time_period .. now are returned. Absolute dates and future rang |
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 or timeseries. ## When to use - Resolve a name before any data call: turn "Ethereum" into the slug ethereum, or "active addresses" into the metric daily_active_addresses. - Check availability
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric | string | no | Santiment id of one metric: lowercase snake_case, e.g. 'price_usd', 'marketcap_usd', 'daily_active_addresses'. One metric per call; lists are not accepted. Alone: returns all assets that support this |
| slug | string | no | Santiment slug of one crypto asset: lowercase, hyphen-separated, e.g. 'bitcoin', 'ethereum', 'avalanche'. Not a ticker - use 'bitcoin', not 'BTC'. One slug per call; lists are not accepted. Alone: re |
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 under the hood), so the response is render-ready — the client just feeds each series entry into the chart unchanged. ## Parameters - slug — asset slug (e.g. bitcoin, ethereum). Defaults to `b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| overlay | string | no | Optional metric to overlay in a second pane. Must be one of the catalog names (see tool description). |
| primary | string | no | Primary series — 'price' for candlestick OHLC, or a metric name from the catalog. Defaults to 'price'. |
| range | string | no | Time range. One of: 24h, 7d, 30d, 90d, 1y. Defaults to 30d. |
| slug | string | no | Asset slug (e.g. 'bitcoin', 'ethereum'). Defaults to 'bitcoin'. |
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 rate-limit sub-cap. combined_trends_tool is a superset — same stories plus trending words, their context and AI-generated bull/bear summaries — but it calls an LLM, so it is slower and capped much lo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | integer | no | Number of trending stories to return (max 10). Defaults to 10. |
| time_period | string | no | Time period for trending stories (e.g., '1h', '6h', '1d', '7d'). This parameter defines how far back to look for trending stories. Defaults to '1h' (last hour). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Santiment or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Santiment can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.