← Back to search
ankitkapur1992-hlido/hlido-mcp

hlido-mcp

Independent trust scores, claim audits, and side-by-side comparisons for AI agents, queryable over MCP. Every verdict is backed by hands-on testing and signed evidence from Hlido (hlido.eu). Hosted endpoint available at https://hlido.eu/mcp — no auth required.

Decision: Allow with approval
Why: exec-capable tools + no confirmation safeguards + high-risk tools need review
Next: export policy, require approval for writes, add authenticated validation
EXECUTIVE VERDICT

Executive verdict

Production trust decision: Allow with approval
Reason: exec-capable tools + no confirmation safeguards + high-risk tools need review
Next action: export policy, require approval for writes, add authenticated validation
Production decision
Allow with approval
exec-capable tools + no confirmation safeguards + high-risk tools need review
Current score
68.5
Snapshot trustsnap_84f3f2975755a03c
Next action
export policy, require approval for writes, add authenticated validation
Claim the profile to add evidence, trigger validation, and configure monitoring.
Compare alternatives Export policy Open report JSON
Observed Attention
Low observed attention
AI discovery detected. This MCP server has recently appeared in AI-assisted discovery or evaluation traffic on Verify.
  • AI crawler activity
  • profile inspection
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Claim this profile to control the metadata agents are reading and publish verified ownership, security contact, policy metadata, badge status, and Intelligence API fields.
Status
Healthy
Score
68.5
Transport
streamable-http
Tools
17

Current trust snapshot

Snapshot ID
trustsnap_84f3f2975755a03c
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Jul 31, 2026 02:06:49 PM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Jul 31, 2026 10:26:23 AM UTC
Age: 3.67h • freshness band: Verified in last 24h • display score: 68.47
Production trust decision
Allow with approval
exec-capable tools + no confirmation safeguards + high-risk tools need review
Readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.

Canonical machine links

SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.

1. Claim
unclaimed
with GitHub, DNS, or HTTP challenge instructions.
2. Revalidate
POST /v1/servers/ankitkapur1992-hlido/hlido-mcp/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 68.5 - last checked Jul 31, 2026
4. Monitor
Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.
Paid profile
Add verified publisher identity, security metadata, evidence packs, badge customization, and owner analytics without buying a better score.
Badge embed
[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/ankitkapur1992-hlido/hlido-mcp.svg)](https://verify.sentinelsignal.io/servers/ankitkapur1992-hlido/hlido-mcp)

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 52.2 • stale score suppressed:
Policy exports
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
Freshly Validated Claude Remote MCP Compatible No Critical Risk
Semantic benchmarks
available
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
metadata signal
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

MCP Runtime hosting

Verify Hosted MCP turns a trusted server report into a managed remote MCP endpoint with GitHub deployment provenance, sandbox policy, encrypted secrets, release history, rollback, and audit/usage events.

Activation readiness
Trusted hosted runtimes require fresh validation, a passing server state, a remote endpoint, and a minimum score.
Minimum tier
TrustOps
Publisher claim plus paid TrustOps tier are required before secrets or releases can be created.
Hosted endpoint
/hosted/{namespace}/{name}/mcp
The endpoint enforces egress allowlists and records audit/usage events.
Blockers
score_below_hosting_threshold
DeploymentStatusEndpointRelease
No hosted runtime deployments yet.

Production readiness class

Production readiness class
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
76.2
Based on 1 recent validations, 26 captured checks, and validation age of 3.7 hours.
Live checks captured
26
More direct checks increase trust in the current verdict.
Validation age
3.7h
Lower age means fresher evidence.

Recommended for

Claude Desktop
Claude Desktop is marked compatible with score 83.
Smithery
Smithery is marked compatible with score 100.
Generic Streamable HTTP
Generic Streamable HTTP is marked compatible with score 100.

Client compatibility verdicts

Client compatibility only means the server shape can work with a client. Production trust decision and write-action publishing are evaluated separately so a client-compatible server can still be blocked for production.

Client compatibility: ChatGPT
Partially client-compatible
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
  • step_up_auth_probeMissing
  • connector_replay_probeMissing — Frozen tool snapshots must survive refresh.
  • request_association_probeMissing — Roots, sampling, and elicitation should stay request-scoped.
Client compatibility: Claude
Client-compatible
Transport behavior should match Claude-compatible HTTP expectations.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history, server_card
Disagreements: none
  • initializeOK
  • tools_listOK
  • transport_compliance_probeError
Write-action publishing
Publishing blocked
Blocked until safeguards and confirmation semantics are verified for write, exec, or destructive tools.
Confidence: high (76.25)
Evidence provenance
Winner: live_validation
Supporting sources: live_validation, history
Disagreements: none
  • action_safety_probeError
Snapshot churn risk
Low
No material tool-surface churn detected in the latest comparison.
Confidence: high (76.25)
Evidence provenance
Winner: history
Supporting sources: history, live_validation
Disagreements: none
  • tool_snapshot_probeMissing
  • connector_replay_probeMissing

Why compatibility is limited by client

ChatGPT custom connector
Partially client-compatible
Remediation checklist
  • OpenAI connectors expect OAuth for remote server auth.
  • Dynamic client registration materially improves connector setup.
  • Transport compliance should be in good shape.
  • search fetch only is not yet satisfied
  • oauth configured is not yet satisfied
  • admin refresh required is not yet satisfied
Claude remote MCP
Client-compatible
Remediation checklist
  • Transport behavior should match Claude-compatible HTTP expectations.
  • search fetch only is not yet satisfied
  • oauth configured is not yet satisfied
  • admin refresh required is not yet satisfied
  • safe for company knowledge is not yet satisfied
  • safe for messages api remote mcp is not yet satisfied
Write-safe publishing
Blocked
Remediation checklist
  • Add a clearer auth boundary around risky write actions.
  • Constrain or sandbox exec-capable tools before publishing broadly.

Verdict traces

Production verdict
Safe for evaluation
The server is suitable for evaluation, but remaining gaps should be resolved before broad production use.
Confidence: high (76.25)
Winning source: live_validation
Triggering alerts
  • No active alert triggers.
Client verdict trace table
VerdictStatusChecksWinning sourceConflicts
openai_connectors Partially client-compatible initialize, tools_list, transport_compliance_probe, step_up_auth_probe, connector_replay_probe, request_association_probe live_validation none
claude_desktop Client-compatible initialize, tools_list, transport_compliance_probe live_validation none
unsafe_for_write_actions Publishing blocked action_safety_probe live_validation none
snapshot_churn_risk Low tool_snapshot_probe, connector_replay_probe history none

Publishability policy profiles

ChatGPT custom connector compatibility
Compatible with review
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No
Claude remote MCP compatibility
Connector-compatible
Transport behavior should match Claude-compatible HTTP expectations. Compatibility is not a production approval; company knowledge and Messages API gates remain separate.
  • Search Fetch Only: No
  • Write Actions Present: Yes
  • Oauth Configured: No
  • Admin Refresh Required: No
  • Safe For Company Knowledge: No
  • Safe For Messages Api Remote Mcp: No

Compatibility fixtures

ChatGPT custom connector fixture
Degraded
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
  • remote_http_endpoint: Passes
  • oauth_discovery: Degraded
  • frozen_tool_snapshot_refresh: Passes
  • request_association: Passes
Anthropic remote MCP fixture
Degraded
Transport behavior should match Claude-compatible HTTP expectations.
  • remote_transport: Passes
  • tool_discovery: Passes
  • auth_connect: Passes
  • safe_write_review: Degraded

Authenticated validation sessions

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Latest profile
remote_mcp
Authenticated session used
Public score isolation
Preview endpoint
/v1/verify
CI preview endpoint
/v1/ci/preview

Public server reputation

Validation success 7d
1.0
Validation success 30d
1.0
Mean time to recover
n/a
Breaking diffs 30d
0
Registry drift frequency 30d
0
Snapshot changes 30d
0

Incident & change feed

TimestampEventDetails
Jul 31, 2026 10:26:23 AM UTC Latest validation: healthy Score 68.5 with status healthy.

Capabilities

Use-case taxonomy
development database search productivity

Security posture

Tools analyzed
17
High-risk tools
3
Destructive tools
0
Exec tools
4
Egress tools
6
Secret tools
2
Bulk-access tools
2
Risk distribution
low:3, medium:11, high:2, critical:1

Agent Commerce & Payment Readiness - Beta

Beta assessment. Verify separates commerce-adjacent context from observed payment execution. Usage, billing, pricing, card, wallet, or meter terms alone do not make a server payment-capable. This is not a certification of safety, compliance, or fraud prevention.

Overall
36
Auth posture
10
Payment readiness
60
Delegation safety
30
Tool risk
35
Commerce signal: moderate Payment capable: inferred Payment execution: no Billing/usage context: no Quote/pricing context: yes Numeric price context: yes Commercial quote context: yes Checkout/charge signal: no Checkout term observed: no Human confirmation: yes Spending policy: yes Receipt support: unknown Auth required: no Operator identity: declared Tool risk: write capable Delegation level: research only
Detected payment rails
ACP, AP2
Purchase stages
none detected
Evidence level
inferred
Confidence
medium

Warnings

Evidence

FieldValueSourceMatched termsConfidence
commerce_signalmoderatetool_schemasubscribe, limit, quote, interest, ratemedium
payment_railsACP, AP2tool_schemaacp, ap2medium

Recommended operator fixes

Tool capability & risk inventory

ToolCapabilitiesRiskFindingsNotes
trust_check read exec network filesystem High command execution arbitrary network egress freeform input surface No explicit safeguard hints detected.
find_trusted read network filesystem export Medium bulk data access No explicit safeguard hints detected.
verify_claim network Medium none No explicit safeguard hints detected.
compare_agents read Low none No explicit safeguard hints detected.
submit_agent read write network Medium arbitrary network egress freeform input surface Safeguards hinted in metadata.
verify_transparency read write network Medium arbitrary network egress freeform input surface No explicit safeguard hints detected.
get_scorecard read Low none No explicit safeguard hints detected.
get_incidents read export Medium bulk data access No explicit safeguard hints detected.
report_review_issue read write network Medium none No explicit safeguard hints detected.
request_quick_audit read network secrets High arbitrary network egress secret material access freeform input surface No explicit safeguard hints detected.
find_similar_agents read network filesystem Medium none No explicit safeguard hints detected.
subscribe read network Medium none No explicit safeguard hints detected.
explain read exec network Medium command execution No explicit safeguard hints detected.
recommend read Low none No explicit safeguard hints detected.
get_behavioral_trace read exec Medium command execution No explicit safeguard hints detected.
commerce_check read network Medium arbitrary network egress freeform input surface No explicit safeguard hints detected.
scan_mcp read write exec network filesystem secrets Critical command execution arbitrary network egress secret material access filesystem mutation Safeguards hinted in metadata.

Write-action governance

Governance status
Error
Safe to publish
Auth boundary
public_or_unclear
Blast radius
High
High-risk tools
3
Confirmation signals
submit_agent, subscribe
Safeguard count
2

Status detail: 3 high-risk tool(s), 4 exec-capable tool(s) are exposed without a clear auth boundary; 2 safeguard(s) and 2 confirmation signal(s) detected.

ToolRiskFlagsSafeguards
trust_check High command execution arbitrary network egress freeform input surface no
request_quick_audit High arbitrary network egress secret material access freeform input surface no
scan_mcp Critical command execution arbitrary network egress secret material access filesystem mutation yes

Action-controls diff

Snapshot changed
no
Disabled-by-default candidates
none
Manual review candidates
none
New actions
ActionRiskFlags
No newly added actions.
Changed actions
ActionChange typesRisk
No materially changed actions.

Why this score?

Access & Protocol
32/44
Connectivity, auth, and transport expectations for common clients.
Interface Quality
35.8/56
How well the tool/resource interface communicates and behaves under automation.
Security Posture
24.2/36
How safely the exposed tool surface handles destructive actions, egress, execution, secrets, and risky inputs.
Reliability & Trust
18.75/24
Operational stability, consistency, and trustworthiness over time.
Discovery & Governance
18.45/28
How well the server is documented, listed, and governed in public registries.
Adoption & Market
5/8
Adoption clues and public evidence that the server is intended for external use.

Algorithmic score breakdown

Auth Operability
2/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
3.4/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
2/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
2/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
4/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
4/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
4/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
1.8/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
4/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
1.5/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
1.5/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
2/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
4/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
4/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
3/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
2/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
3/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
2.4/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
4/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
3/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
4/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
4/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
3/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
0/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
3/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
3/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
2/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
3/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
4/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
2.5/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
1/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3.7/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
2/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
3/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
4/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

OpenAI Connectors
66.7
partial
OpenAI connectors expect OAuth for remote server auth.; Dynamic client registration materially improves connector setup.; Transport compliance should be in good shape.
Connector URL: https://hlido.eu/mcp
# No OAuth metadata detected.
# Server: ankitkapur1992-hlido/hlido-mcp
Claude Desktop
83.3
compatible
Transport behavior should match Claude-compatible HTTP expectations.
{
  "mcpServers": {
    "hlido-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://hlido.eu/mcp"]
    }
  }
}
Smithery
100.0
compatible
No major blockers detected.
smithery mcp add "https://hlido.eu/mcp"
Generic Streamable HTTP
100.0
compatible
No major blockers detected.
curl -sS https://hlido.eu/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Actionable remediation

