Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Hlido Agent Reviews

REMOTE · HLIDO.EU · SCANNED AUG 3

Independent AI-agent reviews: trust checks, evidence scorecards, incident registry, recommendations.

Available components

+2 this week 56 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2665 tokens (~156/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · hlido.eu

# add to Claude Code
claude mcp add --transport http eu-hlido-mcp https://hlido.eu/mcp
# ~/.codex/config.toml
[mcp_servers.eu-hlido-mcp]
url = "https://hlido.eu/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "eu-hlido-mcp": {
      "type": "remote",
      "url": "https://hlido.eu/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add eu-hlido-mcp --url https://hlido.eu/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  eu-hlido-mcp:
    url: "https://hlido.eu/mcp"
// mcp.json
{
  "mcpServers": {
    "eu-hlido-mcp": {
      "type": "http",
      "url": "https://hlido.eu/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 53

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://hlido.eu/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=hlido.eu CN=WE1,O=Google Trust Services,C=US 11 Jun 2026 9 Sept 2026 ECDSA 256 ECDSA-SHA256 a9e875878043f6b4130ca75a3d5c5539
SANs: hlido.eu
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of hlido.eu. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
eu. present 35926 8 Verified
hlido.eu. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://hlido.eu/mcp Verified 200
http (plaintext) http://hlido.eu/mcp Served over HTTP 200
MCP tools — 17 exposed · ~2,665 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
commerce_check ~149

Check whether a Hlido-reviewed agent is ready to be delegated to / transacted with in the agentic-commerce world (MCP/ACP/AP2). Returns its independent Agentic-Commerce Readiness score (0-100), band (COMMERCE-READY/INTEGRABLE/SURFACE-ONLY/CLOSED), the programmatic surfaces it exposes, and the evidence basis. Call this before an orchestrator delegates a paid/identity-bearing task to another agent.

NameTypeReqDescription
agent_or_urlstringyesThe agent to check: either its Hlido slug (e.g. 'voltagent', 'aider') or its product/homepage URL. A URL is matched to the closest reviewed agent.

No output schema declared.

No examples provided.

compare_agents ~121

Head-to-head trust comparison of 2-5 Hlido-reviewed agents. Returns each agent's Laddoo score, tier, dimension scores, and key claim verdicts side by side so you can pick the most trustworthy option for a task. Use this once you've shortlisted candidates (via find_trusted, find_similar_agents, or recommend) and need a direct comparison.

NameTypeReqDescription
slugsarrayyesList of 2 to 5 Hlido agent slugs to compare side by side (e.g. ['aider','cursor','opencode']).

No output schema declared.

No examples provided.

explain ~123

Structured natural-language explanation of why a Hlido-reviewed agent has its current score. Pulls claim-by-claim evidence from the published scorecard. Pass an optional dimension (one of: reliability, transparency, integration, security, evidence) to filter; omit for the full picture. Returns each claim with verdict (PASS|FAIL|PARTIAL|UNKNOWN), a quoted evidence snippet, plus a top-line synthesis.

NameTypeReqDescription
dimensionstringOptional dimension filter. Run without and check supported_dimensions in response if unsure.
slugstringyesThe agent's Hlido slug

No output schema declared.

No examples provided.

find_similar_agents ~154

Semantic search over Hlido's review corpus. Given a task description (e.g. 'I need an agent that can refactor TypeScript and edit multiple files at once'), returns the top-N reviewed agents ranked by embedding similarity, each with their Laddoo score, evidence_tier, and review URL. Use this when you have a task in mind and want Hlido's recommendation — much better than substring matching via find_trusted.

NameTypeReqDescription
descriptionstringyesFree-text description of the task or capability you need
min_scoreintegerMinimum Laddoo score filter (default 0)
top_kintegerNumber of matches to return (default 5, max 20)

No output schema declared.

No examples provided.

find_trusted ~162

Discover Hlido-reviewed agents that match a free-text need, ranked by trust. Returns reviewed agents at or above a minimum tier, each with its Laddoo score, tier, and review URL. Use this for keyword/need-based discovery; for semantic task-matching prefer find_similar_agents, and for structured constraint filters (category/score/tier) prefer recommend.

NameTypeReqDescription
limitintegerMaximum number of agents to return (default 10).
min_tierstringMinimum trust tier to include (VITAL is strictest, FLATLINE allows all). Defaults to STEADY.
needstringyesFree-text description of the capability you need (e.g. 'CLI coding agent that edits multiple files at once').

No output schema declared.

No examples provided.

get_behavioral_trace ~149

Fetch the behavioral evaluation trace for a Hlido-reviewed agent — per-task pass/fail, adapter used, behavioral tier, and signed trace link. Returns status 'not_yet_bench_tested' if the slug hasn't been evaluated yet, or 'not_testable' if the agent's interface doesn't support automated bench runs. Use this when you need evidence that an agent's coding/task behaviour has been independently verified beyond marketing claims.

NameTypeReqDescription
slugstringyesThe Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode')
spec_versionstringBehavioral spec version (default 'v0.1'). Omit to get the latest available.

No output schema declared.

No examples provided.

get_incidents ~155

Fetch published incidents from Hlido's NTSB-style failure registry — real observed agent failures (availability outages, regressions, hallucinations, safety issues) plus Hlido self-reported process incidents, each with severity, evidence, and vendor-response status. Filter by agent slug, severity, or category. Use this before delegating to an agent to check for known recent failures; an empty list means no published incidents, not a guarantee of reliability.

NameTypeReqDescription
categorystringOptional category filter
limitintegerMax results (default 20, max 100)
severitystringOptional minimum-interest filter (exact match)
slugstringOptional: only incidents for this agent slug

No output schema declared.

No examples provided.

get_scorecard ~95

Fetch the full sanitized claim-vs-evidence scorecard for one Hlido-reviewed agent. Returns every claim, verdict, evidence quote, source surface, and (for CLI/API tests) the captured command + exit_code + duration. Schema v1.0. Use this for agent-to-agent pre-flight evaluation.

NameTypeReqDescription
slugstringyesThe agent's Hlido slug (e.g. 'aider', 'gumloop')

No output schema declared.

No examples provided.

recommend ~82

Constraint-driven recommendation across Hlido's reviewed agents. Pass any combination of: category, min_score, tier, use_case, max_results. Returns ranked candidates each with a why_match line. Use this when you have buyer constraints (budget, category, capability) and want Hlido's filtered shortlist instead of one-by-one trust_check calls.

NameTypeReqDescription
constraintsobjectyes

No output schema declared.

No examples provided.

report_review_issue ~138

Report an issue with a Hlido review (stale info, wrong verdict, missing claim, broken link). Use when calling get_scorecard or trust_check returns data you can prove is incorrect. Hlido's R1 maintenance routine processes reports daily and fires re-tests via dispute-retest sub-agent.

NameTypeReqDescription
detailstringyesWhat's wrong, with a concrete reference (URL, claim id, etc) if possible
issue_typestringyesCategory of the report
reporterstringOptional self-identifier — agent name or email — purely informational
slugstringyesThe slug whose review has the issue

No output schema declared.

No examples provided.

request_quick_audit ~184

Request that Hlido audit a NEW AI agent that has no review yet. Use this when trust_check or get_scorecard returns no_review_found and you need a verdict before delegating to the unknown agent. Returns a future scorecard URL + ETA. Free-tier rate-limited (5/day per anonymous, 50/day per identified). The audit produces signed evidence + claim verification within ~24h (sooner if founder triggers manually).

NameTypeReqDescription
namestringOptional human-readable name (we'll derive from URL if missing)
requesterstringOptional self-identifier — agent name, email, or session id — for rate-limiting + follow-up
urlstringyesHomepage or product URL of the agent to audit
whystringOptional one-liner: why are you considering this agent? helps us prioritize

No output schema declared.

No examples provided.

scan_mcp ~273

On-demand independent SAFETY scan of an MCP server — call this BEFORE installing or connecting to one. Give it an HTTP(S) MCP endpoint URL (scanned live in seconds), or an npm/PyPI package name or GitHub repo (queued for an isolated sandbox scan — local stdio servers execute code, so Hlido never runs them inline). Returns the safety tier (SAFE/CAUTION/RISKY/DANGEROUS), tool-poisoning detection (the malice signal), dangerous-capability red-flags (shell/code-eval/fs-write/egress/secrets) with per-tool evidence, and auth posture. Tier = blast radius if hijacked, not maintainer trustworthiness. A server Hlido hasn't scanned returns not_scanned — never assumed safe. Register of already-scanned servers: https://hlido.eu/mcp/

NameTypeReqDescription
requesterstringOptional self-identifier — agent name or email — for follow-up when a queued scan completes.
serverstringyesThe MCP server to scan: an HTTP(S) MCP endpoint URL (e.g. 'https://mcp.example.com/mcp' — scanned live), OR an npm package (e.g. '@modelcontextprotocol/server-filesystem'), PyPI package, or GitHub re…

No output schema declared.

No examples provided.

submit_agent ~196

Nominate a new AI agent for Hlido to review. Use this when an agent isn't in Hlido's corpus yet (trust_check returned no_review_found) and you want it added. Returns a confirmation with a tracking reference; the review is queued and produces a public scorecard. If you need a verdict right now rather than a queued review, use request_quick_audit (faster, rate-limited) instead.

NameTypeReqDescription
emailstringOptional contact email for the submitter — if you want a reply or a heads-up when the review publishes. Providing it always flags the submission to the Hlido team.
namestringyesHuman-readable agent name (e.g. 'Example Coder').
notestringOptional context: what the agent does, or why it's worth reviewing.
urlstringyesThe agent's product or homepage URL (e.g. 'https://example.com').

No output schema declared.

No examples provided.

subscribe ~113

Preview — Wave 3 will add persistent webhook + RSS subscriptions. For now this returns the agent's current state plus advisory polling instructions (RSS at /changelog/feed.xml or polling /data/attestations/{slug}.json). Use this to register interest in being notified when a slug's verdict changes.

NameTypeReqDescription
channelstringPreferred notification channel. webhook is advisory only until Wave 3 ships.
slugstringyesThe Hlido slug to subscribe to (e.g. 'cursor', 'aider')

No output schema declared.

No examples provided.

trust_check ~237

The core Hlido trust query: is a specific AI agent trustworthy? Given one agent (by Hlido slug or product/homepage URL) it returns the independent Laddoo trust score (0-100), tier (VITAL/STEADY/FADING/FLATLINE), a one-line verdict, a claim-verification summary, and any known incidents. Call this FIRST — before delegating to, installing, or relying on another agent — to get a fast trust read. Returns no_review_found if the agent isn't in Hlido's corpus (then call request_quick_audit). For the full claim-by-claim evidence, follow up with get_scorecard.

NameTypeReqDescription
agent_or_urlstringyesThe agent to check: either its Hlido slug (e.g. 'aider', 'cursor') or its product/homepage URL (e.g. 'https://cursor.com'). A URL is matched to the closest reviewed agent.
use_casestringOptional. The task you're considering this agent for (e.g. 'multi-file TypeScript refactor'); tailors the verdict to that use case when provided.

No output schema declared.

No examples provided.

verify_claim ~136

Fact-check one specific marketing or capability claim about an agent against Hlido's independent testing. Returns Hlido's verdict (PASS/FAIL/PARTIAL/UNKNOWN) with a quoted evidence snippet and its source surface — or an honest null when that exact claim wasn't tested (absence of evidence, not proof). Use this to validate a vendor's specific promise before you rely on it.

NameTypeReqDescription
agentstringyesThe agent's Hlido slug or product URL (e.g. 'cursor').
claimstringyesThe specific claim to verify, in plain language (e.g. 'works offline' or 'SOC 2 compliant').

No output schema declared.

No examples provided.

verify_transparency ~198

Check any AI agent's EU AI Act Article-50 transparency posture — including agents Hlido has NOT reviewed yet. Returns two clearly separated layers: (1) Hlido's independent register verdict when the agent is in our reviewed corpus, and (2) a live public-surface probe of the Article-50 signals (AI-interaction disclosure, machine-readable marking/provenance, deepfake/synthetic labelling, detection tool). Use before adopting or delegating to a tool ahead of the 2026-08-02 transparency obligations. The live probe is a first-pass surface read, NOT a compliance determination and NOT legal advice; an undetected signal means 'not discoverable on the public surface', not 'non-compliant'. Unreviewed agents are automatically queued for a full independent review.

NameTypeReqDescription
urlstringyesThe agent's product or homepage URL (e.g. 'https://example.com'), or its Hlido slug.

No output schema declared.

No examples provided.