# Hlido Agent Reviews (remote · hlido.eu)

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

- Trust score: 56/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `hlido.eu`: 56/100 (this document), [markdown](https://verifymcp.io/servers/eu-hlido-mcp/hlido.md), [page](https://verifymcp.io/servers/eu-hlido-mcp/hlido)

## Channel facts

- Endpoint: `https://hlido.eu/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http eu-hlido-mcp https://hlido.eu/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add eu-hlido-mcp --url https://hlido.eu/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  eu-hlido-mcp:
    url: "https://hlido.eu/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 56, +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.

### 2026-08-01 (score 55, +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.

### 2026-07-31 (score 54, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 55, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 55, +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.

### 2026-07-27 (score 54, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 53)

First indexed and scored.

## MCP tools (17)

### `trust_check` (~237 tokens)

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.

Input parameters:

- `agent_or_url` (string, required): The 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_case` (string): Optional. The task you're considering this agent for (e.g. 'multi-file TypeScript refactor'); tailors the verdict to that use case when provided.

### `find_trusted` (~162 tokens)

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.

Input parameters:

- `limit` (integer): Maximum number of agents to return (default 10).
- `min_tier` (string): Minimum trust tier to include (VITAL is strictest, FLATLINE allows all). Defaults to STEADY.
- `need` (string, required): Free-text description of the capability you need (e.g. 'CLI coding agent that edits multiple files at once').

### `verify_claim` (~136 tokens)

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.

Input parameters:

- `agent` (string, required): The agent's Hlido slug or product URL (e.g. 'cursor').
- `claim` (string, required): The specific claim to verify, in plain language (e.g. 'works offline' or 'SOC 2 compliant').

### `compare_agents` (~121 tokens)

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.

Input parameters:

- `slugs` (array, required): List of 2 to 5 Hlido agent slugs to compare side by side (e.g. ['aider','cursor','opencode']).

### `submit_agent` (~196 tokens)

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.

Input parameters:

- `email` (string): Optional 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.
- `name` (string, required): Human-readable agent name (e.g. 'Example Coder').
- `note` (string): Optional context: what the agent does, or why it's worth reviewing.
- `url` (string, required): The agent's product or homepage URL (e.g. 'https://example.com').

### `verify_transparency` (~198 tokens)

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.

Input parameters:

- `url` (string, required): The agent's product or homepage URL (e.g. 'https://example.com'), or its Hlido slug.

### `get_scorecard` (~95 tokens)

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.

Input parameters:

- `slug` (string, required): The agent's Hlido slug (e.g. 'aider', 'gumloop')

### `get_incidents` (~155 tokens)

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.

Input parameters:

- `category` (string): Optional category filter
- `limit` (integer): Max results (default 20, max 100)
- `severity` (string): Optional minimum-interest filter (exact match)
- `slug` (string): Optional: only incidents for this agent slug

### `report_review_issue` (~138 tokens)

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.

Input parameters:

- `detail` (string, required): What's wrong, with a concrete reference (URL, claim id, etc) if possible
- `issue_type` (string, required): Category of the report
- `reporter` (string): Optional self-identifier — agent name or email — purely informational
- `slug` (string, required): The slug whose review has the issue

### `request_quick_audit` (~184 tokens)

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).

Input parameters:

- `name` (string): Optional human-readable name (we'll derive from URL if missing)
- `requester` (string): Optional self-identifier — agent name, email, or session id — for rate-limiting + follow-up
- `url` (string, required): Homepage or product URL of the agent to audit
- `why` (string): Optional one-liner: why are you considering this agent? helps us prioritize

### `find_similar_agents` (~154 tokens)

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.

Input parameters:

- `description` (string, required): Free-text description of the task or capability you need
- `min_score` (integer): Minimum Laddoo score filter (default 0)
- `top_k` (integer): Number of matches to return (default 5, max 20)

### `subscribe` (~113 tokens)

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.

Input parameters:

- `channel` (string): Preferred notification channel. webhook is advisory only until Wave 3 ships.
- `slug` (string, required): The Hlido slug to subscribe to (e.g. 'cursor', 'aider')

### `explain` (~123 tokens)

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.

Input parameters:

- `dimension` (string): Optional dimension filter. Run without and check supported_dimensions in response if unsure.
- `slug` (string, required): The agent's Hlido slug

### `recommend` (~82 tokens)

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.

Input parameters:

- `constraints` (object, required)

### `get_behavioral_trace` (~149 tokens)

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.

Input parameters:

- `slug` (string, required): The Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode')
- `spec_version` (string): Behavioral spec version (default 'v0.1'). Omit to get the latest available.

### `commerce_check` (~149 tokens)

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.

Input parameters:

- `agent_or_url` (string, required): The 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.

### `scan_mcp` (~273 tokens)

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/

Input parameters:

- `requester` (string): Optional self-identifier — agent name or email — for follow-up when a queued scan completes.
- `server` (string, required): The 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…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/eu-hlido-mcp/hlido#diagnostics

## Score history

- 2026-08-03: 56
- 2026-08-02: 55
- 2026-08-01: 55
- 2026-07-31: 54
- 2026-07-30: 55
- 2026-07-29: 55
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 53

## Links

- Remote endpoint: https://hlido.eu/mcp
- Repository: https://github.com/ankitkapur1992-hlido/hlido-mcp
- Website: https://hlido.eu/
- Changelog RSS feed: https://verifymcp.io/servers/eu-hlido-mcp/hlido/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/eu-hlido-mcp/hlido/changelog.json
- HTML version of this page: https://verifymcp.io/servers/eu-hlido-mcp/hlido