SeverityRemediationWhy it mattersRecommended action
High Add confirmation and dry-run semantics for risky actions High-risk write, delete, exec, or egress tools should communicate safeguards clearly. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Align session and protocol behavior with Streamable HTTP expectations Clients increasingly rely on MCP-Protocol-Version, session teardown, and expired-session semantics. Align MCP-Protocol-Version, MCP-Session-Id, DELETE teardown, and expired-session handling with the transport spec.
Playbook
  • Return `Mcp-Session-Id` and `Mcp-Protocol-Version` headers consistently on streamable HTTP responses.
  • Honor `DELETE` session teardown and return `404` when a deleted session is reused.
  • Reject invalid protocol-version headers with `400 Bad Request`.
High Associate roots, sampling, and elicitation with active client requests Modern MCP guidance expects roots, sampling, and elicitation traffic to be tied to an active client request instead of arriving unsolicited on idle sessions. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Expose /.well-known/oauth-protected-resource Without a protected-resource document, OAuth clients cannot discover auth requirements reliably. Serve /.well-known/oauth-protected-resource and point it at your authorization server metadata.
Playbook
  • Serve `/.well-known/oauth-protected-resource` from the same host as the MCP endpoint.
  • Point it at the authorization server metadata URL.
  • Confirm clients receive consistent auth hints before tool execution.
High Keep connector refreshes backward compatible Managed connector clients freeze tool snapshots, so removed tools, new required args, and breaking output changes can break published integrations after refresh. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
High Publish OAuth authorization-server metadata Clients need authorization-server metadata to discover issuer, endpoints, and DCR support. Publish /.well-known/oauth-authorization-server from your issuer and include registration_endpoint when supported.
Playbook
  • Publish `/.well-known/oauth-authorization-server` from the issuer.
  • Add `registration_endpoint` if DCR is supported.
  • Verify issuer, authorization, token, and jwks metadata are all reachable.
High Stop asking users to paste secrets directly Public MCP servers should prefer OAuth or browser-based auth guidance over in-band secret collection. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Adopt a current MCP protocol revision Older protocol revisions reduce compatibility with newer clients and registry programs. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Close connector-publishing gaps Connector catalogs care about protocol recency, session behavior, auth clarity, and tool-surface stability. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Document minimal scopes and return cleaner auth challenges Modern clients expect granular scopes and step-up auth signals such as WWW-Authenticate scope hints. Return granular scopes and WWW-Authenticate challenge hints instead of forcing overly broad auth upfront.
Playbook
  • Advertise the narrowest viable scopes in OAuth metadata.
  • Return `WWW-Authenticate` challenges with scope or insufficient-scope hints when additional consent is needed.
  • Revalidate with both public discovery and auth-required flows.
Medium Publish OpenID configuration OIDC metadata improves token validation and client compatibility. Expose /.well-known/openid-configuration with issuer, jwks_uri, and supported grants.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Reduce tool-surface churn Frequent add/remove or output-shape drift makes published connectors and cached tool snapshots brittle. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Medium Repair prompts/list or stop advertising prompts Prompt metadata should either work live or be removed from the advertised capability set. Only advertise prompts if prompts/list works and prompt arguments are documented.
Playbook
  • Only advertise prompts that are actually accessible.
  • Add prompt descriptions and argument docs.
  • Run a live `prompts/list` check after any prompt changes.
