mcp-registry/org.sentimentfx/market-sentiment · v1.30.0
As of 2026-10-26 17:20 UTC, the Sentimentfx Market Sentiment MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
FinBERT news sentiment and price history for 42 crypto, FX, stock, ETF and commodity tickers.
Point your MCP client at this streamable-http endpoint: https://api.sentimentfx.org/mcp
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
9 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Forg.sentimentfx%2Fmarket-sentiment/fixes
{
"name": "get_correlation",
"description": "180-day Pearson correlation between daily sentiment shifts and next-day\n price returns for `ticker`.\n\n Returns Pearson `r`, `p_value`, `n_days` overlapping, a 95% confidence\n interval (Fisher z), and a categorical `strength` (strong / weak /\n inconclusive). Costs 1 API credit — same as GET /v1/correlation/{ticker}.\n\n Requires ≥30 overlapping day-pairs. Under that, returns a `note` field\n explaining what's missing so a caller can suggest waiting or switching\n to a higher-co",
"inputSchema": {
"type": "object",
"title": "get_correlationArguments",
"required": [
"ticker"
],
"properties": {
"ticker": {
"type": "string",
"title": "Ticker"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_prices",
"description": "Return daily close prices for `ticker` over the last `days`, in the\n ticker's native currency -- see the `currency` field on the response.\n\n Costs 1 API credit per day actually returned — same as\n GET /v1/prices/{ticker}. Prices come\n back reverse-chronological. Crypto is GBP (yfinance BTC-GBP etc.), FX\n pairs are a raw exchange rate in the pair's native convention (e.g.\n USDJPY is yen per dollar), and everything else (stocks/ETFs/commodity\n futures) is native USD -- there",
"inputSchema": {
"type": "object",
"title": "get_pricesArguments",
"required": [
"ticker"
],
"properties": {
"days": {
"type": "integer",
"title": "Days",
"default": 30
},
"ticker": {
"type": "string",
"title": "Ticker"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_sentiment",
"description": "Return the most recent FinBERT-scored news headlines for `ticker`.\n\n Each headline has a `sentiment_score` in [-1, +1] (positive_prob -\n negative_prob), a categorical `sentiment_label`, and a `source_kind`\n (news / reddit / stocktwits / x / youtube). Costs 1 API credit per 25\n headlines actually returned — same billing as GET /v1/sentiment/{ticker}.\n An empty result costs nothing.\n\n `limit` is capped at 100. Social posts are kept separate from news:\n the default `sources=\"",
"inputSchema": {
"type": "object",
"title": "get_sentimentArguments",
"required": [
"ticker"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 25
},
"ticker": {
"type": "string",
"title": "Ticker"
},
"sources": {
"enum": [
"news",
"social",
"all"
],
"type": "string",
"title": "Sources",
"default": "news"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/org.sentimentfx/market-sentiment"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/org.sentimentfx/market-sentiment"}) over MCP.
get_sentiment ~236 tokensget_summary ~232 tokensget_prices ~207 tokensget_correlation ~195 tokensget_usage ~154 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Forg.sentimentfx%2Fmarket-sentiment?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Forg.sentimentfx%2Fmarket-sentiment?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.sentimentfx%2Fmarket-sentiment.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.sentimentfx%2Fmarket-sentiment.svg :target: https://glimind.com/server/mcp-registry%2Forg.sentimentfx%2Fmarket-sentiment?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ca174f96c95ef949…, first seen 2026-10-21, included at leaf 36321 of 74,370. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable ml servers · most reliable data servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:20 UTC, the Sentimentfx Market Sentiment MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Sentimentfx Market Sentiment MCP server advertises 6 tools, including get_correlation, get_prices, get_sentiment, get_summary, get_usage.
Point your MCP client at this streamable-http endpoint: https://api.sentimentfx.org/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.