Robin Saige we check the tools AI agents call

agentView

de.agentview/agentview-mcp

Display delivery platform for AI agents. Push HTML, dashboards and live data to screens.

— the operator's own registry description reported

Publisher de.agentview · first seen 2026-08-12 · endpoint https://agentview.de/mcp

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
57
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency575 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools57
vs populationhigh
capabilities6
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_2e2b70415f3da0ca057798ac · 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?action ● evidence ↓
Q3Can it be checked?V n/a for this kind ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-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
action30changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public18serves public factstruth-checkable against a public source — the V-ladder applies in full
generative4creates contentno answer key exists; disclosure + stability checks, never truth verdicts
retrieval-private4serves the caller's own dataoutside truth-checking is impossible BY NATURE, not by failure — the operator-invited pathway applies
unclassified1not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

assign_display_categories authenticate broadcast_content claim_display clear_display configure_display configure_organization create_api_key create_auth_session create_display create_organization delete_asset delete_data_slot delete_display delete_organization fetch get_account get_agent_artifact get_asset get_auth_session get_data_slot get_display get_display_preview_url get_license_info get_organization get_public_status get_storage_usage get_store_template_content get_store_template_details get_store_template_install_options list_api_keys list_assets list_data_slots list_display_categories list_displays list_organizations list_store_categories logout manage_display_category manage_licenses manage_org_member pair_by_code read_display_html remove_display_from_org revoke_api_key search search_public_apis search_store_templates send_html send_store_template_to_display send_url set_data_slot set_display_grant submit_feedback test_display_content update_asset upload_asset

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 & specific57/57
has a description57/57
description is substantive57/57
parameters are typed56/5756/57
parameters are described56/5756/57

57 of 57 tools graded · 57 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
2.1.119
server version agentView MCP

Capabilities: completions extensions logging prompts resources 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:58:40Zok_tools2005752025-06-18
2026-08-12T05:33:54Zok_tools2004622025-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/de.agentview/agentview-mcp.svg)](https://robinsaige.com/s/de.agentview/agentview-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