avanan-legacy-mcp (WYRE-AI/avanan-legacy-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Warning
74/100

avanan-legacy-mcp

A legacy MCP server for Avanan cloud email security, providing tools to manage threat detection, email policies, and security incidents through Avanan's API.

→ WYRE-AI/avanan-legacy-mcp· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

WYRE-AI

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: AVANAN_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Code appears obfuscated
1 file are unreadable to a human reviewer. Cannot audit what they do.
🔐
You'll be asked for 2 credentials: AVANAN_SECRET, AVANAN_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes17 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

avanan_list_msp_partners
avanan_create_msp_partner
avanan_delete_msp_partner
avanan_list_msp_users
avanan_get_msp_user
avanan_create_msp_user
avanan_update_msp_user
avanan_delete_msp_user
avanan_list_tenants
avanan_get_tenant
avanan_create_tenant
avanan_delete_tenant
avanan_list_licenses
avanan_list_addons
avanan_assign_license
avanan_get_monthly_usage
avanan_get_daily_usage
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAVANAN_APP_IDApplication ID provided by Avanan Support (x-av-app-id).
configAVANAN_REGIONap. Defaults to JWT region claim, then us.
🔐 secretAVANAN_SECRETShared secret used to compute the x-av-sig HMAC.
🔐 secretAVANAN_TOKENToken from the Avanan auth handshake (x-av-token).
configLOG_LEVELerror (default info).
configMCP_HTTP_PORTHTTP transport port (default 8080).
configMCP_TRANSPORTstdio (default) or http.
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

17/17 tools missing one or more hints — avanan_list_msp_partners (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); avanan_create_msp_partner (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); avanan_delete_msp_partner (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 1/17 tools referenced in tests (6%)

Write tests that reference each tool by name so every tool has at least one test.

Readable source code

1 file are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/wyre-technology/avanan-legacy-mcp?variant=verified)](https://m8ven.ai/mcp/wyre-technology/avanan-legacy-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e124a3b5b723349eb75efc360d7900c3a72a262a
code hash: e878b54546c721ccae50263d811f8125a2ef91ef4e954f3058a6f684d0172aea
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client