# Auralogs (remote · mcp.auralogs.ai)

Read-only access to Auralogs production logs: search logs, inspect errors, review AI analyses.

- Trust score: 63/100 (medium)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.auralogs.ai`: 63/100 (this document), [markdown](https://verifymcp.io/servers/ai-auralogs-auralogs/mcp.md), [page](https://verifymcp.io/servers/ai-auralogs-auralogs/mcp)

## Channel facts

- Endpoint: `https://mcp.auralogs.ai/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.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-08-03.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 57/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 337 tokens (~48/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-auralogs-auralogs https://mcp.auralogs.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-auralogs-auralogs]
url = "https://mcp.auralogs.ai/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-auralogs-auralogs --url https://mcp.auralogs.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-auralogs-auralogs:
    url: "https://mcp.auralogs.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-auralogs-auralogs": {
      "type": "http",
      "url": "https://mcp.auralogs.ai/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-08-03 (score 63, +1)

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

### 2026-08-01 (score 62, +1)

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

### 2026-07-31 (score 61, +4)

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

### 2026-07-30 (score 57, 0)

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

### 2026-07-29 (score 57, +1)

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

### 2026-07-28 (score 56, +1)

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

### 2026-07-27 (score 55, 0)

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

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (7)

### `list_projects` (~23 tokens)

List projects accessible to the current read key (one project for v1).

### `get_project` (~31 tokens)

Get a project by id. Must match the read key's scoped project.

Input parameters:

- `project_id` (string, required)

### `list_logs` (~67 tokens)

List logs for the scoped project, optionally filtered by level/since/until.

Input parameters:

- `cursor` (string)
- `level` (string)
- `limit` (integer)
- `project_id` (string, required)
- `since` (string)
- `until` (string)

### `search_logs` (~47 tokens)

Full-text search log messages for the scoped project.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `project_id` (string, required)
- `q` (string, required)

### `get_log` (~32 tokens)

Get a single log row by id, with full context (stack, metadata).

Input parameters:

- `log_id` (string, required)

### `list_analyses` (~103 tokens)

List active analyses for the scoped project. Archived analyses (triaged from the dashboard) are excluded by default; pass include_archived=true to see them. Optional filters: severity (low/medium/high/critical), type (reactive/scheduled).

Input parameters:

- `cursor` (string)
- `include_archived`
- `limit` (integer)
- `project_id` (string, required)
- `severity` (string)
- `type` (string)

### `get_analysis` (~34 tokens)

Get a single analysis by id (diagnosis, suggested fix, PR link if any).

Input parameters:

- `analysis_id` (string, required)

## Diagnostics

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

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 57
- 2026-07-29: 57
- 2026-07-28: 56
- 2026-07-27: 55
- 2026-07-26: 55

## Links

- Remote endpoint: https://mcp.auralogs.ai/mcp
- Authorisation metadata: https://mcp.auralogs.ai/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/auralogs-ai/auralogs-mcp
- Website: https://docs.auralogs.ai/read-api/overview/
- Changelog RSS feed: https://verifymcp.io/servers/ai-auralogs-auralogs/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-auralogs-auralogs/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-auralogs-auralogs/mcp