56
/ 100
10 days ago
glama

PEAK Account MCP Server

MCP server for PEAK Account, a Thai cloud accounting platform, enabling AI assistants to manage accounting data through natural language via the official REST API.

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.

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 16 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: PEAK_CONNECT_KEY, PEAK_SIGNATURE_SECRET, PEAK_USER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies16 high5 medium9 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.12.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.12.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.12.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highaxios@1.7.9GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.7.9GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// required environment variables
This server reads these from process.env. You'll be asked to provide them before it can run.
configPEAK_BASE_URL_PRODproduction https://api.peakaccount.com/api/v1
configPEAK_BASE_URL_UATuat https://peakengineapidev.azurewebsites.net/api/v1
configPEAK_CONNECT_ID... # sent in /clienttoken body
🔐 secretPEAK_CONNECT_KEY... # sent in /clienttoken body
configPEAK_ENVuat # "uat" (sandbox) or "production"
configPEAK_SIGNATURE_ENCODING=base64 # switch to "hex" if auth fails
🔐 secretPEAK_SIGNATURE_SECRET=connectId # switch to "connectKey" if auth fails
🔐 secretPEAK_USER_TOKEN... # per-business token, sent as header
// full audit trail
The full breakdown of what we checked, the deductions that landed, the network hosts, the dependency advisories, and concrete fix guidance is available to verified publishers.
// improvement guidance — verified publishers only
We have 3 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 Score](https://m8ven.ai/badge/mcp/savekikiz-peakaccountmcp-1ioqjc)](https://m8ven.ai/mcp/savekikiz-peakaccountmcp-1ioqjc)
commit: 92f7d5e3a01a953174677894c8cb398068c2244f
code hash: 443cf92722079cd3d7ec1b60a65eda401ca8888fc9490f6b08e135b09a628c2a
verified: 7/21/2026, 9:24:31 AM
view raw JSON →