dev.rampify/rampify-mcp

MCPcommunitylive
v1.0.0dev.rampifyUnknownUpdated 3mo agoGitHub

SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.

Endpoint healthlive
checked 5 days ago · 162ms · auth required
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authordev.rampify
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubrampify-dev/rampify-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface19 tools · none privileged
Security scan✓ CleanvHEAD · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

19 tools · none privileged
Statically extracted from the published packagevHEAD · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

get_page_seoNo description published

This tool published no description. Forge does not invent one.

get_issuesNo description published

This tool published no description. Forge does not invent one.

crawl_siteNo description published

This tool published no description. Forge does not invent one.

generate_schemaNo description published

This tool published no description. Forge does not invent one.

generate_metaNo description published

This tool published no description. Forge does not invent one.

get_gsc_insightsNo description published

This tool published no description. Forge does not invent one.

create_feature_specNo description published

This tool published no description. Forge does not invent one.

get_feature_specNo description published

This tool published no description. Forge does not invent one.

update_feature_specNo description published

This tool published no description. Forge does not invent one.

list_feature_specsNo description published

This tool published no description. Forge does not invent one.

link_commitNo description published

This tool published no description. Forge does not invent one.

get_commit_messageNo description published

This tool published no description. Forge does not invent one.

create_keyword_clusterNo description published

This tool published no description. Forge does not invent one.

get_keyword_clustersNo description published

This tool published no description. Forge does not invent one.

create_content_specNo description published

This tool published no description. Forge does not invent one.

lookup_keywordsNo description published

This tool published no description. Forge does not invent one.

suggest_keywordsNo description published

This tool published no description. Forge does not invent one.

optimize_contentNo description published

This tool published no description. Forge does not invent one.

get_security_contextNo description published

This tool published no description. Forge does not invent one.

0 of 19 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

19 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.