Robin Saige we check the tools AI agents call

quanticdata mcp

io.github.quantumproxies/quanticdata-mcp

Live web access for agents: scrape, SERP search, crawl/map, 74 collectors, datasets, proxies.

— the operator's own registry description reported

Publisher io.github.quantumproxies · first seen 2026-08-26 · endpoint https://api.quanticdata.io/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
25
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 25 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (2 attempts unverifiable, 0 disagreements)

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

Does it answer? Q1 · observed
answersalive_tools
latency162 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools25
vs populationhigh
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_457483a919a3fc6610faf557 · 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 — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness A · 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 (2 shown, 2026-08-30 → 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-30outcomefirst 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
retrieval-public13serves public factstruth-checkable against a public source — the V-ladder applies in full
generative5creates contentno answer key exists; disclosure + stability checks, never truth verdicts
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
orchestration2routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

batch batch_status collector_run_status crawl crawl_status create_dataset dataset_status generate_parser generate_proxies heal_parser_preset list_collectors list_parser_presets list_proxies map parser_preset_stats proxy_locations run_collector save_parser_preset scrape search search_and_read search_bulk search_bulk_status seo_audit whitelist_ip

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 A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific25/25
has a description25/25
description is substantive25/25
parameters are typed25/25
parameters are described24/2524/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 yet confirmed — 2 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
tariff-duty0901.21.00unverifiableus-hts
tariff-duty6109.10.00unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
0.9.0
server version quanticdata

Capabilities: 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:17:01Zok_tools2001622025-06-18
2026-08-30T06:16:51Zok_tools2001962025-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.quantumproxies/quanticdata-mcp.svg)](https://robinsaige.com/s/io.github.quantumproxies/quanticdata-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 →