Esa (aliyun) MCP Server

mcp-server-esa npm v1.1.0

Published by aliyun — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

ESA MCP Server - Modular Alibaba Cloud ESA tools for Edge Routine, Pages, and Site management

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 44

Each tool and what it can reach — statically extracted from the published source.

  • apply_certificateno sensitive capability
  • create_siteno sensitive capability
  • create_site_a_or_aaaa_recordno sensitive capability
  • create_site_cname_recordno sensitive capability
  • create_site_mx_recordno sensitive capability
  • create_site_ns_recordno sensitive capability
  • create_site_txt_recordno sensitive capability
  • delete_certificateno sensitive capability
  • delete_recordno sensitive capability
  • deployment_deleteno sensitive capability
Show 34 more tools ↓
  • er_record_createno sensitive capability
  • er_record_deleteno sensitive capability
  • er_record_listno sensitive capability
  • folder_deployno sensitive capability
  • get_certificateno sensitive capability
  • get_certificate_quotano sensitive capability
  • get_ipv6no sensitive capability
  • get_managed_transformno sensitive capability
  • get_recordno sensitive capability
  • get_site_pauseno sensitive capability
  • html_deployno sensitive capability
  • list_certificatesno sensitive capability
  • list_recordsno sensitive capability
  • list_sitesno sensitive capability
  • route_createno sensitive capability
  • route_deleteno sensitive capability
  • route_getno sensitive capability
  • route_updateno sensitive capability
  • routine_code_commitno sensitive capability
  • routine_code_deployno sensitive capability
  • routine_createno sensitive capability
  • routine_deleteno sensitive capability
  • routine_getno sensitive capability
  • routine_listno sensitive capability
  • routine_route_listno sensitive capability
  • set_certificateno sensitive capability
  • site_active_listno sensitive capability
  • site_matchno sensitive capability
  • site_record_listno sensitive capability
  • site_route_listno sensitive capability
  • update_ipv6no sensitive capability
  • update_managed_transformno sensitive capability
  • update_recordno sensitive capability
  • update_site_pauseno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.0 latest A 99/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-server-esa/badge.svg)](https://mcptrustchecker.com/registry/mcp-server-esa)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-server-esa"><img src="https://mcptrustchecker.com/registry/mcp-server-esa/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-server-esa/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-server-esa --online

Use the free API → How scoring works

Other implementations of Esa 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Other