← Index

Liongard MCP

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

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

The current version, v0.1.2, was published to the official MCP registry on 2026-08-27. It is distributed through a declared package, filed under Search by this index, and declares 5 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

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
Auditable install path →Watch it hold a drift →
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-09-12 23:55 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

evidence“No malicious instructions found”via 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
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

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

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

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Liongard MCP](https://mcpindex.ai/server/io-github-servosity-liongard-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-liongard-mcp">Independent trust record for Liongard MCP</a> - screening verdict, registry provenance, and contract drift monitoring.
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_ACCESS_KEY_ID
secret

Liongard Access Key ID, the half that pairs with LIONGARD_ACCESS_KEY_SECRET; the server composes the two into the base64 X-ROAR-API-KEY. One of two ways to authenticate - set EITHER this pair OR the pre-encoded LIONGARD_API_KEY, never both. LIONGARD_API_KEY wins when it is set, so leave it blank to use this pair.

LIONGARD_ACCESS_KEY_SECRET
secret

Liongard Access Key Secret, the other half of LIONGARD_ACCESS_KEY_ID. One of two ways to authenticate - set EITHER this pair OR the pre-encoded LIONGARD_API_KEY, never both. LIONGARD_API_KEY wins when it is set, so leave it blank to use this pair.

LIONGARD_API_KEY
secret

Pre-encoded X-ROAR-API-KEY: base64 of 'accessKeyId:accessKeySecret'. One of two ways to authenticate - set EITHER this key OR the LIONGARD_ACCESS_KEY_ID + LIONGARD_ACCESS_KEY_SECRET pair, never both. This key wins when it is set, and the pair is ignored.

LIONGARD_BASE_URL

Full API base URL. Leave blank: the CLI builds it from LIONGARD_INSTANCE. Set it only to point at a different host.

LIONGARD_INSTANCE
required

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

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Search
YTDL RMCP
ai.dinglebear/rytdl

yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI.

Fodda Topic & Trend Research
ai.fodda/topic-research

Trend, stats & insight search across PSFK expert graphs with citable sources.

N-able N-central MCP
io.github.Servosity/n-central-mcp

N-central REST API with an offline org-tree mirror, cross-tenant search, and a JWT-expiry guardian.