Auralogs

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v0.1.0

1. Real tool

   passrules 2026-09-29.1 · 5 hours ago

2. Static scan

   passrules 2026-09-29.1 · 5 hours ago

3. Claims check

   skippedrules 2026-09-29.1 · 5 hours ago
   • infoLLM claims check is not configured on this deploy.

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "auralogs": {
      "type": "http",
      "url": "https://mcp.auralogs.ai/mcp"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• list_projects

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

• get_project

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

• list_logs

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

• search_logs

  Full-text search log messages for the scoped project.

• get_log

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

• list_analyses

  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).

• get_analysis

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