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/rampify-dev/rampify-mcp/rampify-mcpgit clone --depth 1 https://github.com/rampify-dev/rampify-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/rampify-dev/rampify-mcp/rampify-mcp)<a href="https://agentmods.dev/mcp/rampify-dev/rampify-mcp/rampify-mcp"><img src="https://agentmods.dev/badge/mcp/rampify-dev/rampify-mcp/rampify-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
rampify-mcp 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.
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.
- 5d ago First seen · 6 lines scan A c257cafc5391
rampify-mcp is an MCP server published in the GitHub repository rampify-dev/rampify-mcp (3 stars, last pushed 2mo 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
mcp-search-console
Google Search Console integration for Model Context Protocol (MCP). Runs locally from the mcp-search-console Python package. Needs 3 environment variables to run.
search-console-mcp
Google Search Console + Bing + GA4 + AdSense — unified SEO intelligence for AI agents. Runs locally from the search-console-mcp npm package. Needs 3 environment variables to run.
screaming-frog-mcp
Headless MCP server for Screaming Frog SEO Spider — run crawls, export and analyze crawl data via the CLI, no GUI session required. Built for scheduled audits, CI, and AI agents. Runs locally from the screaming-frog-mcp Python package. Needs 1 environment variable to run.
sqlew
Automated ADR (Architecture Decision Records) for AI Coding Agents - MCP server with SQL-backed decision repository. Runs locally from the sqlew npm package.
mcp
Track keyword rankings, research SEO opportunities, and manage bisibility projects with AI agents. Runs locally from the @bisibility/mcp npm package. Needs 5 environment variables to run.
keyword-research
SEO keyword research with Google Suggest, intent scoring, long-tail discovery. x402. Remote server at keyword-research.api.klymax402.com.