Robin Saige we check the tools AI agents call

quant brain mcp

io.github.paarths-collab/quant-brain-mcp

Stock analysis MCP: 38 indicators, 7 optimizers, 8 backtests, US + India sectors.

— the operator's own registry description reported

Publisher io.github.paarths-collab · first seen 2026-08-17 · endpoint https://mcp-quant-brain.onrender.com/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
25
tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a
allow — because answers ●, 25 tools legible (band B) ●, no confirmed drift in 3 probes ●; not yet checked: truth (0 runs)

Cluster mid-solo · distinctiveness 0.611 (unusual). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency283 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools25
vs populationhigh
capabilities4
harnessB
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_a017ff48b805da4589cb834d · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 3 probes ●evidence ↓
Q2What is it?action ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?mid-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (3 shown, 2026-08-23 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-23outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action18changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative4creates contentno answer key exists; disclosure + stability checks, never truth verdicts
retrieval-public2serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

analyze_momentum analyze_sector_intelligence_tool analyze_statistics analyze_technical_levels analyze_trend analyze_volatility analyze_volume backtest_macd_momentum backtest_macd_trend_follower backtest_mean_reversion_rsi_bb backtest_rsi_mean_reversion backtest_sma_crossover backtest_trend_crossover backtest_volatility_breakout build_trade_plan find_sector_stock_pipeline_tool generate_chart_pack generate_charts generate_optimized_verdict get_company_profile get_news get_quote plot_charts price_alert scan_watchlist

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility checktools passingok
name is clear & specific25/25
has a description25/25
description is substantive25/25
parameters are typed25/25
parameters are described0/250/25

25 of 25 tools graded · 25 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18
protocol version
session model
1.26.0
server version mcp-quant-brain

Capabilities: experimental prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:16:45Zok_tools2002832025-06-18
2026-08-30T06:16:33Zok_tools2001402025-06-18
2026-08-23T06:14:01Zok_tools2001322025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.paarths-collab/quant-brain-mcp.svg)](https://robinsaige.com/s/io.github.paarths-collab/quant-brain-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →