Avanan MSP (Legacy SmartAPI)
OCI · GHCR.IO/WYRE-TECHNOLOGY/AVANAN-LEGACY-MCP:V1.1.0
MCP server for the Avanan MSP SmartAPI — manage child MSPs, users, tenants, licenses, and usage.
Available components
Last scanned (2 hours ago)
Scores higher than 68% of OCI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 111 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1114 tokens (~61/item across 18 items; 17 tools + 1 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "avanan_delete_msp_partner" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 18 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (13)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
- Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 2 Nov 26 0
- Provenance: fail → unverified ▼ security
- Stability: 0.97 → pass security
- 1 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 −1
- Provenance: unverified → fail ▼ security
- Stability: pass → 0.93 functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 27 Oct 26 0
- Provenance: fail → unverified ▼ security
- 25 Oct 26 0
- Provenance: unverified → fail ▼ security
- Security disclosure: unverified → fail ▼ functional
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 6 Nov 2026 · Analysed oci/ghcr.io/wyre-technology/avanan-legacy-mcp:v1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
avanan_assign_license ~113
Assign a license (and optional add-ons) to an existing customer tenant.
| Name | Type | Req | Description |
|---|---|---|---|
| addonIdList | array | – | Optional list of add-on IDs from avanan_list_addons. |
| licenseCodeName | string | yes | Code name of the desired license from avanan_list_licenses (e.g. 'complete_malware'). |
| maxLicensedUsers | integer | – | Optional maximum number of users for the tenant under this license. |
| tenant_id | integer | yes | Avanan tenant ID to assign the license to. |
No output schema declared.
No examples provided.
avanan_create_msp_partner ~36
Create a new child MSP partner under the current MSP.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name of the new MSP partner. |
No output schema declared.
No examples provided.
avanan_create_msp_user ~143
Create a new MSP user.
| Name | Type | Req | Description |
|---|---|---|---|
| directLogin | boolean | yes | Allow password login to the MSP portal. |
| string | yes | User email address. | |
| firstName | string | yes | User first name. |
| lastName | string | yes | User last name. |
| receiveWeeklyReports | boolean | yes | Send weekly reports from customer tenants to this user. |
| role | string | yes | User role. |
| samlLogin | boolean | yes | Allow SAML login to the MSP portal. |
| sendAlerts | boolean | yes | Send customer tenant alerts to this user. |
| viewPrivateData | boolean | yes | Allow the user to view private data on customer portals. |
No output schema declared.
No examples provided.
avanan_create_tenant ~111
Create a new customer tenant under the current MSP.
| Name | Type | Req | Description |
|---|---|---|---|
| adminEmail | string | yes | Tenant administrator email. |
| adminName | string | yes | Tenant administrator's first and last name. |
| companyName | string | yes | Name of the company associated with the tenant. |
| phone | string | yes | Tenant administrator phone number (10 digits). |
| tenantName | string | yes | Tenant name (used in the customer portal domain). |
| tenantRegion | string | yes | Country code for tenant creation region (lowercase). |
No output schema declared.
No examples provided.
avanan_delete_msp_partner ~48
Delete a child MSP partner by ID. WARNING: all tenants associated with this MSP are also deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| msp_id | integer | yes | ID of the MSP partner to delete. |
No output schema declared.
No examples provided.
avanan_delete_msp_user ~30
Delete an MSP user by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | MSP user ID. |
No output schema declared.
No examples provided.
avanan_delete_tenant ~41
Delete a customer tenant by ID. WARNING: this deletes the tenant and all its data.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | integer | yes | Avanan tenant ID. |
No output schema declared.
No examples provided.
avanan_get_daily_usage ~64
Get daily usage details across all customer tenants for a specific year/month/day.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | Day of month. |
| month | integer | yes | Month, 1-12. |
| year | integer | yes | Year, e.g. 2024. |
No output schema declared.
No examples provided.
avanan_get_monthly_usage ~72
Get monthly usage details across all customer tenants for a given year/month. Returns per-day, per-tenant rows with user count, daily price, and cost.
| Name | Type | Req | Description |
|---|---|---|---|
| month | integer | yes | Month, 1-12. |
| year | integer | yes | Year, e.g. 2024. |
No output schema declared.
No examples provided.
avanan_get_msp_user ~31
Get a single MSP user by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | MSP user ID. |
No output schema declared.
No examples provided.
avanan_get_tenant ~48
Get details of a single customer tenant by ID, including license, PoC/paid dates, user count, and expiration.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | integer | yes | Avanan tenant ID. |
No output schema declared.
No examples provided.
avanan_list_addons ~35
List all available license add-ons (id, name). Add-on IDs are used when assigning a license to a tenant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
avanan_list_licenses ~37
List all available license packages (id, codeName, displayName). Use the codeName when assigning a license to a tenant.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
avanan_list_msp_partners ~33
List all associated child MSP partners under the current MSP. Returns id and name for each child MSP.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
avanan_list_msp_users ~32
List all MSP users.
| Name | Type | Req | Description |
|---|---|---|---|
| scrollId | string | – | Pagination scroll ID from a previous response. |
No output schema declared.
No examples provided.
avanan_list_tenants ~56
List all customer tenants associated with the current MSP. Each tenant entry includes domain, deployment mode, user counts, status, license package and add-ons.
| Name | Type | Req | Description |
|---|---|---|---|
| scrollId | string | – | Pagination scroll ID from a previous response. |
No output schema declared.
No examples provided.
avanan_update_msp_user ~165
Update an MSP user by ID. All fields are required per the SmartAPI spec.
| Name | Type | Req | Description |
|---|---|---|---|
| directLogin | boolean | yes | Allow password login to the MSP portal. |
| string | yes | User email address. | |
| firstName | string | yes | User first name. |
| lastName | string | yes | User last name. |
| receiveWeeklyReports | boolean | yes | Send weekly reports from customer tenants to this user. |
| role | string | yes | User role. |
| samlLogin | boolean | yes | Allow SAML login to the MSP portal. |
| sendAlerts | boolean | yes | Send customer tenant alerts to this user. |
| user_id | integer | yes | MSP user ID. |
| viewPrivateData | boolean | yes | Allow the user to view private data on customer portals. |
No output schema declared.
No examples provided.
How do I install the Avanan MSP (Legacy SmartAPI) MCP server?
Avanan MSP (Legacy SmartAPI) runs locally as a container image, launched with docker run --rm -i -e AVANAN_APP_ID -e AVANAN_TOKEN -e AVANAN_SECRET -e AVANAN_REGION -e MCP_TRANSPORT -e MCP_HTTP_PORT -e LOG_LEVEL ghcr.io/wyre-technology/avanan-legacy-mcp:v1.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/wyre-technology/avanan-legacy-mcp:v1.1.0
claude mcp add wyre-technology-avanan-legacy-mcp -- docker run --rm -i -e AVANAN_APP_ID -e AVANAN_TOKEN -e AVANAN_SECRET -e AVANAN_REGION -e MCP_TRANSPORT -e MCP_HTTP_PORT -e LOG_LEVEL ghcr.io/wyre-technology/avanan-legacy-mcp:v1.1.0
This image reads AVANAN_APP_ID, AVANAN_TOKEN, AVANAN_SECRET, AVANAN_REGION, MCP_TRANSPORT, MCP_HTTP_PORT and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Avanan MSP (Legacy SmartAPI) MCP server?
Avanan MSP (Legacy SmartAPI) is an MCP server listed in the public MCP registry as io.github.wyre-technology/avanan-legacy-mcp. MCP server for the Avanan MSP SmartAPI, manage child MSPs, users, tenants, licenses, and usage. This page covers its container image (ghcr.io/wyre-technology/avanan-legacy-mcp:v1.1.0).
Is the Avanan MSP (Legacy SmartAPI) MCP server safe to use?
Avanan MSP (Legacy SmartAPI) scores 47 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 Avanan MSP (Legacy SmartAPI) MCP server expose?
Avanan MSP (Legacy SmartAPI) exposes 17 tools: avanan_list_msp_partners, avanan_create_msp_partner, avanan_delete_msp_partner, avanan_list_msp_users, avanan_get_msp_user, and 12 more. Their descriptions and schemas cost roughly 1,095 tokens of context every time the server is loaded.
Is the Avanan MSP (Legacy SmartAPI) MCP server still maintained?
Avanan MSP (Legacy SmartAPI) is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Avanan MSP (Legacy SmartAPI) MCP server?
VerifyMCP ran 13 checks on Avanan MSP (Legacy SmartAPI), covering Source repository, Provenance, License, Maintenance and 9 more. 4 items could not be completed, a gap on our side rather than a finding about Avanan MSP (Legacy SmartAPI): Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.