Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/blake365/options-chainWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/blake365/options-chain/options-chain-mcp)<a href="https://agentmods.dev/mcp/blake365/options-chain/options-chain-mcp"><img src="https://agentmods.dev/badge/mcp/blake365/options-chain/options-chain-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
options-chain-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"options-chain-mcp": {
"command": "/usr/local/bin/node",
"args": [
"/Full/Route/to/Folder/options-chain/build/index.js"
],
"env": {
"token": "your_sandbox_api_token_here"
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 11 lines scan A a858c9d11c9f
options-chain-mcp is an MCP server published in the GitHub repository blake365/options-chain (9 stars, last pushed 29d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
chart-library
MCP server "chart-library" as configured in grahammccain/chart-library-mcp. Launched with chartlibrary-mcp. Needs 1 environment variable to run.
pmq
Fail-closed execution and market-data layer for Polymarket CLOB V2: local signing, confirmed fills only, fee-correct math, working deposit-wallet (POLY1271) support. Runs locally from the pmquant Python package. Needs 11 environment variables to run.
market-data-toolkit-mcp
17 market-data tools for AI agents: eBay sold prices, company KYC, SEC filings, patents, auctions. Remote server at mcp.apify.com.
openmarkets
OpenMarkets is a modular Model Context Protocol (MCP) server that unifies access to financial market data for AI, research, and quantitative finance. It offers robust APIs for historical prices, corporate actions, fundamentals, and more, enabling advanced agentic retrieval, RAG, and LLM-powered workflows. Runs locally…
brs-signals-mcp
Live Bitcoin market regime for agents: three sensors read pre-price data — fee curves, funding velocity, whale flows, absence — every 30s and reject almost everything. When they converge, a directional call is emitted with evidence. The data can't be reconstructed from history. Public, agent-auditable track record.…
mansa-african-markets
Live African stock market data — NGX, GSE, NSE, JSE, BRVM and 8 more. Prices, indices and movers. Remote server at mcp.mansamarkets.com.