MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Hlido Agent Reviews is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Independent AI-agent reviews: trust checks, evidence scorecards, incident registry, recommendations.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http hlido-agent-reviews-mcp https://hlido.eu/mcp
# 2 — ask your agent for something these tools do
# trust_check, find_trusted, verify_claim and 16 more
Hlido Agent Reviews costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http hlido-agent-reviews-mcp https://hlido.eu/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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. Retur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_or_url | string | yes | 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 | no | Optional. The task you're considering this agent for (e.g. 'multi-file TypeScript refactor'); tailors the verdict to that use case when provided. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | yes | Free-text description of the capability you need (e.g. 'CLI coding agent that edits multiple files at once'). |
| min_tier | string | no | Minimum trust tier to include (VITAL is strictest, FLATLINE allows all). Defaults to STEADY. |
| limit | integer | no | Maximum number of agents to return (default 10). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent | string | yes | The agent's Hlido slug or product URL (e.g. 'cursor'). |
| claim | string | yes | The specific claim to verify, in plain language (e.g. 'works offline' or 'SOC 2 compliant'). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slugs | array | yes | List of 2 to 5 Hlido agent slugs to compare side by side (e.g. ['aider','cursor','opencode']). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The agent's product or homepage URL (e.g. 'https://example.com'). |
| name | string | yes | Human-readable agent name (e.g. 'Example Coder'). |
| note | string | no | Optional context: what the agent does, or why it's worth reviewing. |
| string | no | 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. |
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 to
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The agent's product or homepage URL (e.g. 'https://example.com'), or its Hlido slug. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The agent's Hlido slug (e.g. 'aider', 'gumloop') |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | no | Optional: only incidents for this agent slug |
| severity | string | no | Optional minimum-interest filter (exact match) |
| category | string | no | Optional category filter |
| limit | integer | no | Max results (default 20, max 100) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The slug whose review has the issue |
| issue_type | string | yes | Category of the report |
| detail | string | yes | What's wrong, with a concrete reference (URL, claim id, etc) if possible |
| reporter | string | no | Optional self-identifier — agent name or email — purely informational |
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 man
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Homepage or product URL of the agent to audit |
| name | string | no | Optional human-readable name (we'll derive from URL if missing) |
| why | string | no | Optional one-liner: why are you considering this agent? helps us prioritize |
| requester | string | no | Optional self-identifier — agent name, email, or session id — for rate-limiting + follow-up |
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | Free-text description of the task or capability you need |
| top_k | integer | no | Number of matches to return (default 5, max 20) |
| min_score | integer | no | Minimum Laddoo score filter (default 0) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The Hlido slug to subscribe to (e.g. 'cursor', 'aider') |
| channel | string | no | Preferred notification channel. webhook is advisory only until Wave 3 ships. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The agent's Hlido slug |
| dimension | string | no | Optional dimension filter. Run without and check supported_dimensions in response if unsure. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| constraints | object | yes | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode') |
| spec_version | string | no | Behavioral spec version (default 'v0.1'). Omit to get the latest available. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_or_url | string | yes | 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. |
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 (th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server | string | yes | 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 rep |
| requester | string | no | Optional self-identifier — agent name or email — for follow-up when a queued scan completes. |
Fetch the Agent Market Pulse — machine-readable market intelligence for the AI-agent market, derived from Hlido's independently tested corpus (never vendor self-reports): tier-health distribution, per-category health, new-entrant rate, public-surface readiness, EU AI Act Article-50 compliance bands, and the not-testable mortality signal. Every module carries its own method and coverage; signals th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional: return only the market summary plus this one category's block (e.g. 'Coding'). |
Query Hlido's market-intelligence store: durable, evidence-cited claims about the AI-agent market and adjacent domains (agent economy, payments rails, EU compliance), each with dated evidence, confidence, and typed relations to other intel. Filter by any facet: sector (ISIC code or text), geo (ISO country or region like 'eu'/'intl'), compliance (e.g. 'eu-ai-act-art50'), protocol (e.g. 'x402'), kin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sector | string | no | ISIC section/division code (e.g. 'K.64', 'J.62') or free-text sector match. |
| geo | string | no | ISO-3166 country code or region: 'cz', 'de', 'eu', 'intl', ... |
| compliance | string | no | Named regulation, any jurisdiction (e.g. 'eu-ai-act-art50', 'gdpr'). |
| protocol | string | no | e.g. 'mcp', 'x402', 'api', 'cli' |
| kind | string | no | Filter by record kind. |
| audience | string | no | — |
| maturity | string | no | — |
| text | string | no | Free-text match over headlines (fallback lens — prefer facets). |
| limit | integer | no | Max records (default 10, max 50). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hlido Agent Reviews or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Hlido Agent Reviews can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.