Robin Saige we check the tools AI agents call

Raven

ai.ravenmcp/raven-mcp

Design intelligence for coding agents: audits, design systems, and a taste profile agents consult.

— the operator's own registry description reported

Publisher ai.ravenmcp · first seen 2026-08-12 · endpoint https://mcp.ravenmcp.ai/api/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
45
tools served

Dependency rating derived

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

Cluster rich-solo · distinctiveness 0.403 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency136 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools45
vs populationhigh
capabilities2
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_574d94f1e4b6d8391125e965 · 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?rich-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-12 → 2026-08-14). 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-12outcomefirst 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-public37serves public factstruth-checkable against a public source — the V-ladder applies in full
generative5creates contentno answer key exists; disclosure + stability checks, never truth verdicts
computational2deterministic transformsself-checkable by re-computation and known-answer tests
predictive1claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

audit_consistency audit_content audit_contrast audit_ios_a11y audit_ios_privacy audit_ios_screen audit_layout audit_page audit_parity audit_responsive_visibility audit_rn audit_screen audit_swiftui audit_tap_targets audit_typography audit_url audit_video_playback compose_system evaluate_design generate_design_system generate_service_blueprint get_brand_principles get_brand_system get_brand_trends get_business_strategy get_checklist get_content_pattern get_content_principles get_content_system get_d4d_framework get_design_system get_metrics_framework get_pattern get_principles get_research_method get_service_pattern get_service_standard list_content_systems list_creative_models list_creative_presets list_design_systems score_creative score_page search_knowledge suggest_contrast_fix

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 & specific45/45
has a description45/45
description is substantive45/45
parameters are typed45/45
parameters are described41/4541/45

45 of 45 tools graded · 45 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 — 3 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
tariff-duty8471.30.01unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
2.4.1
server version raven-mcp

Capabilities: prompts tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:57:38Zok_tools2001362025-06-18
2026-08-12T05:32:56Zok_tools2001002025-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/ai.ravenmcp/raven-mcp.svg)](https://robinsaige.com/s/ai.ravenmcp/raven-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