eu.hlido/mcp

Est-ce que eu.hlido/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « eu.hlido/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 19 outils

• commerce_check≈ 204 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • agent_or_url · string · requis
    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.

  Exemple d'appel

  {"name": "commerce_check", "arguments": {"agent_or_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• compare_agents≈ 200 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • slugs · array · requis
    List of 2 to 5 Hlido agent slugs to compare side by side (e.g. ['aider','cursor','opencode']).

  Exemple d'appel

  {"name": "compare_agents", "arguments": {"slugs": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explain≈ 204 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    The agent's Hlido slug
  • dimension · string · optionnel
    Optional dimension filter. Run without and check supported_dimensions in response if unsure.

  Exemple d'appel

  {"name": "explain", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_similar_agents≈ 238 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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "find_similar_agents", "arguments": {"description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_trusted≈ 260 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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "find_trusted", "arguments": {"need": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_behavioral_trace≈ 226 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    The Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode')
  • spec_version · string · optionnel
    Behavioral spec version (default 'v0.1'). Omit to get the latest available.

  Exemple d'appel

  {"name": "get_behavioral_trace", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_incidents≈ 284 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.

  Paramètres, retour & exemple (4)

  Paramètres

  • slug · string · optionnel
    Optional: only incidents for this agent slug
  • limit · integer · optionnel
    Max results (default 20, max 100)
  • category · string · optionnel · hallucination | regression | safety | availability | cost | other
    Optional category filter
  • severity · string · optionnel · low | medium | high | critical
    Optional minimum-interest filter (exact match)

  Exemple d'appel

  {"name": "get_incidents", "arguments": {"slug": "texte", "limit": 1, "category": "hallucination", "severity": "low"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_scorecard≈ 144 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    The agent's Hlido slug (e.g. 'aider', 'gumloop')

  Exemple d'appel

  {"name": "get_scorecard", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• intel_query≈ 461 tokens

  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'), kind (fact/estimate/trend/signal), audience, maturity. Facet vocabularies + per-value record counts: https://hlido.eu/data/intel/taxonomy.json (fetch that first to see what's queryable). A zero-result query returns an honest empty AND is logged — misses drive what Hlido collects next, so check back. Free at answer-time, declared policy.

  Paramètres, retour & exemple (9)

  Paramètres

  • geo · string · optionnel
    ISO-3166 country code or region: 'cz', 'de', 'eu', 'intl', ...
  • kind · string · optionnel · fact | estimate | trend | signal
    Filter by record kind.
  • text · string · optionnel
    Free-text match over headlines (fallback lens — prefer facets).
  • limit · integer · optionnel
    Max records (default 10, max 50).
  • sector · string · optionnel
    ISIC section/division code (e.g. 'K.64', 'J.62') or free-text sector match.
  • audience · string · optionnel · b2b | b2c | b2g | mixed
  • maturity · string · optionnel · emerging | growing | consolidating | declining
  • protocol · string · optionnel
    e.g. 'mcp', 'x402', 'api', 'cli'
  • compliance · string · optionnel
    Named regulation, any jurisdiction (e.g. 'eu-ai-act-art50', 'gdpr').

  Exemple d'appel

  {"name": "intel_query", "arguments": {"geo": "texte", "kind": "fact", "text": "texte", "limit": 1, "sector": "texte", "audience": "b2b"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• market_pulse≈ 243 tokens

  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 that cannot be measured this edition say 'unmeasured' rather than guessing. Use this for market-level questions ('is category X healthy?', 'how fast are agents entering/dying?'); for one specific agent use trust_check instead. Free, regenerated weekly.

  Paramètres, retour & exemple (1)

  Paramètres

  • category · string · optionnel
    Optional: return only the market summary plus this one category's block (e.g. 'Coding').

  Exemple d'appel

  {"name": "market_pulse", "arguments": {"category": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• recommend≈ 309 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • constraints · object · requis

  Exemple d'appel

  {"name": "recommend", "arguments": {"constraints": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• report_review_issue≈ 249 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.

  Paramètres, retour & exemple (4)

  Paramètres

  • slug · string · requis
    The slug whose review has the issue
  • detail · string · requis
    What's wrong, with a concrete reference (URL, claim id, etc) if possible
  • reporter · string · optionnel
    Optional self-identifier — agent name or email — purely informational
  • issue_type · string · requis · stale | wrong_verdict | missing_claim | broken_link | other
    Category of the report

  Exemple d'appel

  {"name": "report_review_issue", "arguments": {"slug": "texte", "detail": "texte", "issue_type": "stale"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• request_quick_audit≈ 271 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).

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "request_quick_audit", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• scan_mcp≈ 339 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/

  Paramètres, retour & exemple (2)

  Paramètres

  • server · string · requis
    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 repo URL (queued for sandbox scan).
  • requester · string · optionnel
    Optional self-identifier — agent name or email — for follow-up when a queued scan completes.

  Exemple d'appel

  {"name": "scan_mcp", "arguments": {"server": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_agent≈ 281 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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "submit_agent", "arguments": {"url": "texte", "name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• subscribe≈ 191 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    The Hlido slug to subscribe to (e.g. 'cursor', 'aider')
  • channel · string · optionnel · rss | json | webhook
    Preferred notification channel. webhook is advisory only until Wave 3 ships.

  Exemple d'appel

  {"name": "subscribe", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• trust_check≈ 298 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • use_case · string · optionnel
    Optional. The task you're considering this agent for (e.g. 'multi-file TypeScript refactor'); tailors the verdict to that use case when provided.
  • agent_or_url · string · requis
    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.

  Exemple d'appel

  {"name": "trust_check", "arguments": {"agent_or_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_claim≈ 208 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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "verify_claim", "arguments": {"agent": "texte", "claim": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_transparency≈ 275 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.

  Paramètres, retour & exemple (1)

  Paramètres

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

  Exemple d'appel

  {"name": "verify_transparency", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://hlido.eu/mcp