ro.avizo/avizo-mcp
REMOTE · AVIZO.RO · SCANNED SEP 20
Avizo (RO SME compliance-deadline SaaS) as MCP tools: about, plans, categories, docs. Read-only.
Available components
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 → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 906 tokens (~50/item across 18 items; 5 tools + 13 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
How do I install the ro.avizo/avizo-mcp server?
ro.avizo/avizo-mcp is a hosted endpoint at https://avizo.ro/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.
remote · avizo.ro
claude mcp add --transport http ro-avizo-avizo-mcp 'https://avizo.ro/mcp'
{
"mcpServers": {
"ro-avizo-avizo-mcp": {
"url": "https://avizo.ro/mcp"
}
}
} {
"servers": {
"ro-avizo-avizo-mcp": {
"type": "http",
"url": "https://avizo.ro/mcp"
}
}
} [mcp_servers.ro-avizo-avizo-mcp] url = "https://avizo.ro/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ro-avizo-avizo-mcp": {
"type": "remote",
"url": "https://avizo.ro/mcp",
"enabled": true
}
}
} openclaw mcp add ro-avizo-avizo-mcp --url 'https://avizo.ro/mcp' --transport streamable-http
mcp_servers:
ro-avizo-avizo-mcp:
url: "https://avizo.ro/mcp" {
"McpServers": {
"ro-avizo-avizo-mcp": {
"Transport": "http",
"Url": "https://avizo.ro/mcp"
}
}
} assistant mcp add ro-avizo-avizo-mcp -t streamable-http -u 'https://avizo.ro/mcp'
{
"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.
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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 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
- 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
- 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 0
First indexed and scored.
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 20 Sept 2026 · Probed https://avizo.ro/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=avizo.ro | CN=YE2,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 628395cf92994848364881e9bfecfdb904f |
| SANs: *.avizo.ro, avizo.ro | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of avizo.ro. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ro. | present | 39877 | 8 | Verified |
| avizo.ro. | present | 2371 | 13 | Verified |
| avizo.ro. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://avizo.ro/mcp | Verified | 200 | |
| http (plaintext) | http://avizo.ro/mcp | HTTPS enforced | 301 | https://avizo.ro/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
avizo_about What Avizo is and how it works ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
avizo_categories Tracked document categories ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Filter by group; omit for all 28 categories |
No output schema declared.
No examples provided.
avizo_docs User documentation (list or fetch one page) ~99
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"}.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | Doc slug from the list, e.g. "quickstart" or "api-reference" |
No output schema declared.
No examples provided.
avizo_my_items Your tracked documents and deadlines (requires API key) ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expiring_within_days | integer | – | Only documents expiring within N days (server-side filter) |
No output schema declared.
No examples provided.
avizo_plans Plans and pricing (EUR) ~73
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the ro.avizo/avizo-mcp server?
ro.avizo/avizo-mcp is listed in the public MCP registry as ro.avizo/avizo-mcp. Avizo (RO SME compliance-deadline SaaS) as MCP tools: about, plans, categories, docs. Read-only. This page covers its hosted endpoint (https://avizo.ro/mcp).
Is the ro.avizo/avizo-mcp server safe to use?
ro.avizo/avizo-mcp scores 89 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 ro.avizo/avizo-mcp server expose?
ro.avizo/avizo-mcp exposes 5 tools: avizo_about, avizo_plans, avizo_categories, avizo_docs, avizo_my_items. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Does the ro.avizo/avizo-mcp server require authentication?
No. We connected to ro.avizo/avizo-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ro.avizo/avizo-mcp server still maintained?
ro.avizo/avizo-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.