Causal check on AI agent claims, from ad-spend/ROAS lift to any decision: pass, caution or hold.
- Remote endpoint
Uptime
Checked · every day
100%from 11 days of checks
Up without downtime on 10 of 10 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 599 ms, slowest 5% 1236 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
2 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 10 Nov (today) | No verdict yet | 0 | – |
| 9 Nov | No downtime | 1of 1 | 608 ms |
| 8 Nov | No downtime | 1of 1 | 627 ms |
| 7 Nov | No downtime | 1of 1 | 560 ms |
| 6 Nov | No downtime | 1of 1 | 820 ms |
| 5 Nov | No downtime | 1of 1 | 794 ms |
| 4 Nov | No downtime | 1of 1 | 841 ms |
| 3 Nov | No downtime | 1of 1 | 539 ms |
| 2 Nov | No downtime | 1of 1 | 622 ms |
| 1 Nov | No downtime | 1of 1 | 569 ms |
| 31 Oct | No downtime | 1 | 951 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://guardian.sylai.io/mcp This server needs a header that the connector form cannot set; use Claude Code, Cursor or VS Code for it.
Run in a terminal:
claude mcp add --transport http guardian https://guardian.sylai.io/mcp --header 'X-API-Key: YOUR_X_API_KEY' Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"guardian": {
"type": "http",
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
{
"mcpServers": {
"guardian": {
"type": "streamableHttp",
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "guardian"
type: streamable-http
url: "https://guardian.sylai.io/mcp" This server needs a header, and Continue's documentation shows no way to send one to a remote server; use another client for it.
Add to ~/.config/goose/config.yaml:
extensions:
"guardian":
type: streamable_http
name: "guardian"
enabled: true
uri: "https://guardian.sylai.io/mcp"
headers: { "X-API-Key": "YOUR_X_API_KEY" }
env_keys: []
envs: {}
timeout: 300 Add to ~/.gemini/settings.json:
{
"mcpServers": {
"guardian": {
"httpUrl": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to ~/.codex/config.toml:
[mcp_servers.guardian]
url = "https://guardian.sylai.io/mcp"
http_headers = { "X-API-Key" = "YOUR_X_API_KEY" } Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
{
"mcpServers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
{
"mcpServers": {
"guardian": {
"type": "streamable",
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"guardian": {
"type": "http",
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
} This server needs a header, and Augment Code's documentation shows no way to send one to a remote server; use another client for it.
Replace YOUR_X_API_KEY with your own value.
For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Syl Guardian (`io.sylai/guardian`)
Its page: https://plug.directory/servers/io.sylai/guardian
It runs on the publisher's servers; the client connects to its URL.
Ask the person for `YOUR_X_API_KEY` and put it in place of the placeholder; never invent a value.
Use the section for the person's client.
## Claude Desktop
This server needs a header that the connector form cannot set; use Claude Code, Cursor or VS Code for it.
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport http guardian https://guardian.sylai.io/mcp --header 'X-API-Key: YOUR_X_API_KEY'
```
## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
```json
{
"mcpServers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"guardian": {
"type": "http",
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## Zed
Merge into ~/.config/zed/settings.json:
```json
{
"context_servers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## Cline
Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
```json
{
"mcpServers": {
"guardian": {
"type": "streamableHttp",
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## Continue
This server needs a header, and Continue's documentation shows no way to send one to a remote server; use another client for it.
## Goose
Merge into ~/.config/goose/config.yaml:
```yaml
extensions:
"guardian":
type: streamable_http
name: "guardian"
enabled: true
uri: "https://guardian.sylai.io/mcp"
headers: { "X-API-Key": "YOUR_X_API_KEY" }
env_keys: []
envs: {}
timeout: 300
```
## Gemini CLI
Merge into ~/.gemini/settings.json:
```json
{
"mcpServers": {
"guardian": {
"httpUrl": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## Codex
Add to ~/.codex/config.toml:
```toml
[mcp_servers.guardian]
url = "https://guardian.sylai.io/mcp"
http_headers = { "X-API-Key" = "YOUR_X_API_KEY" }
```
## mcp-client-cli, TUUI, BoltAI
This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
Merge into ~/.config/agenvoy/mcp.json:
```json
{
"servers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"guardian": {
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## AnythingLLM
Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
```json
{
"mcpServers": {
"guardian": {
"type": "streamable",
"url": "https://guardian.sylai.io/mcp",
"headers": { "X-API-Key": "YOUR_X_API_KEY" }
}
}
}
```
## Augment Code
This server needs a header, and Augment Code's documentation shows no way to send one to a remote server; use another client for it.
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem