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.
git clone --depth 1 https://github.com/liftli-ai/liftli-mcpWrote 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/liftli-ai/liftli-mcp/liftli)<a href="https://agentmods.dev/mcp/liftli-ai/liftli-mcp/liftli"><img src="https://agentmods.dev/badge/mcp/liftli-ai/liftli-mcp/liftli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/liftli-ai/liftli-mcp/liftli"><img src="https://agentmods.dev/badge/mcp/liftli-ai/liftli-mcp/liftli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
liftli 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 1mo 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.
What it actually says
{
"liftli": {
"url": "https://liftli-strategist-mcp.onrender.com/mcp",
"type": "streamable-http"
}
}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.
- 1mo ago First seen · 6 lines scan A c9f7f7609295
liftli is an MCP server published in the GitHub repository liftli-ai/liftli-mcp (0 stars, last pushed 11d ago), licensed MIT. 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
linkedin-mcp-server
MCP server "linkedin-mcp-server" as configured in stickerdaniel/linkedin-mcp-server.
unlinked
MCP server that brings your LinkedIn professional profile and experience into your context. Runs locally from the @larsbaunwall/unlinked npm package. Needs 2 environment variables to run.
1social
Publish, schedule and verify social posts across seven networks from your AI assistant. Remote server at mcp.1social.dev.
reddit-radar
MCP server to find Reddit threads where your product genuinely fits, reconstruct the conversation, and gate drafted replies against a claim boundary you define. Read-only: never posts, votes, or automates an account. Runs locally from the reddit-radar-mcp npm package. Needs 9 environment variables to run.
linkedin-engine-cli
MCP server "linkedin-engine-cli" as configured in styfinity/linkedin-engine. Runs locally from the @styfinity/linkedin-engine-cli npm package.
publiar
MCP server "publiar" as configured in TokDar2410621/publiar-mcp. Launched with publiar-mcp. Needs 2 environment variables to run.