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/tickerdb/tickerdb-mcpWrote 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/tickerdb/tickerdb-mcp/mcp-server)<a href="https://agentmods.dev/mcp/tickerdb/tickerdb-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/tickerdb/tickerdb-mcp/mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/tickerdb/tickerdb-mcp/mcp-server"><img src="https://agentmods.dev/badge/mcp/tickerdb/tickerdb-mcp/mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server 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 1mo 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
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"tickerdb-mcp"
],
"env": {
"TICKERDB_KEY": ""
}
}
}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.
- 1mo ago First seen · 12 lines scan A 363e87931c41
mcp-server is an MCP server published in the GitHub repository tickerdb/tickerdb-mcp (5 stars, last pushed 1mo 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
coinrithm-trading
CoinRithm MCP server (coinrithm-mcp) and self-host agent runner (coinrithm-agent): keyless prediction-market data across 12 venues, plus paper trading of crypto spot, futures, and prediction markets with a user-minted API key. Runs locally from the @coinrithm/mcp-trading npm package. Needs 1 environment variable to…
mcp-trading
Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM. Runs locally from the @coinrithm/mcp-trading npm package. Needs 2 environment variables to run.
tegro-wallet-mcp
The TON & GRAM wallet MCP — give any AI assistant read-only on-chain data (balances, tokens, transactions, prices, NFTs, DNS, address validation). One server for Claude, Cursor, Claude Code, ChatGPT and Hermes Agent. No keys, no signing. Runs locally from the @tegroton/wallet-mcp npm package. Needs 1 environment…
crypto
Crypto token and narrative trend volume over time, with growth signals. Free key at trendsmcp.ai. Remote server at crypto.api.trendsmcp.ai.
apollo-proxy
26 AI tools: DeFi, OSINT, crypto, intel feeds, search, proxy. x402 micropayments. Runs locally from the @apollo_ai/mcp-proxy npm package.
trading-cli
MCP server "trading-cli" as configured in Alorse/trading-cli. Launched with trading-cli mcp.