goflag

io.github.tancredesimoninPublished by GitHub account tancredesimoninv0.1.0Updated Nov 7, 2026

SEO and i18n audit of the site an agent is editing: localhost or protected preview, with sources.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Local MCP server that lets an agent audit the SEO and i18n of the site it is editing, on localhost or a preview, with the sources behind each rule.

What you can do
  • Audit a site URL for SEO and i18n findings, translation holes, broken links and coverage
  • Compare a fresh audit against a saved baseline to see what is new or resolved
  • Explain a rule: what it checks, why, its rigor and the documents behind it
  • List all rules by scope, severity and rigor
When to use it
Useful when an agent edits a site and should check the SEO and internationalization impact of its changes, for example auditing a local dev server after a change and re-running the audit after fixes.
Requirements
Runs locally over stdio via npx, so Node 22 or later is needed. Pages that render in the browser are audited in Chromium through the playwright package; without it, or with static mode, only server-rendered HTML is judged. No accounts, keys or headers are declared.
Before you install
All four tools are read-only and nothing is written to disk or to the site. It cannot send custom headers, so protected previews behind a token must be audited with the CLI instead. It never starts a dev server or writes a baseline; baselines must be captured with the CLI. External link checking is off by default.

Installation

In SourceWeft

  1. Open goflag in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@goflag/mcp

goflag as an MCP server. An agent audits the site it is editing — a dev server on localhost, a preview behind a VPN — and reads each rule with the documents that require it.

It runs locally, over stdio, on the same engine as @goflag/cli: an answer here is the answer goflag would print.

Getting started

Claude Code:

bash
claude mcp add goflag -- npx -y @goflag/mcp

Cursor (.cursor/mcp.json), VS Code (.vscode/mcp.json, under servers) and other clients take the same command:

json
{  "mcpServers": {    "goflag": { "command": "npx", "args": ["-y", "@goflag/mcp"] }  }}

Then ask your agent to check the SEO of what it just changed: it starts the dev server, calls audit_site on its URL, fixes what is new, and calls it again.

Tools

All four are read-only: none writes to disk or to the site.

ToolInputReturns
audit_siteurl; optional maxPages (default 50), locales, expectIndexing, static, advisories, checkExternal (default off)The findings rolled up by rule with their rigor, translation holes, broken links, the coverage, and the exit code the CLI would return
compare_to_baselinethe same, plus baseline: a JSON report saved by goflag --report or --update-baselineWhat is new, what was resolved, how many findings are unchanged
explain_ruleid, from a findingWhat the rule checks, why, its rigor, the documents behind it, and its page on goflag.tech
list_rulesoptional scope: page, site or proseEvery rule with its scope, severity and rigor

audit_site reports crawl progress to a client that asks for it, and stops when the call is cancelled.

What it does not do

  • No headers. A token passed as a tool argument would sit in the agent's transcript. Audit a protected preview with the CLI: goflag <url> --header "<name>: <value>".
  • No command to run. The agent starts its own dev server; this server never executes one.
  • No baseline written. Capture one with goflag <url> --update-baseline --baseline .goflag/baseline.json; compare_to_baseline only reads it, and refuses a file that is not a goflag report without quoting it.
  • No remote mode. It runs where the agent runs — which is why it can see localhost.

Requirements

Node 22 or later. A page that renders in the browser is audited in Chromium, through the playwright package; without it, or with static: true, the server-rendered HTML is judged instead.

Learn more

Source: packages/mcp/README.md at commit d9aa189

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 7, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts