SentimentFX
REMOTE · API.SENTIMENTFX.ORG · SCANNED SEP 20
FinBERT news sentiment and price history for 42 crypto, FX, stock, ETF and commodity tickers.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · api.sentimentfx.org
claude mcp add --transport http org-sentimentfx-market-sentiment 'https://api.sentimentfx.org/mcp'
{
"mcpServers": {
"org-sentimentfx-market-sentiment": {
"url": "https://api.sentimentfx.org/mcp"
}
}
} {
"servers": {
"org-sentimentfx-market-sentiment": {
"type": "http",
"url": "https://api.sentimentfx.org/mcp"
}
}
} [mcp_servers.org-sentimentfx-market-sentiment] url = "https://api.sentimentfx.org/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-sentimentfx-market-sentiment": {
"type": "remote",
"url": "https://api.sentimentfx.org/mcp",
"enabled": true
}
}
} openclaw mcp add org-sentimentfx-market-sentiment --url 'https://api.sentimentfx.org/mcp' --transport streamable-http
mcp_servers:
org-sentimentfx-market-sentiment:
url: "https://api.sentimentfx.org/mcp" {
"McpServers": {
"org-sentimentfx-market-sentiment": {
"Transport": "http",
"Url": "https://api.sentimentfx.org/mcp"
}
}
} assistant mcp add org-sentimentfx-market-sentiment -t streamable-http -u 'https://api.sentimentfx.org/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 7 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 6 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://api.sentimentfx.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.sentimentfx.org | CN=YR1,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | RSA 2048 | SHA256-RSA | 503636d2f9940b9782298ec7bea174a2ebc |
| SANs: api.sentimentfx.org | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.sentimentfx.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| sentimentfx.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.sentimentfx.org/mcp | Verified | 200 | |
| http (plaintext) | http://api.sentimentfx.org/mcp | HTTPS enforced | 301 | https://api.sentimentfx.org/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_correlation ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_prices ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_sentiment ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_summary ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_usage ~96
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_tickers ~103
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
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.