Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/clipsense/-mcp-server/clipsense-mcp-servergit clone --depth 1 https://github.com/clipsense/-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/clipsense/-mcp-server/clipsense-mcp-server)<a href="https://agentmods.dev/mcp/clipsense/-mcp-server/clipsense-mcp-server"><img src="https://agentmods.dev/badge/mcp/clipsense/-mcp-server/clipsense-mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
clipsense-mcp-server scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 9 lines scan A 36d01867d2f9
clipsense-mcp-server is an MCP server published in the GitHub repository clipsense/-mcp-server (0 stars, last pushed 9mo ago), with no licence file. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
xcodebuildmcp
XcodeBuildMCP is a Model Context Protocol server that provides tools for Xcode project management, simulator management, and app utilities. Runs locally from the xcodebuildmcp npm package. Needs 1 environment variable to run.
android-sqlite-mcp
A Model Context Protocol (MCP) server to connect AI agents directly to the embedded SQLite/Room databases of your Android applications. Runs locally from the android-sqlite-mcp npm package.
expo-local-docs-mcp
MCP server for Expo documentation - reads local .mdx files for blazing fast performance. Works out of the box with zero configuration. Runs locally from the expo-local-docs-mcp npm package.
ulink
Deep linking for iOS, Android & Flutter. Firebase Dynamic Links alternative. Runs locally from the @ulinkly/mcp-server npm package. Needs 1 environment variable to run.
mcp-connect
MCP server for iOS Simulator control and browser automation - unified toolkit for mobile and web testing. Runs locally from the @plaintest/mcp-connect npm package.
haplane
鸿蒙 HAP 签名部署 MCP：面向鸿蒙应用开发者，真机调试一键签装，也走华为邀测/上架。中性工具+可订阅源，本地 stdio。. Runs locally from the haplane npm package.