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.
npx agentmods add mcp/quantoracledev/quantoracle/ga4git clone --depth 1 https://github.com/QuantOracledev/quantoracleGrade C, and why
ga4 scanned grade C with 1 finding 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 2d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
"//": "GOOGLE_APPLICATION_CREDENTIALS is auto-discovered from gcloud ADC (~/AppData/Roaming/gcloud/application_default_credentials.json on Windows). Run 'gcloud auth application-default login' before first use — see SETU What it actually says
{
"ga4": {
"//": "Official Google Analytics MCP server (googleanalytics/google-analytics-mcp on GitHub). Installed via pip into the project venv. Exposes 7 tools: get_account_summaries, get_property_details, list_google_ads_links, run_report, run_funnel_report, get_custom_dimensions_and_metrics, run_realtime_report.",
"command": "D:\\Quantcalc\\venv\\Scripts\\analytics-mcp.exe",
"args": [],
"env": {
"//": "GOOGLE_APPLICATION_CREDENTIALS is auto-discovered from gcloud ADC (~/AppData/Roaming/gcloud/application_default_credentials.json on Windows). Run 'gcloud auth application-default login' before first use — see SETUP-GA4-MCP.md.",
"GOOGLE_PROJECT_ID": "quantoracle-analytics"
}
}
}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.
- 2d ago First seen · 11 lines scan C 334152cff0a3
ga4 is an MCP server published in the GitHub repository QuantOracledev/quantoracle (11 stars, last pushed 14d 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 C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
web3-signals
AI crypto buy/sell signals for 20 assets: 6 data dimensions fused into 0-100 scores. x402 + MCP. Remote server at web3-signals-api-production.up.railway.app.
crypto-derivatives-mcp
Crypto data MCP: 22 tools covering derivatives, forecasts, alerts, liquidations, GEX — 16 assets. Runs locally from the crypto-derivatives-mcp npm package.
crypto-quant-signal-mcp
Quant trading signals, funding rate arb scanning, and market regime detection for crypto perps. Runs locally from the crypto-quant-signal-mcp npm package.
mcp
Live crypto data: funding rates, funding arbitrage, OI pressure, Fear & Greed. Free, no API key. Runs locally from the bykaranteli-mcp npm package.
coingecko-mcp-server
Crypto market data via CoinGecko — prices, markets, history, trending, and deep coin metadata. Runs locally from the @cyanheads/coingecko-mcp-server npm package. Needs 2 environment variables to run.
verdictswarm
Every tool has an answer — your agent needs a decision. MCP server for the VerdictSwarm pre-trade check: a machine-readable avoid/caution/clear before your agent trades, plus intended-size exit feasibility and holder-cluster attribution on Solana. Runs locally from the verdictswarm-mcp Python package. Needs 3…