SEO and i18n audit of the site an agent is editing: localhost or protected preview, with sources.
MCPpedia last refreshed this data
io.github.tancredesimonin/goflag is an MCP server that SEO and i18n audit of the site an agent is editing: localhost or protected preview, with sources. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 62/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-tancredesimonin-goflag": {
"args": [
"-y",
"@goflag/mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
SEO and i18n audit of the site an agent is editing: localhost or protected preview, with sources.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @goflag/mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in marketing
Search Console, Google Analytics and keyword data for your AI agent.
DataForSEO API modelcontextprotocol server
Newsletters where you pay for the emails you send, not for dormant subscribers, at a fraction of the price of beehiiv and the like. Open source: self-host it, or use mailcheap.ai.
X/Twitter automation MCP: scrape, post, schedule, analyze, engage. No API key required.
MCP Security Weekly
Get CVE alerts and security updates for io.github.tancredesimonin/goflag and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A CLI that audits a site for broken links, missing translation pages, a robots.txt that contradicts your pages, and missing or misconfigured SEO metadata — and a Next.js library that produces the HTML it would have nothing to say about.
The first eleven lines of a real run. Rendered from the same transcript the documentation site paints, which is compared to the renderers byte for byte — so this picture cannot drift from what the command prints.
Goflag crawls a site once and judges what it found. It is deliberately small: no dashboard, no config system, no social-preview gallery. Just the findings, as a machine-readable report you can pipe, diff, or gate CI on.
It is built for the mistakes that are invisible while browsing and expensive in
search: a hreflang that points at a 404, a canonical that silently
de-indexes a page, a robots.txt that contradicts every <meta name="robots">
on the site. A human cannot check those on 400 pages. That is the whole job.
npx @goflag/cli https://example.com # one-off, nothing installed
pnpm add -D @goflag/cli # then: pnpm goflag https://example.com
Install it as a dev dependency once you run it more than once — in a script, in
CI, in a git hook. npx is for trying it. The package is @goflag/cli; the
command it installs is goflag. Everything under the brand lives in the
@goflag scope; the bare goflag name on npm is a deprecated signpost pointing
here and carries no code.
>=22.playwright is an optional peer dependency. Add it only if you audit client-rendered pages without --static: pnpm add -D playwright && pnpm exec playwright install chromium.pnpm install, then see AGENTS.md.HEAD→GET fallback, redirect-chain/loop detection, soft-404 and anti-bot (403/429) triage. Broken links are mapped back to the pages that reference them.route × locale matrix and flags every route that exists in one locale but is missing in another, plus hreflang reciprocity gaps (A → B with no B → A), missing x-default, and locale tags naming a language, script or region that does not exist. Rows are keyed by pathname, unless the site declares its translation clusters — either with xhtml:link in the sitemap, or with reciprocal hreflang between two crawled pages' <head>. Then those declarations decide which URLs are one page, whatever their slugs, and the run reports diagnostics.declaredClusters. The sitemap source survives --coverage structural, where the two locales of a slug-translating family are rarely both sampled; the <head> source needs both pages in hand and is what fixes the common site that declares properly there and nothing in its sitemap.