# hybridlog (remote · {hybridlog_host})

Reads your own Garmin mirror: readiness, training load, muscle freshness, and read-only SQL.

- Trust score: 0/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- remote · `{hybridlog_host}`: 0/100 (this document), [markdown](https://verifymcp.io/servers/imgrund-hybridlog/https-hybridlog-host-mcp-garmin.md), [page](https://verifymcp.io/servers/imgrund-hybridlog/https-hybridlog-host-mcp-garmin)
- oci · `ghcr.io/imgrund/hybridlog:0.1.12`: 10/100, [markdown](https://verifymcp.io/servers/imgrund-hybridlog/ghcr-io-imgrund-hybridlog-0-1-12.md), [page](https://verifymcp.io/servers/imgrund-hybridlog/ghcr-io-imgrund-hybridlog-0-1-12)

## Channel facts

- Endpoint: `https://{hybridlog_host}/mcp/garmin`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.12`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Endpoint Security**: 0/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: this endpoint is not published over https, so there is no plaintext variant to compare against.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC not yet verified: we couldn't validate it against a resolver.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: not scored yet
  - Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the hybridlog MCP server?

hybridlog is a hosted endpoint at https://{hybridlog_host}/mcp/garmin, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http imgrund-hybridlog 'https://{hybridlog_host}/mcp/garmin'
```

### Cursor

```json
{
  "mcpServers": {
    "imgrund-hybridlog": {
      "url": "https://{hybridlog_host}/mcp/garmin"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "imgrund-hybridlog": {
      "type": "http",
      "url": "https://{hybridlog_host}/mcp/garmin"
    }
  }
}
```

### Codex

```toml
[mcp_servers.imgrund-hybridlog]
url = "https://{hybridlog_host}/mcp/garmin"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "imgrund-hybridlog": {
      "type": "remote",
      "url": "https://{hybridlog_host}/mcp/garmin",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add imgrund-hybridlog --url 'https://{hybridlog_host}/mcp/garmin' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  imgrund-hybridlog:
    url: "https://{hybridlog_host}/mcp/garmin"
```

### Netclaw

```json
{
  "McpServers": {
    "imgrund-hybridlog": {
      "Transport": "http",
      "Url": "https://{hybridlog_host}/mcp/garmin"
    }
  }
}
```

### Vellum

```bash
assistant mcp add imgrund-hybridlog -t streamable-http -u 'https://{hybridlog_host}/mcp/garmin'
```

### Other

```json
{
  "mcpServers": {
    "imgrund-hybridlog": {
      "type": "http",
      "url": "https://{hybridlog_host}/mcp/garmin"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-16 (score 0)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/imgrund-hybridlog/https-hybridlog-host-mcp-garmin#diagnostics

## Score history

- 2026-08-22: 0
- 2026-08-21: 0
- 2026-08-20: 0
- 2026-08-19: 0
- 2026-08-18: 0
- 2026-08-17: 0
- 2026-08-16: 0

## Common questions

### What is the hybridlog MCP server?

hybridlog is an MCP server listed in the public MCP registry as io.github.Imgrund/hybridlog. Reads your own Garmin mirror: readiness, training load, muscle freshness, and read-only SQL. This page covers its hosted endpoint (https://{hybridlog_host}/mcp/garmin).

### Is the hybridlog MCP server safe to use?

hybridlog scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Does the hybridlog MCP server require authentication?

Its publisher declares no required credentials for hybridlog. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the hybridlog MCP server still maintained?

hybridlog has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://{hybridlog_host}/mcp/garmin
- Repository: https://github.com/Imgrund/hybridlog
- Changelog RSS feed: https://verifymcp.io/servers/imgrund-hybridlog/https-hybridlog-host-mcp-garmin.xml
- Changelog JSON feed: https://verifymcp.io/servers/imgrund-hybridlog/https-hybridlog-host-mcp-garmin.json
- HTML version of this page: https://verifymcp.io/servers/imgrund-hybridlog/https-hybridlog-host-mcp-garmin