# UsageMax public observability (remote · usagemax.com)

Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `usagemax.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/symbaiex-usagemax/usagemax.md), [page](https://verifymcp.io/servers/symbaiex-usagemax/usagemax)

## Channel facts

- Endpoint: `https://usagemax.com/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-10-02.

- **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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 212 tokens (~42/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 73/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the UsageMax public observability MCP server?

UsageMax public observability is a hosted endpoint at https://usagemax.com/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 symbaiex-usagemax 'https://usagemax.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "symbaiex-usagemax": {
      "url": "https://usagemax.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "symbaiex-usagemax": {
      "type": "http",
      "url": "https://usagemax.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.symbaiex-usagemax]
url = "https://usagemax.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add symbaiex-usagemax --url 'https://usagemax.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  symbaiex-usagemax:
    url: "https://usagemax.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "symbaiex-usagemax": {
      "Transport": "http",
      "Url": "https://usagemax.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add symbaiex-usagemax -t streamable-http -u 'https://usagemax.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "symbaiex-usagemax": {
      "type": "http",
      "url": "https://usagemax.com/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-10-02 (score 81, +1)

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

### 2026-09-30 (score 80, +1)

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

### 2026-09-28 (score 79, +1)

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

### 2026-09-26 (score 78, +1)

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

### 2026-09-25 (score 77, 0)

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

### 2026-09-24 (score 77, +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-09-21 (score 76, +1)

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

### 2026-09-20 (score 75, +3)

- [security] The server changed its declared name: UsageMax public product MCP → UsageMax public observability
- [functional regression] Schema quality: 38 → 42
- [functional improvement] Tool coverage: 0% → 75%
- [functional improvement] Tool “ask_site” now declares an output schema
- [functional improvement] Tool “leaderboard” now declares an output schema
- [functional improvement] Tool “network_stats” now declares an output schema
- [functional improvement] Tool “public_profile” now declares an output schema
- [functional] First check of Tool coverage: 100
- [cosmetic] “leaderboard” reworded the description of “metric”
- [cosmetic] “leaderboard” reworded the description of “period”
- [cosmetic] “public_profile” reworded the description of “handle”

## MCP tools (4)

### `public_profile` (~36 tokens)

Read public profile

Read one opt-in public UsageMax profile and aggregate statistics.

Input parameters:

- `handle` (string, required): The public profile handle, without the @ prefix.

### `leaderboard` (~45 tokens)

Read public leaderboard

Read the public UsageMax leaderboard (maximum 100 rows).

Input parameters:

- `metric` (string): Rank by aggregate tokens or tracked spend.
- `period` (string): Choose the bounded reporting window.

### `network_stats` (~24 tokens)

Read network statistics

Read aggregate public UsageMax network statistics and render the optional inline observability view.

### `ask_site` (~30 tokens)

Ask UsageMax documentation

Ask a bounded natural-language question about UsageMax and receive cited public resources.

Input parameters:

- `query` (string, required)

## Diagnostics

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

## Score history

- 2026-10-02: 81
- 2026-10-01: 80
- 2026-09-30: 80
- 2026-09-29: 79
- 2026-09-28: 79
- 2026-09-27: 78
- 2026-09-26: 78
- 2026-09-25: 77
- 2026-09-24: 77
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 72
- 2026-09-18: 72
- 2026-09-17: 71
- 2026-09-16: 71

## Common questions

### What is the UsageMax public observability MCP server?

UsageMax public observability is an MCP server listed in the public MCP registry as io.github.SYMBaiEX/usagemax. Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data. This page covers its hosted endpoint (https://usagemax.com/mcp).

### Is the UsageMax public observability MCP server safe to use?

UsageMax public observability scores 81 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 UsageMax public observability MCP server expose?

UsageMax public observability exposes 4 tools: public_profile, leaderboard, network_stats, ask_site. Their descriptions and schemas cost roughly 135 tokens of context every time the server is loaded.

### Does the UsageMax public observability MCP server require authentication?

No. We connected to UsageMax public observability without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UsageMax public observability MCP server still maintained?

UsageMax public observability is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://usagemax.com/mcp
- Repository: https://github.com/SYMBaiEX/usagemax
- Website: https://usagemax.com/
- Changelog RSS feed: https://verifymcp.io/servers/symbaiex-usagemax/usagemax.xml
- Changelog JSON feed: https://verifymcp.io/servers/symbaiex-usagemax/usagemax.json
- HTML version of this page: https://verifymcp.io/servers/symbaiex-usagemax/usagemax