Connector For Akamai MCP Server
mcp-connector-for-akamai
npm
v0.1.2
Published by amankrokx — 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.
An unofficial MCP (Model Context Protocol) server that connects AI assistants to Akamai APIs for edge diagnostics, debugging, and network analysis.
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 − 4 = 96. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −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 3
medium Unconstrained URL/host parameter "url" on "connectivity_problems"MTC-CAP-007
Tool "connectivity_problems" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool connectivity_problems · inputSchema.properties.url
medium Unconstrained URL/host parameter "url" on "content_problems"MTC-CAP-007
Tool "content_problems" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool content_problems · inputSchema.properties.url
medium Unconstrained URL/host parameter "url" on "curl_from_edge"MTC-CAP-007
Tool "curl_from_edge" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool curl_from_edge · inputSchema.properties.url
Tools 14
Each tool and what it can reach — statically extracted from the published source.
connectivity_problemsnetwork egresscontent_problemsnetwork egresscurl_from_edgenetwork egressdig_from_edgeno sensitive capabilityget_error_statisticsno sensitive capabilitygrep_edge_logsno sensitive capabilitylist_edge_locationsno sensitive capabilitylocate_ipno sensitive capabilitymtr_from_edgeno sensitive capabilitytranslate_akamaized_urlno sensitive capability
Show 4 more tools ↓
translate_error_stringno sensitive capabilityurl_health_checkno sensitive capabilityverify_edge_ipno sensitive capabilityverify_locate_ipno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (14 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.2 latest |
A 96/100 | 3 | 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.
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-connector-for-akamai --onlineMore in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.