Medium Repair resources/list or stop advertising resources Resource metadata should either work live or be removed from the advertised capability set. Only advertise resources if resources/list works and resources expose stable URIs/types.
Playbook
  • Only advertise resources with stable URIs and read semantics.
  • Add MIME/type hints where possible.
  • Run a live `resources/list` and `resources/read` check after updates.
Medium Support resumable HTTP sessions cleanly Modern MCP clients increasingly expect resumable session behavior on streamable HTTP transports. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Expose modern utility surfaces like completions, pagination, or tasks Utility coverage improves interoperability with larger clients and long-lived agent workflows. Expose completions, pagination, and task metadata where supported so larger clients can plan and resume work safely.
Playbook
  • Advertise `completions`, pagination cursors, and `tasks` only when they are actually supported.
  • Return `nextCursor` on large list operations when pagination is available.
  • Document task support and whether it requires step-up auth.
Low Publish newer MCP capability signals Roots, sampling, elicitation, structured outputs, and related metadata improve client understanding and ranking. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.
Low Publish or reconcile the server in the official MCP registry Official registry presence improves discovery confidence and cross-source consistency. Inspect the latest validation evidence and resolve the client-visible regression.
Playbook
  • Inspect the latest validation evidence.
  • Resolve the highest-severity client-facing gap first.
  • Revalidate and confirm the score and verdict improve.

Point loss breakdown

ComponentCurrentPoints missing
Transport Compliance 0/4 -4.0
Dependency Supply Chain Signal 0.5/4 -3.5
Execution Sandbox Safety 1/4 -3.0
Resource Contract 1.5/4 -2.5
Prompt Contract 1.5/4 -2.5
Trust Confidence 1.8/4 -2.2
Utility Coverage 2/4 -2.0
Secret Handling Hygiene 2/4 -2.0
Schema Completeness 2/4 -2.0
Result Shape Stability 2/4 -2.0
Registry Consistency 2/4 -2.0
Rate Limit Semantics 2/4 -2.0

Validation diff

Need at least two validation runs before diffing changes.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

Status
Missing
Backward compatible
Would break after refresh
Added tools
none
Removed tools
none
Additive output changes
none
Required-argument replay breaks
ToolAdded required argsRemoved required args
No required-argument replay breaks detected.
Output-schema replay breaks
ToolRemoved propertiesAdded properties
No output-schema replay breaks detected.

Transport compliance drilldown

Probe status
Error
Transport
streamable-http
Session header
no
Protocol header
no
Bad protocol response
200
DELETE teardown
n/a
Expired session retry
n/a
Last-Event-ID visible
no

Issues: missing_session_id, missing_protocol_header, bad_protocol_not_rejected

Request association

Status
Missing
Advertised capabilities
none
Observed idle methods
none
Violating methods
none
Probe HTTP status
n/a
Issues
none

Utility coverage

Probe status
Missing
Completions
not detected
Completion probe target: none
Pagination
not detected
No nextCursor evidence.
Tasks
Missing
Advertised: no

Benchmark tasks

Benchmark taskStatusEvidence
Discover tools Passes
  • initializeOK
  • tools_listOK
Read-only fetch flow Degraded
  • resource_readMissing
  • read_only_tool_surfaceOK
OAuth-required connect Degraded
  • oauth_protected_resourceError
  • step_up_auth_probeMissing
Safe write flow with confirmation Likely to fail
  • action_safety_probeError

Registry & provenance divergence

Probe status
OK
Direct official match
no
Drift fields
none
FieldRegistryLive server card
Titlen/ahlido-agent-reviews
Versionn/a3.2.0
Homepagen/an/a

Active alerts

No active alerts for the current server state.

Aliases & registry graph

IdentifierSourceCanonicalScore
ankitkapur1992-hlido/hlido-mcp glama_registry yes 68.47
awesome-ankitkapur1992-hlido/hlido-mcp awesome_mcp_servers no 46.71

Alias consolidation

Source disagreements
FieldWhat differsObserved values
Registry source Multiple registries or registry sync paths claim this same canonical server. awesome_mcp_servers glama_registry
Remote URL Aliases currently point at different MCP endpoints, which can indicate mirrors, stale registry data, or a real endpoint split. https://glama.ai/mcp/servers/ankitkapur1992-hlido/hlido-mcp/badges/score.svg)](https://glama.ai/mcp/servers/ankitkapur1992-hlido/hlido-mcp https://hlido.eu/mcp
Homepage Registry entries disagree on the primary homepage for this server. https://github.com/ankitkapur1992-hlido/hlido-mcp https://glama.ai/mcp/servers/f3lbnk9mwd
Registry identifier Different registry-specific identifiers resolve to the same canonical server record here. awesome_mcp_servers:ankitkapur1992-hlido/hlido-mcp glama_registry:f3lbnk9mwd

Install snippets

Openai Connectors
Connector URL: https://hlido.eu/mcp
# No OAuth metadata detected.
# Server: ankitkapur1992-hlido/hlido-mcp
Claude Desktop
{
  "mcpServers": {
    "hlido-mcp": {
      "command": "npx",
      "args": ["mcp-remote", "https://hlido.eu/mcp"]
    }
  }
}
Smithery
smithery mcp add "https://hlido.eu/mcp"
Generic Http
curl -sS https://hlido.eu/mcp -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"mcp-verify","version":"0.1.0"}}}'

Agent access & tool surface

Live server tools
trust_check find_trusted verify_claim compare_agents submit_agent verify_transparency get_scorecard get_incidents
Observed from the latest live validation against https://hlido.eu/mcp. This is the target server surface, not Verify's own inspection tools.
Live capability counts
17 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for ankitkapur1992-hlido/hlido-mcp.
Direct machine links

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

Active watches
0
Generic webhooks
0
Slack routes
0
Teams routes
0
Email routes
0
WatchTeamChannelsMinimum severity
No active watch destinations.

Maintainer analytics

Validation Run Count
1
Average Latency Ms
448.42
Healthy Run Ratio Recent
1.0
Registry Presence Count
2
Active Alert Count
0
Watcher Count
0
Verified Claim
False
Taxonomy Tags
development, database, search, productivity
Score Trend
68.47
Remediation Count
18
High Risk Tool Count
3
Destructive Tool Count
0
Exec Tool Count
4

Maintainer response quality

Score
33.33
Verified claim
Support contact
Changelog present
Incident notes present
Tool changes documented
Annotation history
Annotation count
0

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Latest validation evidence

Latest summary
Healthy
Validation profile
remote_mcp
Started
Jul 31, 2026 10:26:23 AM UTC
Latency
448.4 ms

Failures

Checks

CheckStatusLatencyEvidence
action_safety_probe Error n/a 3 high-risk, 4 exec-capable tool(s); no clear auth boundary; safeguards=2; confirmation=submit agent, subscribe.
advanced_capabilities_probe Missing n/a No advanced MCP capability signals detected.
connector_publishability_probe Warning n/a Publishability blockers: transport compliance, action safety.
connector_replay_probe Missing n/a No connector replay evidence recorded.
determinism_probe OK 9.8 ms Check completed
initialize OK 76.1 ms Protocol 2024-11-05
interactive_flow_probe Missing n/a Check completed
oauth_authorization_server Missing n/a no authorization server
oauth_protected_resource Error 43.7 ms Client error '404 Not Found' for url 'https://hlido.eu/.well-known/oauth-protected-resource' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
official_registry_probe Warning n/a Check completed
openid_configuration Missing n/a no authorization server
probe_noise_resilience OK 84.1 ms Fetched https://hlido.eu/robots.txt
prompt_get Missing n/a no prompt name
prompts_list Error 7.4 ms JSON-RPC error -32601: Method not found: prompts/list
protocol_version_probe Warning n/a Claims 2024-11-05; 3 release(s) behind 2025-11-25.
provenance_divergence_probe OK n/a Check completed
request_association_probe Missing n/a No request-association capabilities were advertised.
resource_read Missing n/a no resource uri
resources_list Error 7.3 ms JSON-RPC error -32601: Method not found: resources/list
server_card OK 168.7 ms capabilities, contact, description, documentation
session_resume_probe Warning n/a no session id
step_up_auth_probe Missing n/a No OAuth or incremental-scope signals detected.
tool_snapshot_probe Missing n/a no historical snapshot
tools_list OK 8.9 ms 17 tool(s) exposed
transport_compliance_probe Error 9.5 ms Issues: missing session id, missing protocol header, bad protocol not rejected (bad protocol=200).
utility_coverage_probe Missing 8.7 ms No completions evidence; no pagination evidence; tasks missing.

