Robin Saige we check the tools AI agents call

Microvix

io.github.mcp-dir/microvix-mcp

Microvix retail ERP (Linx, part of the Stone group) for store chains and franchises, via the officia

— the operator's own registry description reported

Publisher io.github.mcp-dir · first seen 2026-08-12 · endpoint https://api.mcp.ai/p_microvix

allow
verdict
gateway
cluster
ok_tools
answers
16
tools served

Dependency rating derived

allow
allow — gateway · retrieval-public ● · V1 shows its work ◐
allow — because answers ●, 16 tools legible (band B) ●, no confirmed drift in 2 probes ●; not yet checked: truth (0 runs)

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

Does it answer? Q1 · observed
answersalive_tools
latency829 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools16
vs populationmid
capabilities1
harnessB
Did it hold when checked? Q3–Q4 · derived
identityfarm_member
servers on its host99
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_f07615629e6af3e94b7de3c2 · 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?gateway — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V1 shows its work ◐evidence ↓
Q4Did it hold?harness B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?gateway · 99 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-public14serves public factstruth-checkable against a public source — the V-ladder applies in full
action2changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions

Tools last seen observed

authenticate connect marketplace microvix_clientes_fornec microvix_grupo_lojas microvix_list_accounts microvix_lojas microvix_movimento microvix_pedidos_venda microvix_produtos microvix_produtos_detalhes microvix_produtos_inventario microvix_vendedores report_bug show_version toolkit_info

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 & specific16/16
has a description16/16
description is substantive16/16
parameters are typed16/16
parameters are described3/163/16

16 of 16 tools graded · 16 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
0.9.241
server version mcp-ai

Capabilities: 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:59:48Zok_tools2008292025-06-18
2026-08-12T05:35:01Zok_tools20046772025-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.mcp-dir/microvix-mcp.svg)](https://robinsaige.com/s/io.github.mcp-dir/microvix-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