← Index

Liongard MCP

io.github.Servosity/liongard-mcpv0.1.0Search

Liongard config visibility: sync your estate offline, then drift-check and search it from one CLI.

In-path gate · all MCP tools

Using Liongard MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-08-20 09:02 UTC
screened 2026-07-21tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidenceNo malicious instructions foundvia static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-07-22).

Contracts can change after screening, with no version bump. The gate pins Liongard MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-servosity-liongard-mcp)](https://mcpindex.ai/server/io-github-servosity-liongard-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-liongard-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-liongard-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
LIONGARD_INSTANCE
required

Your Liongard subdomain (the 'acme' in acme.app.liongard.com); builds the API URL.

LIONGARD_API_KEY
requiredsecret

Base64 X-ROAR-API-KEY for the Liongard API (or use LIONGARD_ACCESS_KEY_ID + LIONGARD_ACCESS_KEY_SECRET).

LIONGARD_ENDPOINTS_API_KEY
secret

Optional. Only needed for the Liongard Endpoints API surface.

MCP quality score · maturity, not trust · methodology
freshness
24
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Search