Trust Directory / report
Avaza UNKNOWN
No anonymous handshake observed — endpoints behind authentication are expected to show this result; it does not mean the server is broken.
Manage Avaza projects, tasks, timesheets, expenses, invoices, and scheduling from AI assistants.
| Registry name | com.avaza/avaza-mcp (v1.1.0) |
|---|---|
| Endpoint | https://mcp.avaza.com/mcp |
| Reported server | — |
| Protocol version | not negotiated |
| Tools exposed | unknown |
| Checked at | 2026-10-11T03:28:59.609Z |
Findings
- UNKNOWN
NO_RESPONSE— Endpoint did not complete MCP initialize + tools/list within timeout
Reproduce this report
npx @eidonze/mcpdoctor schema https://mcp.avaza.com/mcp
Embed status: <img src="https://xka0085-byte.github.io/mcp-doctor/trust/badge/com.avaza-avaza-mcp.svg"> · Machine-readable: /api/com.avaza-avaza-mcp.json
Generated by mcpdoctor — read-only MCP initialize + tools/list. No tools were called, no payments attempted. Static schema checks do not predict model tool selection or prove behavior across all clients. Scanned: 2026-10-11.