Robin Saige we check the tools AI agents call

Agrus.ai — Enterprise AI Agency

io.github.phwizard/mcp-agrus-ai

AI consulting agency for regulated industries. Scope a PoC, query compliance, request a proposal.

— the operator's own registry description reported

Publisher io.github.phwizard · first seen 2026-08-12 · endpoint https://mcp.agrus.ai/mcp

allow
verdict
mid-solo
cluster
ok_tools
answers
7
tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.132 (typical). 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
latency125 ms
vs populationtypical
protocolcurrent
authopen
Use — can it use it?
tools7
vs populationmid
capabilities1
harnessA
Trust — can it rely on it?
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_c033d14589e4b5ce694d63ee · 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 tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
action3changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public3serves public factstruth-checkable against a public source — the V-ladder applies in full
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen

get_case_study list_services list_verticals query_compliance_position request_proposal request_quote scope_poc

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 & specific7/7
has a description7/7
description is substantive7/7
parameters are typed7/7
parameters are described7/7

7 of 7 tools graded · 7 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.2.0
server version agrus

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_tools
raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:56Zok_tools2001252025-06-18
2026-08-12T05:35:12Zok_tools2001182025-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.phwizard/mcp-agrus-ai.svg)](https://robinsaige.com/s/io.github.phwizard/mcp-agrus-ai)

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