mcp-registry/com.optionsbell/options-flow · v2.0.0
As of 2026-10-23 22:43 UTC, the Optionsbell Options Flow MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Unusual options activity on 7,000+ US stocks: top prints, streaks, IV rank, sentiment, sectors.
Claude Code
claude mcp add --transport http optionsbell-options-flow-mcp-server https://optionsbell.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"optionsbell-options-flow-mcp-server": {
"type": "http",
"url": "https://optionsbell.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
13 of 13 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 →
11 parameter(s) across 6 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 →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 5 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. 6 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.optionsbell%2Foptions-flow/fixes
{
"name": "get_dataset_stats",
"description": "Discover what data is available before querying: date ranges, contract counts, symbol counts and sector coverage for the unusual-activity dataset and its daily aggregates. Call this first when unsure about available history.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Dataset coverage"
}{
"name": "get_expiry_concentration",
"description": "Where the day's unusual premium sits along the expiry axis, in DTE buckets (0-7, 8-30, 31-90, 90+) with call/put splits. Heavy short-dated premium reads as event bets; heavy long-dated as positioning.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"date": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Trading day, YYYY-MM-DD. Defaults to the latest available day."
},
"symbols": {
"type": "string",
"description": "Comma-separated tickers, e.g. 'AAPL,NVDA,TSLA'."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Expiry (DTE) concentration (Pro)"
}{
"name": "get_flow_history",
"description": "End-of-day series of one symbol's UNUSUAL options flow (aggregated from the contracts that passed the unusual filter - not the full tape): daily call/put volume, premium, C/P ratios, average IV, net delta and the consecutive-day streak. ~75 trading days - the series behind back-tests and 'how has unusual flow on NVDA developed?'",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"symbol"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 200,
"minimum": 1,
"description": "Max rows, newest first (default 90)."
},
"symbol": {
"type": "string",
"maxLength": 10,
"minLength": 1,
"description": "Single ticker, e.g. 'TSLA'."
},
"date_to": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Range end, YYYY-MM-DD inclusive."
},
"date_from": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Range start, YYYY-MM-DD inclusive."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Per-symbol unusual-flow history (Pro)"
}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/com.optionsbell/options-flow"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.optionsbell/options-flow"}) over MCP.
get_unusual_activity ~598 tokensget_flow_sentiment ~512 tokensget_oi_changes ~423 tokensget_flow_streaks ~291 tokensget_symbol_flow ~266 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%2Fcom.optionsbell%2Foptions-flow?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.optionsbell%2Foptions-flow?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.optionsbell%2Foptions-flow.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.optionsbell%2Foptions-flow.svg :target: https://glimind.com/server/mcp-registry%2Fcom.optionsbell%2Foptions-flow?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:8173335d9f20b66f…, first seen 2026-10-17, included at leaf 5719 of 55,031. Version history · verify what your client received.
Compare: most reliable data servers · most reliable finance 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-23 22:43 UTC, the Optionsbell Options Flow MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Optionsbell Options Flow MCP server advertises 13 tools, including get_dataset_stats, get_expiry_concentration, get_flow_history, get_flow_sentiment, get_flow_streaks.
Point your MCP client at this streamable-http endpoint: https://optionsbell.com/mcp
Glimind scanned all 13 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.