Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Auralogs

REMOTE · MCP.AURALOGS.AI · SCANNED AUG 3

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

Available components

+8 this week 63 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security71
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 337 tokens (~48/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.auralogs.ai

# add to Claude Code
claude mcp add --transport http ai-auralogs-auralogs https://mcp.auralogs.ai/mcp
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-auralogs-auralogs --url https://mcp.auralogs.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-auralogs-auralogs:
    url: "https://mcp.auralogs.ai/mcp"
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +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.

  • 1 Aug 26 +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.

  • 31 Jul 26 +4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +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.

  • 28 Jul 26 +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.

  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 55

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.auralogs.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=auralogs.ai CN=WE1,O=Google Trust Services,C=US 13 Jul 2026 11 Oct 2026 ECDSA 256 ECDSA-SHA256 a7b032d94fb3a6e00e41760cea112738
SANs: auralogs.ai, mcp.auralogs.ai, *.mcp.auralogs.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of mcp.auralogs.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
auralogs.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="auralogs"

Bearer realm="auralogs"

Protected resource metadata

Retrieved No
Problem no_resource_metadata
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.auralogs.ai/mcp Verified 200
http (plaintext) http://mcp.auralogs.ai/mcp Inconclusive 401
MCP tools — 7 exposed · ~337 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
get_analysis ~34

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

NameTypeReqDescription
analysis_idstringyes

No output schema declared.

No examples provided.

get_log ~32

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

NameTypeReqDescription
log_idstringyes

No output schema declared.

No examples provided.

get_project ~31

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

NameTypeReqDescription
project_idstringyes

No output schema declared.

No examples provided.

list_analyses ~103

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

NameTypeReqDescription
cursorstring
include_archived
limitinteger
project_idstringyes
severitystring
typestring

No output schema declared.

No examples provided.

list_logs ~67

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

NameTypeReqDescription
cursorstring
levelstring
limitinteger
project_idstringyes
sincestring
untilstring

No output schema declared.

No examples provided.

list_projects ~23

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_logs ~47

Full-text search log messages for the scoped project.

NameTypeReqDescription
cursorstring
limitinteger
project_idstringyes
qstringyes

No output schema declared.

No examples provided.