Raw evidence view

Show raw JSON evidence
{
  "checks": {
    "action_safety_probe": {
      "details": {
        "auth_present": false,
        "confirmation_signals": [
          "submit_agent",
          "subscribe"
        ],
        "safeguard_count": 2,
        "summary": {
          "bulk_access_tools": 2,
          "capability_distribution": {
            "exec": 4,
            "export": 2,
            "filesystem": 4,
            "network": 12,
            "read": 16,
            "secrets": 2,
            "write": 4
          },
          "destructive_tools": 0,
          "egress_tools": 6,
          "exec_tools": 4,
          "high_risk_tools": 3,
          "risk_distribution": {
            "critical": 1,
            "high": 2,
            "low": 3,
            "medium": 11
          },
          "secret_tools": 2,
          "tool_count": 17
        }
      },
      "latency_ms": null,
      "status": "error"
    },
    "advanced_capabilities_probe": {
      "details": {
        "capabilities": {
          "completions": false,
          "elicitation": false,
          "prompts": false,
          "resource_links": false,
          "resources": false,
          "roots": false,
          "sampling": false,
          "structured_outputs": false
        },
        "enabled": [],
        "enabled_count": 0,
        "initialize_capability_keys": [
          "tools"
        ]
      },
      "latency_ms": null,
      "status": "missing"
    },
    "connector_publishability_probe": {
      "details": {
        "blockers": [
          "transport_compliance",
          "action_safety"
        ],
        "criteria": {
          "action_safety": false,
          "auth_flow": true,
          "connector_replay": true,
          "initialize": true,
          "protocol_version": true,
          "remote_transport": true,
          "request_association": true,
          "server_card": true,
          "session_resume": true,
          "step_up_auth": true,
          "tool_surface": true,
          "tools_list": true,
          "transport_compliance": false
        },
        "high_risk_tools": 3,
        "tool_count": 17,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "connector_replay_probe": {
      "details": {
        "reason": "no_historical_snapshot"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "determinism_probe": {
      "details": {
        "attempts": 2,
        "baseline_signature": "36f7b162f3d5586171852d1535b45533eb79f84e9fefba50052aaea73319a6a5",
        "errors": [],
        "matches": 2,
        "stable_ratio": 1.0,
        "successful": 2
      },
      "latency_ms": 9.81,
      "status": "ok"
    },
    "initialize": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "id": 1,
          "jsonrpc": "2.0",
          "result": {
            "capabilities": {
              "tools": {}
            },
            "protocolVersion": "2024-11-05",
            "serverInfo": {
              "name": "hlido-agent-reviews",
              "version": "3.3.0-workers"
            }
          }
        },
        "url": "https://hlido.eu/mcp"
      },
      "latency_ms": 76.11,
      "status": "ok"
    },
    "interactive_flow_probe": {
      "details": {
        "oauth_supported": false,
        "prompt_available": false,
        "risk_hits": [],
        "safe_hits": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_authorization_server": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "oauth_protected_resource": {
      "details": {
        "error": "Client error '404 Not Found' for url 'https://hlido.eu/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
        "url": "https://hlido.eu/.well-known/oauth-protected-resource"
      },
      "latency_ms": 43.71,
      "status": "error"
    },
    "official_registry_probe": {
      "details": {
        "direct_match": false,
        "official_identifiers": [
          "ai.agentutility/mcp-bestiary",
          "ai.ai-akari/one-minute-akari",
          "ai.artidrop/artidrop",
          "ai.agentutility/mcp-browser-workflow",
          "ai.adramp/google-ads",
          "ai.adweave/meta-ads-mcp",
          "ai.agentutility/mcp-edge-finance",
          "ai.aetherwealth/mcp",
          "ai.afmr/discovery",
          "ai.agentberg/agentberg"
        ],
        "official_peer_count": 10,
        "registry_source": "glama_registry"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "openid_configuration": {
      "details": {
        "reason": "no_authorization_server"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "probe_noise_resilience": {
      "details": {
        "headers": {
          "content-type": "text/plain; charset=utf-8"
        },
        "http_status": 200,
        "url": "https://hlido.eu/robots.txt"
      },
      "latency_ms": 84.11,
      "status": "ok"
    },
    "prompt_get": {
      "details": {
        "reason": "no_prompt_name"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "prompts_list": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found: prompts/list"
          },
          "id": 3,
          "jsonrpc": "2.0"
        },
        "url": "https://hlido.eu/mcp"
      },
      "latency_ms": 7.43,
      "status": "error"
    },
    "protocol_version_probe": {
      "details": {
        "claimed_version": "2024-11-05",
        "lag_days": 385,
        "latest_known_version": "2025-11-25",
        "releases_behind": 3,
        "validator_protocol_version": "2025-03-26"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "provenance_divergence_probe": {
      "details": {
        "direct_official_match": false,
        "drift_fields": [],
        "metadata_document_count": 2,
        "registry_homepage": null,
        "registry_repository": null,
        "registry_title": null,
        "registry_version": null,
        "server_card_homepage": null,
        "server_card_repository": null,
        "server_card_title": "hlido-agent-reviews",
        "server_card_version": "3.2.0"
      },
      "latency_ms": null,
      "status": "ok"
    },
    "request_association_probe": {
      "details": {
        "reason": "no_request_association_capabilities_advertised"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resource_read": {
      "details": {
        "reason": "no_resource_uri"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "resources_list": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "error": {
            "code": -32601,
            "message": "Method not found: resources/list"
          },
          "id": 5,
          "jsonrpc": "2.0"
        },
        "url": "https://hlido.eu/mcp"
      },
      "latency_ms": 7.3,
      "status": "error"
    },
    "server_card": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "capabilities": {
            "prompts": false,
            "resources": false,
            "tools": true
          },
          "contact": "ankit@hlido.eu",
          "description": "The independent trust layer for AI agents \u2014 each agent hands-on tested for one evidence-backed Laddoo Score (0-100). Query trust checks, scorecards, incidents, and recommendations over MCP.",
          "documentation": "https://hlido.eu/llms.txt",
          "endpoint": "https://hlido.eu/mcp",
          "publisher": "hlido.eu",
          "serverInfo": {
            "name": "hlido-agent-reviews",
            "version": "3.2.0"
          },
          "tools": [
            {
              "description": "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 \u2014 before delegating to, installing, or relying on another agent \u2014 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.",
              "name": "trust_check"
            },
            {
              "description": "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.",
              "name": "find_trusted"
            },
            {
              "description": "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 \u2014 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.",
              "name": "verify_claim"
            },
            {
              "description": "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.",
              "name": "compare_agents"
            },
            {
              "description": "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.",
              "name": "submit_agent"
            },
            {
              "description": "Check any AI agent's EU AI Act Article-50 transparency posture \u2014 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.",
              "name": "verify_transparency"
            },
            {
              "description": "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.",
              "name": "get_scorecard"
            },
            {
              "description": "Fetch published incidents from Hlido's NTSB-style failure registry \u2014 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.",
              "name": "get_incidents"
            },
            {
              "description": "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.",
              "name": "report_review_issue"
            },
            {
              "description": "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).",
              "name": "request_quick_audit"
            },
            {
              "description": "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 \u2014 much better than substring matching via find_trusted.",
              "name": "find_similar_agents"
            },
            {
              "description": "Preview \u2014 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.",
              "name": "subscribe"
            },
            {
              "description": "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.",
              "name": "explain"
            },
            {
              "description": "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.",
              "name": "recommend"
            },
            {
              "description": "Fetch the behavioral evaluation trace for a Hlido-reviewed agent \u2014 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.",
              "name": "get_behavioral_trace"
            },
            {
              "description": "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.",
              "name": "commerce_check"
            },
            {
              "description": "On-demand independent SAFETY scan of an MCP server \u2014 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 \u2014 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 \u2014 never assumed safe. Register of already-scanned servers: https://hlido.eu/mcp/",
              "name": "scan_mcp"
            }
          ],
          "transport": {
            "type": "streamable-http"
          },
          "transports": [
            "streamable-http",
            "http"
          ],
          "url": "https://hlido.eu/mcp"
        },
        "url": "https://hlido.eu/.well-known/mcp/server-card.json"
      },
      "latency_ms": 168.65,
      "status": "ok"
    },
    "session_resume_probe": {
      "details": {
        "protocol_version": "2024-11-05",
        "reason": "no_session_id",
        "resume_expected": true,
        "transport": "streamable-http"
      },
      "latency_ms": null,
      "status": "warning"
    },
    "step_up_auth_probe": {
      "details": {
        "auth_required_checks": [],
        "broad_scopes": [],
        "challenge_headers": [],
        "minimal_scope_documented": false,
        "oauth_present": false,
        "scope_specificity_ratio": 0.0,
        "step_up_signals": [],
        "supported_scopes": []
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tool_snapshot_probe": {
      "details": {
        "current_tool_count": 17,
        "reason": "no_historical_snapshot"
      },
      "latency_ms": null,
      "status": "missing"
    },
    "tools_list": {
      "details": {
        "headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "http_status": 200,
        "payload": {
          "id": 2,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "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 \u2014 before delegating to, installing, or relying on another agent \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "agent_or_url": {
                      "description": "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.",
                      "type": "string"
                    },
                    "use_case": {
                      "description": "Optional. The task you're considering this agent for (e.g. 'multi-file TypeScript refactor'); tailors the verdict to that use case when provided.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "agent_or_url"
                  ],
                  "type": "object"
                },
                "name": "trust_check"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "limit": {
                      "default": 10,
                      "description": "Maximum number of agents to return (default 10).",
                      "type": "integer"
                    },
                    "min_tier": {
                      "default": "STEADY",
                      "description": "Minimum trust tier to include (VITAL is strictest, FLATLINE allows all). Defaults to STEADY.",
                      "enum": [
                        "VITAL",
                        "STEADY",
                        "FADING",
                        "FLATLINE"
                      ],
                      "type": "string"
                    },
                    "need": {
                      "description": "Free-text description of the capability you need (e.g. 'CLI coding agent that edits multiple files at once').",
                      "type": "string"
                    }
                  },
                  "required": [
                    "need"
                  ],
                  "type": "object"
                },
                "name": "find_trusted"
              },
              {
                "description": "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 \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "agent": {
                      "description": "The agent's Hlido slug or product URL (e.g. 'cursor').",
                      "type": "string"
                    },
                    "claim": {
                      "description": "The specific claim to verify, in plain language (e.g. 'works offline' or 'SOC 2 compliant').",
                      "type": "string"
                    }
                  },
                  "required": [
                    "agent",
                    "claim"
                  ],
                  "type": "object"
                },
                "name": "verify_claim"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "slugs": {
                      "description": "List of 2 to 5 Hlido agent slugs to compare side by side (e.g. ['aider','cursor','opencode']).",
                      "items": {
                        "description": "A Hlido agent slug (e.g. 'aider').",
                        "type": "string"
                      },
                      "maxItems": 5,
                      "minItems": 2,
                      "type": "array"
                    }
                  },
                  "required": [
                    "slugs"
                  ],
                  "type": "object"
                },
                "name": "compare_agents"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "email": {
                      "description": "Optional contact email for the submitter \u2014 if you want a reply or a heads-up when the review publishes. Providing it always flags the submission to the Hlido team.",
                      "type": "string"
                    },
                    "name": {
                      "description": "Human-readable agent name (e.g. 'Example Coder').",
                      "type": "string"
                    },
                    "note": {
                      "description": "Optional context: what the agent does, or why it's worth reviewing.",
                      "type": "string"
                    },
                    "url": {
                      "description": "The agent's product or homepage URL (e.g. 'https://example.com').",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url",
                    "name"
                  ],
                  "type": "object"
                },
                "name": "submit_agent"
              },
              {
                "description": "Check any AI agent's EU AI Act Article-50 transparency posture \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "description": "The agent's product or homepage URL (e.g. 'https://example.com'), or its Hlido slug.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "type": "object"
                },
                "name": "verify_transparency"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "slug": {
                      "description": "The agent's Hlido slug (e.g. 'aider', 'gumloop')",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "get_scorecard"
              },
              {
                "description": "Fetch published incidents from Hlido's NTSB-style failure registry \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "category": {
                      "description": "Optional category filter",
                      "enum": [
                        "hallucination",
                        "regression",
                        "safety",
                        "availability",
                        "cost",
                        "other"
                      ],
                      "type": "string"
                    },
                    "limit": {
                      "default": 20,
                      "description": "Max results (default 20, max 100)",
                      "type": "integer"
                    },
                    "severity": {
                      "description": "Optional minimum-interest filter (exact match)",
                      "enum": [
                        "low",
                        "medium",
                        "high",
                        "critical"
                      ],
                      "type": "string"
                    },
                    "slug": {
                      "description": "Optional: only incidents for this agent slug",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "get_incidents"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "detail": {
                      "description": "What's wrong, with a concrete reference (URL, claim id, etc) if possible",
                      "type": "string"
                    },
                    "issue_type": {
                      "description": "Category of the report",
                      "enum": [
                        "stale",
                        "wrong_verdict",
                        "missing_claim",
                        "broken_link",
                        "other"
                      ],
                      "type": "string"
                    },
                    "reporter": {
                      "description": "Optional self-identifier \u2014 agent name or email \u2014 purely informational",
                      "type": "string"
                    },
                    "slug": {
                      "description": "The slug whose review has the issue",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug",
                    "issue_type",
                    "detail"
                  ],
                  "type": "object"
                },
                "name": "report_review_issue"
              },
              {
                "description": "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).",
                "inputSchema": {
                  "properties": {
                    "name": {
                      "description": "Optional human-readable name (we'll derive from URL if missing)",
                      "type": "string"
                    },
                    "requester": {
                      "description": "Optional self-identifier \u2014 agent name, email, or session id \u2014 for rate-limiting + follow-up",
                      "type": "string"
                    },
                    "url": {
                      "description": "Homepage or product URL of the agent to audit",
                      "type": "string"
                    },
                    "why": {
                      "description": "Optional one-liner: why are you considering this agent? helps us prioritize",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "type": "object"
                },
                "name": "request_quick_audit"
              },
              {
                "description": "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 \u2014 much better than substring matching via find_trusted.",
                "inputSchema": {
                  "properties": {
                    "description": {
                      "description": "Free-text description of the task or capability you need",
                      "type": "string"
                    },
                    "min_score": {
                      "default": 0,
                      "description": "Minimum Laddoo score filter (default 0)",
                      "type": "integer"
                    },
                    "top_k": {
                      "default": 5,
                      "description": "Number of matches to return (default 5, max 20)",
                      "type": "integer"
                    }
                  },
                  "required": [
                    "description"
                  ],
                  "type": "object"
                },
                "name": "find_similar_agents"
              },
              {
                "description": "Preview \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "channel": {
                      "description": "Preferred notification channel. webhook is advisory only until Wave 3 ships.",
                      "enum": [
                        "rss",
                        "json",
                        "webhook"
                      ],
                      "type": "string"
                    },
                    "slug": {
                      "description": "The Hlido slug to subscribe to (e.g. 'cursor', 'aider')",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "subscribe"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "dimension": {
                      "description": "Optional dimension filter. Run without and check supported_dimensions in response if unsure.",
                      "type": "string"
                    },
                    "slug": {
                      "description": "The agent's Hlido slug",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "explain"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "constraints": {
                      "additionalProperties": false,
                      "properties": {
                        "category": {
                          "description": "Filter by category (e.g. 'Coding', 'Voice', 'Productivity')",
                          "type": "string"
                        },
                        "max_results": {
                          "default": 5,
                          "description": "Cap on results (default 5, max 25)",
                          "type": "integer"
                        },
                        "min_score": {
                          "default": 0,
                          "description": "Minimum Laddoo score (0-100)",
                          "type": "integer"
                        },
                        "tier": {
                          "description": "Minimum tier filter (VITAL strictest, FLATLINE allows all)",
                          "enum": [
                            "VITAL",
                            "STEADY",
                            "FADING",
                            "FLATLINE"
                          ],
                          "type": "string"
                        },
                        "use_case": {
                          "description": "Free-text capability description for ranking (e.g. 'multi-file refactor in TypeScript')",
                          "type": "string"
                        }
                      },
                      "type": "object"
                    }
                  },
                  "required": [
                    "constraints"
                  ],
                  "type": "object"
                },
                "name": "recommend"
              },
              {
                "description": "Fetch the behavioral evaluation trace for a Hlido-reviewed agent \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "slug": {
                      "description": "The Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode')",
                      "type": "string"
                    },
                    "spec_version": {
                      "default": "v0.1",
                      "description": "Behavioral spec version (default 'v0.1'). Omit to get the latest available.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "get_behavioral_trace"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "agent_or_url": {
                      "description": "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.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "agent_or_url"
                  ],
                  "type": "object"
                },
                "name": "commerce_check"
              },
              {
                "description": "On-demand independent SAFETY scan of an MCP server \u2014 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 \u2014 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 \u2014 never assumed safe. Register of already-scanned servers: https://hlido.eu/mcp/",
                "inputSchema": {
                  "properties": {
                    "requester": {
                      "description": "Optional self-identifier \u2014 agent name or email \u2014 for follow-up when a queued scan completes.",
                      "type": "string"
                    },
                    "server": {
                      "description": "The MCP server to scan: an HTTP(S) MCP endpoint URL (e.g. 'https://mcp.example.com/mcp' \u2014 scanned live), OR an npm package (e.g. '@modelcontextprotocol/server-filesystem'), PyPI package, or GitHub repo URL (queued for sandbox scan).",
                      "type": "string"
                    }
                  },
                  "required": [
                    "server"
                  ],
                  "type": "object"
                },
                "name": "scan_mcp"
              }
            ]
          }
        },
        "url": "https://hlido.eu/mcp"
      },
      "latency_ms": 8.92,
      "status": "ok"
    },
    "transport_compliance_probe": {
      "details": {
        "bad_protocol_error": null,
        "bad_protocol_headers": {
          "content-type": "application/json; charset=utf-8"
        },
        "bad_protocol_payload": {
          "id": 410,
          "jsonrpc": "2.0",
          "result": {
            "tools": [
              {
                "description": "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 \u2014 before delegating to, installing, or relying on another agent \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "agent_or_url": {
                      "description": "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.",
                      "type": "string"
                    },
                    "use_case": {
                      "description": "Optional. The task you're considering this agent for (e.g. 'multi-file TypeScript refactor'); tailors the verdict to that use case when provided.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "agent_or_url"
                  ],
                  "type": "object"
                },
                "name": "trust_check"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "limit": {
                      "default": 10,
                      "description": "Maximum number of agents to return (default 10).",
                      "type": "integer"
                    },
                    "min_tier": {
                      "default": "STEADY",
                      "description": "Minimum trust tier to include (VITAL is strictest, FLATLINE allows all). Defaults to STEADY.",
                      "enum": [
                        "VITAL",
                        "STEADY",
                        "FADING",
                        "FLATLINE"
                      ],
                      "type": "string"
                    },
                    "need": {
                      "description": "Free-text description of the capability you need (e.g. 'CLI coding agent that edits multiple files at once').",
                      "type": "string"
                    }
                  },
                  "required": [
                    "need"
                  ],
                  "type": "object"
                },
                "name": "find_trusted"
              },
              {
                "description": "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 \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "agent": {
                      "description": "The agent's Hlido slug or product URL (e.g. 'cursor').",
                      "type": "string"
                    },
                    "claim": {
                      "description": "The specific claim to verify, in plain language (e.g. 'works offline' or 'SOC 2 compliant').",
                      "type": "string"
                    }
                  },
                  "required": [
                    "agent",
                    "claim"
                  ],
                  "type": "object"
                },
                "name": "verify_claim"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "slugs": {
                      "description": "List of 2 to 5 Hlido agent slugs to compare side by side (e.g. ['aider','cursor','opencode']).",
                      "items": {
                        "description": "A Hlido agent slug (e.g. 'aider').",
                        "type": "string"
                      },
                      "maxItems": 5,
                      "minItems": 2,
                      "type": "array"
                    }
                  },
                  "required": [
                    "slugs"
                  ],
                  "type": "object"
                },
                "name": "compare_agents"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "email": {
                      "description": "Optional contact email for the submitter \u2014 if you want a reply or a heads-up when the review publishes. Providing it always flags the submission to the Hlido team.",
                      "type": "string"
                    },
                    "name": {
                      "description": "Human-readable agent name (e.g. 'Example Coder').",
                      "type": "string"
                    },
                    "note": {
                      "description": "Optional context: what the agent does, or why it's worth reviewing.",
                      "type": "string"
                    },
                    "url": {
                      "description": "The agent's product or homepage URL (e.g. 'https://example.com').",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url",
                    "name"
                  ],
                  "type": "object"
                },
                "name": "submit_agent"
              },
              {
                "description": "Check any AI agent's EU AI Act Article-50 transparency posture \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "url": {
                      "description": "The agent's product or homepage URL (e.g. 'https://example.com'), or its Hlido slug.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "type": "object"
                },
                "name": "verify_transparency"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "slug": {
                      "description": "The agent's Hlido slug (e.g. 'aider', 'gumloop')",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "get_scorecard"
              },
              {
                "description": "Fetch published incidents from Hlido's NTSB-style failure registry \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "category": {
                      "description": "Optional category filter",
                      "enum": [
                        "hallucination",
                        "regression",
                        "safety",
                        "availability",
                        "cost",
                        "other"
                      ],
                      "type": "string"
                    },
                    "limit": {
                      "default": 20,
                      "description": "Max results (default 20, max 100)",
                      "type": "integer"
                    },
                    "severity": {
                      "description": "Optional minimum-interest filter (exact match)",
                      "enum": [
                        "low",
                        "medium",
                        "high",
                        "critical"
                      ],
                      "type": "string"
                    },
                    "slug": {
                      "description": "Optional: only incidents for this agent slug",
                      "type": "string"
                    }
                  },
                  "type": "object"
                },
                "name": "get_incidents"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "detail": {
                      "description": "What's wrong, with a concrete reference (URL, claim id, etc) if possible",
                      "type": "string"
                    },
                    "issue_type": {
                      "description": "Category of the report",
                      "enum": [
                        "stale",
                        "wrong_verdict",
                        "missing_claim",
                        "broken_link",
                        "other"
                      ],
                      "type": "string"
                    },
                    "reporter": {
                      "description": "Optional self-identifier \u2014 agent name or email \u2014 purely informational",
                      "type": "string"
                    },
                    "slug": {
                      "description": "The slug whose review has the issue",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug",
                    "issue_type",
                    "detail"
                  ],
                  "type": "object"
                },
                "name": "report_review_issue"
              },
              {
                "description": "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).",
                "inputSchema": {
                  "properties": {
                    "name": {
                      "description": "Optional human-readable name (we'll derive from URL if missing)",
                      "type": "string"
                    },
                    "requester": {
                      "description": "Optional self-identifier \u2014 agent name, email, or session id \u2014 for rate-limiting + follow-up",
                      "type": "string"
                    },
                    "url": {
                      "description": "Homepage or product URL of the agent to audit",
                      "type": "string"
                    },
                    "why": {
                      "description": "Optional one-liner: why are you considering this agent? helps us prioritize",
                      "type": "string"
                    }
                  },
                  "required": [
                    "url"
                  ],
                  "type": "object"
                },
                "name": "request_quick_audit"
              },
              {
                "description": "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 \u2014 much better than substring matching via find_trusted.",
                "inputSchema": {
                  "properties": {
                    "description": {
                      "description": "Free-text description of the task or capability you need",
                      "type": "string"
                    },
                    "min_score": {
                      "default": 0,
                      "description": "Minimum Laddoo score filter (default 0)",
                      "type": "integer"
                    },
                    "top_k": {
                      "default": 5,
                      "description": "Number of matches to return (default 5, max 20)",
                      "type": "integer"
                    }
                  },
                  "required": [
                    "description"
                  ],
                  "type": "object"
                },
                "name": "find_similar_agents"
              },
              {
                "description": "Preview \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "channel": {
                      "description": "Preferred notification channel. webhook is advisory only until Wave 3 ships.",
                      "enum": [
                        "rss",
                        "json",
                        "webhook"
                      ],
                      "type": "string"
                    },
                    "slug": {
                      "description": "The Hlido slug to subscribe to (e.g. 'cursor', 'aider')",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "subscribe"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "dimension": {
                      "description": "Optional dimension filter. Run without and check supported_dimensions in response if unsure.",
                      "type": "string"
                    },
                    "slug": {
                      "description": "The agent's Hlido slug",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "explain"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "constraints": {
                      "additionalProperties": false,
                      "properties": {
                        "category": {
                          "description": "Filter by category (e.g. 'Coding', 'Voice', 'Productivity')",
                          "type": "string"
                        },
                        "max_results": {
                          "default": 5,
                          "description": "Cap on results (default 5, max 25)",
                          "type": "integer"
                        },
                        "min_score": {
                          "default": 0,
                          "description": "Minimum Laddoo score (0-100)",
                          "type": "integer"
                        },
                        "tier": {
                          "description": "Minimum tier filter (VITAL strictest, FLATLINE allows all)",
                          "enum": [
                            "VITAL",
                            "STEADY",
                            "FADING",
                            "FLATLINE"
                          ],
                          "type": "string"
                        },
                        "use_case": {
                          "description": "Free-text capability description for ranking (e.g. 'multi-file refactor in TypeScript')",
                          "type": "string"
                        }
                      },
                      "type": "object"
                    }
                  },
                  "required": [
                    "constraints"
                  ],
                  "type": "object"
                },
                "name": "recommend"
              },
              {
                "description": "Fetch the behavioral evaluation trace for a Hlido-reviewed agent \u2014 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.",
                "inputSchema": {
                  "properties": {
                    "slug": {
                      "description": "The Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode')",
                      "type": "string"
                    },
                    "spec_version": {
                      "default": "v0.1",
                      "description": "Behavioral spec version (default 'v0.1'). Omit to get the latest available.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "slug"
                  ],
                  "type": "object"
                },
                "name": "get_behavioral_trace"
              },
              {
                "description": "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.",
                "inputSchema": {
                  "properties": {
                    "agent_or_url": {
                      "description": "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.",
                      "type": "string"
                    }
                  },
                  "required": [
                    "agent_or_url"
                  ],
                  "type": "object"
                },
                "name": "commerce_check"
              },
              {
                "description": "On-demand independent SAFETY scan of an MCP server \u2014 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 \u2014 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 \u2014 never assumed safe. Register of already-scanned servers: https://hlido.eu/mcp/",
                "inputSchema": {
                  "properties": {
                    "requester": {
                      "description": "Optional self-identifier \u2014 agent name or email \u2014 for follow-up when a queued scan completes.",
                      "type": "string"
                    },
                    "server": {
                      "description": "The MCP server to scan: an HTTP(S) MCP endpoint URL (e.g. 'https://mcp.example.com/mcp' \u2014 scanned live), OR an npm package (e.g. '@modelcontextprotocol/server-filesystem'), PyPI package, or GitHub repo URL (queued for sandbox scan).",
                      "type": "string"
                    }
                  },
                  "required": [
                    "server"
                  ],
                  "type": "object"
                },
                "name": "scan_mcp"
              }
            ]
          }
        },
        "bad_protocol_status_code": 200,
        "delete_error": null,
        "delete_status_code": null,
        "expired_session_error": null,
        "expired_session_status_code": null,
        "issues": [
          "missing_session_id",
          "missing_protocol_header",
          "bad_protocol_not_rejected"
        ],
        "last_event_id_visible": false,
        "protocol_header_present": false,
        "requested_protocol_version": "2024-11-05",
        "session_id_present": false,
        "transport": "streamable-http"
      },
      "latency_ms": 9.48,
      "status": "error"
    },
    "utility_coverage_probe": {
      "details": {
        "completions": {
          "advertised": false,
          "live_probe": "not_executed",
          "sample_target": null
        },
        "initialize_capability_keys": [
          "tools"
        ],
        "pagination": {
          "metadata_signal": false,
          "next_cursor_methods": [],
          "supported": false
        },
        "tasks": {
          "advertised": false,
          "http_status": 200,
          "probe_status": "missing"
        }
      },
      "latency_ms": 8.72,
      "status": "missing"
    }
  },
  "failures": {
    "oauth_authorization_server": {
      "reason": "no_authorization_server"
    },
    "oauth_protected_resource": {
      "error": "Client error '404 Not Found' for url 'https://hlido.eu/.well-known/oauth-protected-resource'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404",
      "url": "https://hlido.eu/.well-known/oauth-protected-resource"
    },
    "openid_configuration": {
      "reason": "no_authorization_server"
    },
    "prompts_list": {
      "headers": {
        "content-type": "application/json; charset=utf-8"
      },
      "http_status": 200,
      "payload": {
        "error": {
          "code": -32601,
          "message": "Method not found: prompts/list"
        },
        "id": 3,
        "jsonrpc": "2.0"
      },
      "url": "https://hlido.eu/mcp"
    },
    "resources_list": {
      "headers": {
        "content-type": "application/json; charset=utf-8"
      },
      "http_status": 200,
      "payload": {
        "error": {
          "code": -32601,
          "message": "Method not found: resources/list"
        },
        "id": 5,
        "jsonrpc": "2.0"
      },
      "url": "https://hlido.eu/mcp"
    },
    "transport_compliance_probe": {
      "bad_protocol_error": null,
      "bad_protocol_headers": {
        "content-type": "application/json; charset=utf-8"
      },
      "bad_protocol_payload": {
        "id": 410,
        "jsonrpc": "2.0",
        "result": {
          "tools": [
            {
              "description": "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 \u2014 before delegating to, installing, or relying on another agent \u2014 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.",
              "inputSchema": {
                "properties": {
                  "agent_or_url": {
                    "description": "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.",
                    "type": "string"
                  },
                  "use_case": {
                    "description": "Optional. The task you're considering this agent for (e.g. 'multi-file TypeScript refactor'); tailors the verdict to that use case when provided.",
                    "type": "string"
                  }
                },
                "required": [
                  "agent_or_url"
                ],
                "type": "object"
              },
              "name": "trust_check"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "limit": {
                    "default": 10,
                    "description": "Maximum number of agents to return (default 10).",
                    "type": "integer"
                  },
                  "min_tier": {
                    "default": "STEADY",
                    "description": "Minimum trust tier to include (VITAL is strictest, FLATLINE allows all). Defaults to STEADY.",
                    "enum": [
                      "VITAL",
                      "STEADY",
                      "FADING",
                      "FLATLINE"
                    ],
                    "type": "string"
                  },
                  "need": {
                    "description": "Free-text description of the capability you need (e.g. 'CLI coding agent that edits multiple files at once').",
                    "type": "string"
                  }
                },
                "required": [
                  "need"
                ],
                "type": "object"
              },
              "name": "find_trusted"
            },
            {
              "description": "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 \u2014 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.",
              "inputSchema": {
                "properties": {
                  "agent": {
                    "description": "The agent's Hlido slug or product URL (e.g. 'cursor').",
                    "type": "string"
                  },
                  "claim": {
                    "description": "The specific claim to verify, in plain language (e.g. 'works offline' or 'SOC 2 compliant').",
                    "type": "string"
                  }
                },
                "required": [
                  "agent",
                  "claim"
                ],
                "type": "object"
              },
              "name": "verify_claim"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "slugs": {
                    "description": "List of 2 to 5 Hlido agent slugs to compare side by side (e.g. ['aider','cursor','opencode']).",
                    "items": {
                      "description": "A Hlido agent slug (e.g. 'aider').",
                      "type": "string"
                    },
                    "maxItems": 5,
                    "minItems": 2,
                    "type": "array"
                  }
                },
                "required": [
                  "slugs"
                ],
                "type": "object"
              },
              "name": "compare_agents"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "email": {
                    "description": "Optional contact email for the submitter \u2014 if you want a reply or a heads-up when the review publishes. Providing it always flags the submission to the Hlido team.",
                    "type": "string"
                  },
                  "name": {
                    "description": "Human-readable agent name (e.g. 'Example Coder').",
                    "type": "string"
                  },
                  "note": {
                    "description": "Optional context: what the agent does, or why it's worth reviewing.",
                    "type": "string"
                  },
                  "url": {
                    "description": "The agent's product or homepage URL (e.g. 'https://example.com').",
                    "type": "string"
                  }
                },
                "required": [
                  "url",
                  "name"
                ],
                "type": "object"
              },
              "name": "submit_agent"
            },
            {
              "description": "Check any AI agent's EU AI Act Article-50 transparency posture \u2014 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.",
              "inputSchema": {
                "properties": {
                  "url": {
                    "description": "The agent's product or homepage URL (e.g. 'https://example.com'), or its Hlido slug.",
                    "type": "string"
                  }
                },
                "required": [
                  "url"
                ],
                "type": "object"
              },
              "name": "verify_transparency"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "slug": {
                    "description": "The agent's Hlido slug (e.g. 'aider', 'gumloop')",
                    "type": "string"
                  }
                },
                "required": [
                  "slug"
                ],
                "type": "object"
              },
              "name": "get_scorecard"
            },
            {
              "description": "Fetch published incidents from Hlido's NTSB-style failure registry \u2014 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.",
              "inputSchema": {
                "properties": {
                  "category": {
                    "description": "Optional category filter",
                    "enum": [
                      "hallucination",
                      "regression",
                      "safety",
                      "availability",
                      "cost",
                      "other"
                    ],
                    "type": "string"
                  },
                  "limit": {
                    "default": 20,
                    "description": "Max results (default 20, max 100)",
                    "type": "integer"
                  },
                  "severity": {
                    "description": "Optional minimum-interest filter (exact match)",
                    "enum": [
                      "low",
                      "medium",
                      "high",
                      "critical"
                    ],
                    "type": "string"
                  },
                  "slug": {
                    "description": "Optional: only incidents for this agent slug",
                    "type": "string"
                  }
                },
                "type": "object"
              },
              "name": "get_incidents"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "detail": {
                    "description": "What's wrong, with a concrete reference (URL, claim id, etc) if possible",
                    "type": "string"
                  },
                  "issue_type": {
                    "description": "Category of the report",
                    "enum": [
                      "stale",
                      "wrong_verdict",
                      "missing_claim",
                      "broken_link",
                      "other"
                    ],
                    "type": "string"
                  },
                  "reporter": {
                    "description": "Optional self-identifier \u2014 agent name or email \u2014 purely informational",
                    "type": "string"
                  },
                  "slug": {
                    "description": "The slug whose review has the issue",
                    "type": "string"
                  }
                },
                "required": [
                  "slug",
                  "issue_type",
                  "detail"
                ],
                "type": "object"
              },
              "name": "report_review_issue"
            },
            {
              "description": "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).",
              "inputSchema": {
                "properties": {
                  "name": {
                    "description": "Optional human-readable name (we'll derive from URL if missing)",
                    "type": "string"
                  },
                  "requester": {
                    "description": "Optional self-identifier \u2014 agent name, email, or session id \u2014 for rate-limiting + follow-up",
                    "type": "string"
                  },
                  "url": {
                    "description": "Homepage or product URL of the agent to audit",
                    "type": "string"
                  },
                  "why": {
                    "description": "Optional one-liner: why are you considering this agent? helps us prioritize",
                    "type": "string"
                  }
                },
                "required": [
                  "url"
                ],
                "type": "object"
              },
              "name": "request_quick_audit"
            },
            {
              "description": "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 \u2014 much better than substring matching via find_trusted.",
              "inputSchema": {
                "properties": {
                  "description": {
                    "description": "Free-text description of the task or capability you need",
                    "type": "string"
                  },
                  "min_score": {
                    "default": 0,
                    "description": "Minimum Laddoo score filter (default 0)",
                    "type": "integer"
                  },
                  "top_k": {
                    "default": 5,
                    "description": "Number of matches to return (default 5, max 20)",
                    "type": "integer"
                  }
                },
                "required": [
                  "description"
                ],
                "type": "object"
              },
              "name": "find_similar_agents"
            },
            {
              "description": "Preview \u2014 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.",
              "inputSchema": {
                "properties": {
                  "channel": {
                    "description": "Preferred notification channel. webhook is advisory only until Wave 3 ships.",
                    "enum": [
                      "rss",
                      "json",
                      "webhook"
                    ],
                    "type": "string"
                  },
                  "slug": {
                    "description": "The Hlido slug to subscribe to (e.g. 'cursor', 'aider')",
                    "type": "string"
                  }
                },
                "required": [
                  "slug"
                ],
                "type": "object"
              },
              "name": "subscribe"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "dimension": {
                    "description": "Optional dimension filter. Run without and check supported_dimensions in response if unsure.",
                    "type": "string"
                  },
                  "slug": {
                    "description": "The agent's Hlido slug",
                    "type": "string"
                  }
                },
                "required": [
                  "slug"
                ],
                "type": "object"
              },
              "name": "explain"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "constraints": {
                    "additionalProperties": false,
                    "properties": {
                      "category": {
                        "description": "Filter by category (e.g. 'Coding', 'Voice', 'Productivity')",
                        "type": "string"
                      },
                      "max_results": {
                        "default": 5,
                        "description": "Cap on results (default 5, max 25)",
                        "type": "integer"
                      },
                      "min_score": {
                        "default": 0,
                        "description": "Minimum Laddoo score (0-100)",
                        "type": "integer"
                      },
                      "tier": {
                        "description": "Minimum tier filter (VITAL strictest, FLATLINE allows all)",
                        "enum": [
                          "VITAL",
                          "STEADY",
                          "FADING",
                          "FLATLINE"
                        ],
                        "type": "string"
                      },
                      "use_case": {
                        "description": "Free-text capability description for ranking (e.g. 'multi-file refactor in TypeScript')",
                        "type": "string"
                      }
                    },
                    "type": "object"
                  }
                },
                "required": [
                  "constraints"
                ],
                "type": "object"
              },
              "name": "recommend"
            },
            {
              "description": "Fetch the behavioral evaluation trace for a Hlido-reviewed agent \u2014 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.",
              "inputSchema": {
                "properties": {
                  "slug": {
                    "description": "The Hlido slug to fetch behavioral trace for (e.g. 'aider', 'opencode')",
                    "type": "string"
                  },
                  "spec_version": {
                    "default": "v0.1",
                    "description": "Behavioral spec version (default 'v0.1'). Omit to get the latest available.",
                    "type": "string"
                  }
                },
                "required": [
                  "slug"
                ],
                "type": "object"
              },
              "name": "get_behavioral_trace"
            },
            {
              "description": "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.",
              "inputSchema": {
                "properties": {
                  "agent_or_url": {
                    "description": "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.",
                    "type": "string"
                  }
                },
                "required": [
                  "agent_or_url"
                ],
                "type": "object"
              },
              "name": "commerce_check"
            },
            {
              "description": "On-demand independent SAFETY scan of an MCP server \u2014 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 \u2014 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 \u2014 never assumed safe. Register of already-scanned servers: https://hlido.eu/mcp/",
              "inputSchema": {
                "properties": {
                  "requester": {
                    "description": "Optional self-identifier \u2014 agent name or email \u2014 for follow-up when a queued scan completes.",
                    "type": "string"
                  },
                  "server": {
                    "description": "The MCP server to scan: an HTTP(S) MCP endpoint URL (e.g. 'https://mcp.example.com/mcp' \u2014 scanned live), OR an npm package (e.g. '@modelcontextprotocol/server-filesystem'), PyPI package, or GitHub repo URL (queued for sandbox scan).",
                    "type": "string"
                  }
                },
                "required": [
                  "server"
                ],
                "type": "object"
              },
              "name": "scan_mcp"
            }
          ]
        }
      },
      "bad_protocol_status_code": 200,
      "delete_error": null,
      "delete_status_code": null,
      "expired_session_error": null,
      "expired_session_status_code": null,
      "issues": [
        "missing_session_id",
        "missing_protocol_header",
        "bad_protocol_not_rejected"
      ],
      "last_event_id_visible": false,
      "protocol_header_present": false,
      "requested_protocol_version": "2024-11-05",
      "session_id_present": false,
      "transport": "streamable-http"
    }
  },
  "remote_url": "https://hlido.eu/mcp",
  "server_card_payload": null,
  "server_identifier": "ankitkapur1992-hlido/hlido-mcp"
}

Known versions

Validation history

7 day score delta
n/a
30 day score delta
n/a
Recent healthy ratio
100%
Freshness
3.7h
TimestampStatusScoreLatencyTools
Jul 31, 2026 10:26:23 AM UTC Healthy 68.5 448.4 ms 17

Validation timeline

ValidatedSummaryScoreProtocolAuth modeToolsHigh-risk toolsChanges
Jul 31, 2026 10:26:23 AM UTC Healthy 68.5 2024-11-05 public 17 3 none

Recent validation runs

StartedStatusSummaryLatencyChecks
Jul 31, 2026 10:26:23 AM UTC Completed Healthy 448.4 ms action_safety_probe, advanced_capabilities_probe, connector_publishability_probe, connector_replay_probe, determinism_probe, initialize, interactive_flow_probe, oauth_authorization_server, oauth_protected_resource, official_registry_probe, openid_configuration, probe_noise_resilience, prompt_get, prompts_list, protocol_version_probe, provenance_divergence_probe, request_association_probe, resource_read, resources_list, server_card, session_resume_probe, step_up_auth_probe, tool_snapshot_probe, tools_list, transport_compliance_probe, utility_coverage_probe