Robin Saige we check the tools AI agents call

Agent Commerce Guard

io.github.fxjim/agent-commerce-guard

Policy review and purchase discovery for AI-agent commerce actions.

— the operator's own registry description reported

Publisher io.github.fxjim · first seen 2026-08-12 · endpoint https://agent-commerce-guard.vercel.app/api/mcp

allow
verdict
thin-solo
cluster
ok_tools
answers
1
tools served

Dependency rating derived

allow — thin-solo — safe to depend on

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

Reach — can an agent get to it?
answersalive_tools
latency73 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools1
vs populationlow
capabilities3
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

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

Tools last seen

review_agent_commerce_actions

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 & specific1/1
has a description1/1
description is substantive1/1
parameters are typed1/1
parameters are described1/1

1 of 1 tools graded · 1 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
1.2.0
server version agent-commerce-guard

Capabilities: prompts resources 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_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:33Zok_tools200732025-06-18
2026-08-12T05:34:46Zok_tools200812025-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.fxjim/agent-commerce-guard.svg)](https://robinsaige.com/s/io.github.fxjim/agent-commerce-guard)

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