# ro.avizo/avizo-mcp (remote · avizo.ro)

Avizo (RO SME compliance-deadline SaaS) as MCP tools: about, plans, categories, docs. Read-only.

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

## Components

- remote · `avizo.ro`: 76/100 (this document), [markdown](https://verifymcp.io/servers/ro-avizo-avizo-mcp/avizo.md), [page](https://verifymcp.io/servers/ro-avizo-avizo-mcp/avizo)

## Channel facts

- Endpoint: `https://avizo.ro/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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**: 77/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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **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 906 tokens (~50/item across 18 items; 5 tools + 13 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### Claude

```bash
claude mcp add --transport http ro-avizo-avizo-mcp https://avizo.ro/mcp
```

### Codex

```toml
[mcp_servers.ro-avizo-avizo-mcp]
url = "https://avizo.ro/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ro-avizo-avizo-mcp --url https://avizo.ro/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ro-avizo-avizo-mcp:
    url: "https://avizo.ro/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ro-avizo-avizo-mcp": {
      "type": "http",
      "url": "https://avizo.ro/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-02 (score 76, +1)

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

### 2026-07-31 (score 75, +3)

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

### 2026-07-30 (score 72, 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 72, +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 71, +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 70, +1)

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

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

First indexed and scored.

## MCP tools (5)

### `avizo_about` (~73 tokens)

What Avizo is and how it works

Product overview of Avizo (avizo.ro): compliance-deadline tracking and alerting for Romanian SMEs — what it tracks, alert channels and cadence, post-expiry escalation, integrations, billing model, GDPR posture. Factual summary; use avizo_plans for pricing details and avizo_docs for user documentation.

### `avizo_plans` (~73 tokens)

Plans and pricing (EUR)

The four Avizo subscription plans (Free, Basic, Pro, Fleet) with monthly EUR prices, item/user limits, alert channels and feature lists. Generated from the same plan definitions the app enforces — null max_items/max_users means unlimited; null price_monthly_eur means custom pricing (see price_label).

### `avizo_categories` (~115 tokens)

Tracked document categories

All document/obligation categories Avizo tracks out of the box (Romanian display names — the product UI is Romanian): vehicles (ITP, RCA, road vignette, tachograph…), HR (occupational medicine, SSM/PSI trainings…), fiscal (permits, local taxes, contracts…), IT (domains…) and company documents. Each category carries its default alert lead times in days. Custom categories can be added by users.

Input parameters:

- `group` (string): Filter by group; omit for all 28 categories

### `avizo_docs` (~99 tokens)

User documentation (list or fetch one page)

Without arguments: lists every documentation page on avizo.ro/docs (quickstart, alert cadence, hierarchical escalation, SmartBill integration, API reference, troubleshooting) with slug and description. With {slug}: returns that page as markdown — the exact content the site renders. For programmatic integration read {slug: "api-reference"}.

Input parameters:

- `slug` (string): Doc slug from the list, e.g. "quickstart" or "api-reference"

### `avizo_my_items` (~121 tokens)

Your tracked documents and deadlines (requires API key)

The calling company's OWN tracked documents from Avizo, with days-to-expiry, urgency level (expired / critical ≤7 days / warning ≤30 / ok) and a recommended action per document. REQUIRES an Avizo API key (Pro/Fleet) sent as "Authorization: Bearer avizo_pk_...". Without a key the tool returns instructions for creating one — it never invents data. Read-only: nothing is modified.

Input parameters:

- `expiring_within_days` (integer): Only documents expiring within N days (server-side filter)

## Diagnostics

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

## Score history

- 2026-08-03: 76
- 2026-08-02: 76
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 72
- 2026-07-29: 72
- 2026-07-28: 71
- 2026-07-27: 70
- 2026-07-26: 69

## Links

- Remote endpoint: https://avizo.ro/mcp
- Website: https://avizo.ro/
- Changelog RSS feed: https://verifymcp.io/servers/ro-avizo-avizo-mcp/avizo/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ro-avizo-avizo-mcp/avizo/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ro-avizo-avizo-mcp/avizo