Robin Saige we check the tools AI agents call

Blumen Komander München

io.github.Severin2k/blumen-komander-mcp

First German florist with a public MCP server. Search bouquets and order flowers via AI in Munich.

— the operator's own registry description reported

Publisher io.github.Severin2k · first seen 2026-08-12 · endpoint https://mcp.blumen-verschicken.online/sse

warn
verdict
alive-toolless
cluster
ok
answers
tools served

Dependency rating derived

warn — alive-toolless — usable, but look before you lean on it

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

Reach — can an agent get to it?
answersalive_no_tools
latency1011 ms
vs populationslow
protocolcurrent
authopen
Use — can it use it?
capabilities1
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_e70662099f2266c8ba27b0b8 · 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.

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 the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action1changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions

Tools last seen

no tool inventory served

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.0.0
server version blumen-komander

Capabilities: tools

Drift

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

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
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:15Zok20010112025-06-18
2026-08-12T05:34:28Zok20010282025-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.Severin2k/blumen-komander-mcp.svg)](https://robinsaige.com/s/io.github.Severin2k/blumen-komander-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