goflag
NPM · @GOFLAG/MCP
SEO and i18n audit of the site an agent is editing: localhost or protected preview, with sources.
Available components
Last scanned (18 hours ago)
Scores higher than 53% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 115 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 744 tokens (~186/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 8 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.0 → 0.1.2 functional
- Package version: 0.1.0 → 0.1.1 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@goflag/mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 115 packages
| Packages resolved | 115 |
|---|---|
| Deprecated | 1 |
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_site Audit a site ~222
Crawl a site — a local dev server, a preview or production — and judge its SEO and i18n plumbing. Returns the findings rolled up by rule, each with its rigor, plus translation holes, broken links and the pages audited.
| Name | Type | Req | Description |
|---|---|---|---|
| advisories | boolean | – | Also return the questions a linter cannot settle, with their evidence, for you to judge. |
| checkExternal | boolean | – | Also probe links to other sites. Off by default: slow, and not your site's fault. |
| expectIndexing | string | – | "no" for a staging or preview host that must stay out of search indexes. |
| locales | array | – | Locales the site serves, e.g. ["en", "fr"], when its sitemap does not say. |
| maxPages | integer | – | Page budget. Default 50. |
| static | boolean | – | Never launch Chromium; judge the server-rendered HTML only. |
| url | string | yes | The site to audit, http or https. A dev server's URL works: http://localhost:3000. |
No output schema declared.
No examples provided.
compare_to_baseline Compare to a baseline ~250
Audit a site and compare it to a report saved earlier with the goflag CLI (--report or --update-baseline). Returns what is new, what was resolved, and how many findings are unchanged: the question a change has to answer is whether it made things worse.
| Name | Type | Req | Description |
|---|---|---|---|
| advisories | boolean | – | Also return the questions a linter cannot settle, with their evidence, for you to judge. |
| baseline | string | yes | Path to the saved JSON report, relative to where this server runs. |
| checkExternal | boolean | – | Also probe links to other sites. Off by default: slow, and not your site's fault. |
| expectIndexing | string | – | "no" for a staging or preview host that must stay out of search indexes. |
| locales | array | – | Locales the site serves, e.g. ["en", "fr"], when its sitemap does not say. |
| maxPages | integer | – | Page budget. Default 50. |
| static | boolean | – | Never launch Chromium; judge the server-rendered HTML only. |
| url | string | yes | The site to audit, http or https. A dev server's URL works: http://localhost:3000. |
No output schema declared.
No examples provided.
explain_rule Explain a rule ~63
What one goflag rule checks, why, how authoritative it is (rigor), the documents that require it, and what a passing page looks like.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A rule id from a finding, e.g. "hreflang.cluster-incomplete". |
No output schema declared.
No examples provided.
list_rules List the rules ~53
Every rule goflag runs, with its scope (page, site, prose), severity and rigor. Prose rules are questions for a reviewer, never findings.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | Only the rules of one scope. |
No output schema declared.
No examples provided.
How do I install the goflag MCP server?
goflag runs locally as an npm package, launched with npx -y @goflag/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @goflag/mcp
claude mcp add tancredesimonin-goflag -- npx -y @goflag/mcp
What is the goflag MCP server?
goflag is an MCP server listed in the public MCP registry as io.github.tancredesimonin/goflag. SEO and i18n audit of the site an agent is editing: localhost or protected preview, with sources. This page covers its npm package (@goflag/mcp).
Is the goflag MCP server safe to use?
goflag scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the goflag MCP server expose?
goflag exposes 4 tools: audit_site, compare_to_baseline, explain_rule, list_rules. Their descriptions and schemas cost roughly 588 tokens of context every time the server is loaded.
Is the goflag MCP server still maintained?
goflag is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the goflag MCP server under?
goflag declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the goflag MCP server?
VerifyMCP ran 16 checks on goflag, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.