# Liongard (io.github.wyre-technology/liongard-mcp@2.3.7)

> Source: <https://mcpindex.ai/server/io-github-wyre-technology-liongard-mcp>
> Published: 2026-08-20 22:30:08+00:00

[← Index](/leaderboard)

# Liongard

MCP server for Liongard — inspectors, environments, metrics, detections, and timeline data.

The current version, v2.3.7, was published to the official MCP registry on 2026-08-20. It is distributed as the Docker image ghcr.io/wyre-technology/liongard-mcp:v2.3.7, filed under Other 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](/stats) put this record in context.

## Using Liongard 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).

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
```

[method](/methodology)

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

`mcpindex.integrity.description`

passINFOevidence“No malicious instructions found”via static_description

- - 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 →](/screen)

## That verdict was true at screening time (snapshot 2026-08-20).

Contracts can change after screening, with no version bump. The gate pins Liongard’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 →](/guides/install-the-gate-first-hold)

Related: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift)

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.

```
[Independent trust record for Liongard](https://mcpindex.ai/server/io-github-wyre-technology-liongard-mcp) - screening verdict, registry provenance, and contract drift monitoring.
<a href="https://mcpindex.ai/server/io-github-wyre-technology-liongard-mcp">Independent trust record for Liongard</a> - screening verdict, registry provenance, and contract drift monitoring.
```

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

```
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-wyre-technology-liongard-mcp)](https://mcpindex.ai/server/io-github-wyre-technology-liongard-mcp)
<a href="https://mcpindex.ai/server/io-github-wyre-technology-liongard-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-wyre-technology-liongard-mcp" alt="mcpindex verdict" height="20" /></a>
```

`LIONGARD_API_KEY`

Liongard API access key (access key ID and secret combined per Liongard auth scheme)

`LIONGARD_INSTANCE`

Liongard instance hostname (e.g. yourorg.app.liongard.com)

`MCP_TRANSPORT`

Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.

`AUTH_MODE`

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.

`LOG_LEVEL`

Log verbosity: debug, info, warn, error

[methodology](/methodology)

[ConnectMachineai.connectmachine/connectmachine](/server/ai-connectmachine-connectmachine)

Manage your ConnectMachine contacts, networks, events, and digital business cards.

[DABLOCK AI Visibility Indexai.dablock/visibility-index](/server/ai-dablock-visibility-index)

Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.

[Mailprotectorio.github.wyre-technology/mailprotector-mcp](/server/io-github-wyre-technology-mailprotector-mcp)

MCP server for Mailprotector — customers, domains, users, quarantine, allow/block rules for MSPs.
