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/ssembleinc/ssemble-mcp-server/mcp-servergit clone --depth 1 https://github.com/ssembleinc/ssemble-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/ssembleinc/ssemble-mcp-server/mcp-server)<a href="https://agentmods.dev/mcp/ssembleinc/ssemble-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/ssembleinc/ssemble-mcp-server/mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
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 5d 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
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@ssemble/mcp-server"
],
"env": {
"SSEMBLE_API_KEY": ""
}
}
}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.
- 5d ago First seen · 12 lines scan A 5c6704504e0b
mcp-server is an MCP server published in the GitHub repository ssembleinc/ssemble-mcp-server (6 stars, last pushed 5mo 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
memorix
Local-first project memory with legacy MCP and 2026 discovery compatibility. Runs locally from the memorix npm package.
transcriptor-mcp
MCP server "transcriptor-mcp" as configured in samson-art/transcriptor-mcp. Runs in Docker (docker.io/artsamsonov/transcriptor-mcp:1.2.4).
solana-mcp-vybe
MCP server "solana-mcp-vybe", hosted remotely at mcp.vybenetwork.xyz, as configured in vybenetwork/solana-mcp-vybe.
vybe-solana-api
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools. Remote server at docs.vybenetwork.com.
better-telegram-mcp
Production-grade MCP server for Telegram — dual-mode Bot API + MTProto, domain-separated tools. Runs locally from the better-telegram-mcp Python package. Needs 3 environment variables to run.
speclock
Enforce project constraints from CLAUDE.md, AGENTS.md, and .cursorrules before AI-generated edits, commands, and commits. Runs locally from the speclock npm package.