# Where Them Logs (remote · wherethemlogs.app)

Where apps write their log files on Windows, macOS and Linux, as exact copyable paths.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `wherethemlogs.app`: 85/100 (this document), [markdown](https://verifymcp.io/servers/app-wherethemlogs-log-locations/api-mcp.md), [page](https://verifymcp.io/servers/app-wherethemlogs-log-locations/api-mcp)

## Channel facts

- Endpoint: `https://wherethemlogs.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-11-06.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 170 tokens (~85/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Where Them Logs MCP server?

Where Them Logs is a hosted endpoint at https://wherethemlogs.app/api/mcp, 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 app-wherethemlogs-log-locations 'https://wherethemlogs.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-wherethemlogs-log-locations": {
      "url": "https://wherethemlogs.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-wherethemlogs-log-locations": {
      "type": "http",
      "url": "https://wherethemlogs.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-wherethemlogs-log-locations]
url = "https://wherethemlogs.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-wherethemlogs-log-locations": {
      "type": "remote",
      "url": "https://wherethemlogs.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-wherethemlogs-log-locations --url 'https://wherethemlogs.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-wherethemlogs-log-locations:
    url: "https://wherethemlogs.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-wherethemlogs-log-locations": {
      "Transport": "http",
      "Url": "https://wherethemlogs.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-wherethemlogs-log-locations -t streamable-http -u 'https://wherethemlogs.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-wherethemlogs-log-locations": {
      "type": "http",
      "url": "https://wherethemlogs.app/api/mcp"
    }
  }
}
```

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-11-06 (score 85, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 85, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `search_log_locations` (~96 tokens)

Search log locations

Find where an application writes its log files. Matches app names and aliases (for example 'teams', 'zoom', 'docker') and the names of files listed under a path (for example 'AppWorkload.log'), not vendor names. Returns each app's log paths by platform.

Input parameters:

- `limit` (integer)
- `platform` (string): Only paths on this platform
- `query` (string, required): App name or alias

### `get_app_log_locations` (~33 tokens)

Get one app's log locations

Every log location for one app, by the slug that search_log_locations returns.

Input parameters:

- `slug` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-wherethemlogs-log-locations/api-mcp#diagnostics

## Score history

- 2026-11-06: 85
- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 74
- 2026-10-12: 74
- 2026-10-11: 73
- 2026-10-10: 73
- 2026-10-07: 71
- 2026-10-06: 71

## Common questions

### What is the Where Them Logs MCP server?

Where Them Logs is an MCP server listed in the public MCP registry as app.wherethemlogs/log-locations. Where apps write their log files on Windows, macOS and Linux, as exact copyable paths. This page covers its hosted endpoint (https://wherethemlogs.app/api/mcp).

### Is the Where Them Logs MCP server safe to use?

Where Them Logs scores 85 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.

### What tools does the Where Them Logs MCP server expose?

Where Them Logs exposes 2 tools: search_log_locations, get_app_log_locations. Their descriptions and schemas cost roughly 129 tokens of context every time the server is loaded.

### Does the Where Them Logs MCP server require authentication?

No. We connected to Where Them Logs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Where Them Logs MCP server still maintained?

Where Them Logs is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Where Them Logs MCP server?

VerifyMCP ran 13 checks on Where Them Logs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://wherethemlogs.app/api/mcp
- Repository: https://github.com/scotscottmca/wherethemlogs.app
- Website: https://wherethemlogs.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-wherethemlogs-log-locations/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-wherethemlogs-log-locations/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-wherethemlogs-log-locations/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-wherethemlogs-log-locations/api-mcp