UnClick MCP Server (malamutemayhem/unclick) is an MCP server listed on the M8ven Trust Index. It scores 48 out of 100, grade D. It declares 63 tools. No publisher has claimed this listing.

D
Caution
48/100

UnClick MCP Server

MCP server for the UnClick agent platform, providing native endpoint tools for browser automation and AI agent workflows.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we 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

malamutemayhem

Source: Glama · also listed on npm

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 →

Install from

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
8 flows detected: UNCLICK_API_KEY, ALGOLIA_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
⚠️
Known vulnerabilities in dependencies: 7 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: ALGOLIA_API_KEY, BGG_API_TOKEN, BITBUCKET_APP_PASSWORD, UNCLICK_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies7 high1 medium4 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.15.1GHSA-345p-7cg4-v4c7

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

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

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

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

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

highjs-yaml@4.2.0GHSA-2883-xcg3-v3hh

js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

highjs-yaml@4.2.0GHSA-52cp-r559-cp3m

js-yaml: YAML merge-key chains can force quadratic CPU consumption

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
configABN_GUID
configABN_TIMEOUT_MS
configABUSEIPDB_TIMEOUT_MS
configADVICESLIP_TIMEOUT_MS
configAFFIRMATION_TIMEOUT_MS
configAGIFY_TIMEOUT_MS
configAIRTABLE_TIMEOUT_MS
🔐 secretALGOLIA_API_KEY
configALGOLIA_APP_ID
configALGOLIA_TIMEOUT_MS
configALPHAVANTAGE_TIMEOUT_MS
configAMAZON_TIMEOUT_MS
configAMBER_HOME_SITE_ID
configAMBER_TIMEOUT_MS
configANTHROPIC_TIMEOUT_MS
configAOE2_TIMEOUT_MS
configARCHIVEORG_TIMEOUT_MS
configASANA_TIMEOUT_MS
configASSEMBLYAI_TIMEOUT_MS
configAUSPOST_TIMEOUT_MS
configBANDSINTOWN_APP_ID
configBANDSINTOWN_TIMEOUT_MS
🔐 secretBGG_API_TOKEN
configBGG_TIMEOUT_MS
configBIBLE_TIMEOUT_MS
🔐 secretBITBUCKET_APP_PASSWORD
configBITBUCKET_TIMEOUT_MS
configBITBUCKET_USERNAME
configBLUESKY_TIMEOUT_MS
configBORED_TIMEOUT_MS
configBREVO_TIMEOUT_MS
configBREWERY_TIMEOUT_MS
configBUNGIE_TIMEOUT_MS
configCALCOM_TIMEOUT_MS
configCALENDLY_TIMEOUT_MS
configSPORTSDB_TIMEOUT_MS
configUMAMI_URL
configUMAMI_WEBSITE_ID
configUNCLICK_AGENT_ID
🔐 secretUNCLICK_API_KEYYour UnClick API key
configUNCLICK_API_KEY_HASH
configUNCLICK_CLIENT_USER_AGENT
configUNCLICK_MEMORY_BASE_URL
configUNCLICK_SEAT_TOOL_MODE
configUNCLICK_SITE_URL
// 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

63/63 tools missing one or more hints — unclick_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); unclick_browse (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); unclick_tool_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +60 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

21/63 tools referenced in tests (33%)

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

Production dependencies are patched

0 critical, 7 high severity in production deps — @modelcontextprotocol/sdk@1.15.1 (high), @modelcontextprotocol/sdk@1.15.1 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

2/18 production deps stale: imap@2022-06-19 (4.2y), @iarna/toml@2023-07-15 (3.2y)

Domain consistency

npm scope @unclick doesn't match GitHub owner malamutemayhem

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 5 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/malamutemayhem/unclick-agent-native-endpoints?variant=verified)](https://m8ven.ai/mcp/malamutemayhem/unclick-agent-native-endpoints)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 89d8792d452fb4e021c07a7eb8f501faa442417e
code hash: d35bc3b4c97e9c5aea9c0101644648684307b57726ce821bfd38cb7eb6985571
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