# SentimentFX (remote · api.sentimentfx.org)

FinBERT news sentiment and price history for 42 crypto, FX, stock, ETF and commodity tickers.

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.sentimentfx.org`: 68/100 (this document), [markdown](https://verifymcp.io/servers/org-sentimentfx-market-sentiment/api.md), [page](https://verifymcp.io/servers/org-sentimentfx-market-sentiment/api)

## Channel facts

- Endpoint: `https://api.sentimentfx.org/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 867 tokens (~144/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SentimentFX MCP server?

SentimentFX is a hosted endpoint at https://api.sentimentfx.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-sentimentfx-market-sentiment 'https://api.sentimentfx.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-sentimentfx-market-sentiment": {
      "url": "https://api.sentimentfx.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-sentimentfx-market-sentiment": {
      "type": "http",
      "url": "https://api.sentimentfx.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-sentimentfx-market-sentiment]
url = "https://api.sentimentfx.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-sentimentfx-market-sentiment": {
      "type": "remote",
      "url": "https://api.sentimentfx.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-sentimentfx-market-sentiment --url 'https://api.sentimentfx.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-sentimentfx-market-sentiment:
    url: "https://api.sentimentfx.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-sentimentfx-market-sentiment": {
      "Transport": "http",
      "Url": "https://api.sentimentfx.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-sentimentfx-market-sentiment -t streamable-http -u 'https://api.sentimentfx.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-sentimentfx-market-sentiment": {
      "type": "http",
      "url": "https://api.sentimentfx.org/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-06 (score 61)

First indexed and scored.

## MCP tools (6)

### `list_tickers` (~103 tokens)

List every asset SentimentFX tracks.

    Cheap (free — doesn't hit the billing meter).  Returns two groups:
    `primary` (5 crypto + 7 FX pairs — the ones with full sentiment coverage
    across the primary RSS feeds), and `background` (US equities, ETFs,
    commodity futures — coverage is thinner but real).  Use the exact ticker
    string from either group as the `ticker` arg to the other tools.

### `get_usage` (~96 tokens)

Introspect your API key: calls used this month, included allowance,
    remaining credits, and when the counter resets.

    Free — doesn't hit the billing meter.  Mirrors `GET /v1/usage`
    (MCP_MIRRORS_V1: change both together).  Useful before a large batch of
    `get_sentiment`/`get_summary` calls to check you have credit headroom.

### `get_sentiment` (~136 tokens)

Return the most recent FinBERT-scored headlines for `ticker`.

    Each headline has a `sentiment_score` in [-1, +1] (positive_prob -
    negative_prob) and a categorical `sentiment_label`.  Costs 1 API credit
    per 25 headlines actually returned — same billing as
    GET /v1/sentiment/{ticker}.  An empty result costs nothing.

    `limit` is capped at 100.  Titles come back reverse-chronological so the
    first item is the freshest.

Input parameters:

- `limit` (integer)
- `ticker` (string, required)

### `get_summary` (~117 tokens)

Return daily aggregated sentiment for `ticker` over the last `days`.

    Each entry has `avg_sentiment` (unweighted mean of that day's scores),
    `article_count`, and a directional `label` (positive / negative /
    neutral, thresholded at ±0.1).  Costs 1 API credit per day actually
    returned — same as GET /v1/summary/{ticker}.  A window with no coverage
    costs nothing.

Input parameters:

- `days` (integer)
- `ticker` (string, required)

### `get_prices` (~154 tokens)

Return daily close prices for `ticker` over the last `days`, in the
    ticker's native currency -- see the `currency` field on the response.

    Costs 1 API credit per day actually returned — same as
    GET /v1/prices/{ticker}.  Prices come
    back reverse-chronological.  Crypto is GBP (yfinance BTC-GBP etc.), FX
    pairs are a raw exchange rate in the pair's native convention (e.g.
    USDJPY is yen per dollar), and everything else (stocks/ETFs/commodity
    futures) is native USD -- there is no currency conversion.

Input parameters:

- `days` (integer)
- `ticker` (string, required)

### `get_correlation` (~141 tokens)

180-day Pearson correlation between daily sentiment shifts and next-day
    price returns for `ticker`.

    Returns Pearson `r`, `p_value`, `n_days` overlapping, a 95% confidence
    interval (Fisher z), and a categorical `strength` (strong / weak /
    inconclusive).  Costs 1 API credit — same as GET /v1/correlation/{ticker}.

    Requires ≥30 overlapping day-pairs.  Under that, returns a `note` field
    explaining what's missing so a caller can suggest waiting or switching
    to a higher-coverage ticker.

Input parameters:

- `ticker` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-sentimentfx-market-sentiment/api#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 67
- 2026-09-18: 67
- 2026-09-17: 66
- 2026-09-16: 66
- 2026-09-15: 65
- 2026-09-14: 65
- 2026-09-13: 64
- 2026-09-12: 64
- 2026-09-11: 63
- 2026-09-10: 63
- 2026-09-09: 62
- 2026-09-08: 62
- 2026-09-07: 62
- 2026-09-06: 61

## Common questions

### What is the SentimentFX MCP server?

SentimentFX is an MCP server listed in the public MCP registry as org.sentimentfx/market-sentiment. FinBERT news sentiment and price history for 42 crypto, FX, stock, ETF and commodity tickers. This page covers its hosted endpoint (https://api.sentimentfx.org/mcp).

### Is the SentimentFX MCP server safe to use?

SentimentFX scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SentimentFX MCP server expose?

SentimentFX exposes 6 tools: list_tickers, get_usage, get_sentiment, get_summary, get_prices, get_correlation. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.

### Does the SentimentFX MCP server require authentication?

No. We connected to SentimentFX without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SentimentFX MCP server still maintained?

SentimentFX is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.sentimentfx.org/mcp
- Authorisation metadata: https://api.sentimentfx.org/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/shaelegowski7/crypto-sentiment
- Website: https://developers.sentimentfx.org/
- Changelog RSS feed: https://verifymcp.io/servers/org-sentimentfx-market-sentiment/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-sentimentfx-market-sentiment/api.json
- HTML version of this page: https://verifymcp.io/servers/org-sentimentfx-market-sentiment/api