# Tested Templates Ops Guardrails MCP server

> List local ops-guardrails checks, view sample findings and get the install file for a local pre-flight checker for server and secret safety.

- Listing: https://mcp.tc/i/tested-templates-ops-guardrails
- Connect: use the server's own URL `https://testedtemplates.com/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Security & Compliance](https://mcp.tc/c/security)
- Vendor: Tested Templates
- Homepage: <https://testedtemplates.com/>

## About

This hosted endpoint is a directory for the Ops Guardrails local checker. It lists the checks (audit\_server\_snippet, scan\_secret\_leak, rewrite\_safe\_curl), shows sample finding ids from built-in public fixtures, and returns the local install file with its sha256 and client config.

The endpoint does not audit anything you send. Do not send sudoers files, unit files, commands or secrets. The checks run in the single-file local server on your own machine. No sign-in or API key is needed for the endpoint.

## What it can do

- List the local ops-guardrails checks
- Show sample finding ids from public fixtures
- Get the local install file and its sha256
- Get client config for Claude Desktop, Claude Code, Cursor, Gemini or Codex
- Find kit and install page links

## Tools (4)

- `list_checks`: List the local checks; it cannot run them on text you send. (read-only)
- `sample_findings`: Show finding ids from built-in public fixtures. (read-only)
- `install_local`: Return the local install file, its sha256 and client config for a chosen client. (read-only)
- `products`: Return the kit URLs, the install page and the registry remote. (read-only)

## Example prompts

- "List the local ops-guardrails checks."
- "Show sample findings from the guardrails checker."
- "Give me the local install and Claude Code config for ops guardrails."
- "Where can I get the Tested Templates kits?"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http tested-templates-ops-guardrails https://testedtemplates.com/mcp
```

2. Start Claude Code and type `/mcp`. **tested-templates-ops-guardrails** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Tested Templates Ops Guardrails** and paste this URL:

```url
https://testedtemplates.com/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Tested%20Templates%20Ops%20Guardrails&connectorUrl=https%3A%2F%2Ftestedtemplates.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://testedtemplates.com/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://testedtemplates.com/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=tested-templates-ops-guardrails&config=eyJ1cmwiOiJodHRwczovL3Rlc3RlZHRlbXBsYXRlcy5jb20vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "tested-templates-ops-guardrails": {
      "url": "https://testedtemplates.com/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=tested-templates-ops-guardrails&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Ftestedtemplates.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"tested-templates-ops-guardrails","type":"http","url":"https://testedtemplates.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "tested-templates-ops-guardrails": {
      "type": "http",
      "url": "https://testedtemplates.com/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "tested-templates-ops-guardrails": {
      "serverUrl": "https://testedtemplates.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add tested-templates-ops-guardrails --url https://testedtemplates.com/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.tested-templates-ops-guardrails]
url = "https://testedtemplates.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http tested-templates-ops-guardrails https://testedtemplates.com/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "tested-templates-ops-guardrails": {
      "type": "http",
      "url": "https://testedtemplates.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://testedtemplates.com/mcp`.

## Recent changes

- 2026-10-27 11:38 UTC: Tracking started: 4 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/tested-templates-ops-guardrails#history (Atom feed: https://mcp.tc/i/tested-templates-ops-guardrails/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 1.1.0
- MCP protocol version: 2025-11-25
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-27
- Updated: 2026-10-27

---
Source: https://mcp.tc/i/tested-templates-ops-guardrails (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
