Findable

findable-page3stars

Offline SEO + AEO + GEO auditor for the AI search era: CLI, MCP server, and edge API

1# Findable

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-27

Stars: 3
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Findable?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Findable need an API key?

No required environment variable is listed on this record.

What transport does Findable use?

Findable runs locally over stdio.

When was Findable last checked?

Last checked 2026-10-27. Offline SEO + AEO + GEO auditor for the AI search era: CLI, MCP server, and edge API

From the publisher

Documentation

Is your site findable by Google AND by ChatGPT/Perplexity?

findable: SEO + AEO + GEO auditor for the AI search era (CLI, MCP, edge API). Scores summarise findable's own checks; they do not measure Google rankings or AI citations.

Live demo: https://findable.page · Learn: https://findable.page/learn · The build story

findable web UI showing a score hero, family cards and a failing-first issue list

Why

AI answer engines now sit between your page and your reader. They tend to quote short, structured, attributed passages. A page can rank well on Google and still not be cited in a ChatGPT or Perplexity answer.

findable checks the signals answer engines are documented or commonly reported to use: whether a machine can lift a clean answer out of the page (AEO), and whether the page carries trust signals a generative engine may use to cite it (GEO), alongside classic SEO. It is written in Go with no account and no quota. Scoring a local HTML file is fully offline; URL, crawl and site checks make network requests, and the hosted API exists if you prefer not to run it yourself.

Scoring model

One overall score from 0 to 100, built from three families:

Family	Weight	Page checks	What it measures
SEO	50%	98	Title and meta tags, headings, canonical, Open Graph and Twitter cards, mobile, HTTPS and security headers, accessibility landmarks
AEO (answer engine optimization)	25%	35	Structured data, FAQ markup, short direct answers, question headings, lists, tables, steps, readability
GEO (generative engine optimization)	25%	27	Author and organization markup, dates, citations and quotes, passage-ready blocks, trust links, no snippet blocking

That is 160 page checks in the Go engine. The edge API runs a port with the same 160. Seven more site checks are opt-in (-site) and unscored: robots.txt present, the page allowed for *, GPTBot, ClaudeBot, PerplexityBot and Google-Extended, and /llms.txt present. Every failing check names what to fix.

Quickstart

go install github.com/findable-page/findable/cmd/findable@latest   # Go 1.26+

Homebrew: planned for first release; use go install.

Then:

findable https://example.com
findable ./page.html          # local file, no server needed

It prints the four scores and the failing checks, and saves a report file in -o (default .).

CLI

findable [-o dir] [-format csv|json|sarif] [-fail-under N] [-q] [-k keyphrase]
         [-site] [-crawl] [-sitemap url] [-limit N] [-serve :port] [-mcp] [-allow-private] <url or file>

Flag	Meaning
`-format csv\|json\|sarif`	Report format. `json` is the same object `/api/scan` returns, `sarif` is SARIF 2.1.0 for GitHub code scanning. Default `csv`.
`-fail-under N`	Exit 1 and name every page whose overall score is below N.
`-sitemap URL`	Audit the pages a sitemap lists. Sitemap indexes are followed.
`-site`	Also run the 7 site checks (robots.txt, AI crawlers, llms.txt).
`-crawl`	Follow internal links, up to `-limit` pages (default 20).
`-k`	Focus keyphrase. Only the edge API scores it today; the offline engine ignores it.
`-o`, `-q`	Report directory; `-q` hides the failing-check list.
`-serve 127.0.0.1:8080`	Local API and web UI. Bind to localhost; `:8080` listens on every interface.
`-mcp`	MCP server over stdio.
`-allow-private`	Allow localhost and private-network targets. Without it every fetch, including crawl and sitemap links and MCP, refuses non-public hosts, ignores `HTTPS_PROXY`/`HTTP_PROXY`, and only connects to ports 80 and 443. With it the CLI uses a plain HTTP client: no address guard, any port, proxy variables honoured. `-serve` is always guarded and ignores this flag.

findable -q -format sarif -fail-under 70 https://example.com
findable -sitemap https://example.com/sitemap.xml -limit 50
findable -site -crawl -limit 10 https://example.com

MCP for agents

Add to Claude Desktop, Cursor or Windsurf:

{ "mcpServers": { "findable": { "command": "findable", "args": ["-mcp"] } } }

No Go toolchain? Build the MCP server from source: (cd mcp && bun install && bun run build), then use { "command": "node", "args": ["/path/to/findable/mcp/dist/index.js"] }.

Tools: audit_page (URL or file), audit_html_content (raw HTML, no network), crawl_site, generate_csv_report. Prompt: seo_audit_prompt.

API

Hosted at https://findable.page (source: findable-page/findable-page), or run your own local server with findable -serve 127.0.0.1:8080.

curl -s -X POST https://findable.page/api/scan \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","keyphrase":"example","site":true}'

/api/scan only fetches public hosts: ports 80 and 443, 5 redirects, 10 seconds, 5 MB, rate limited. See SECURITY.md.

GitHub Action

permissions:
  security-events: write
steps:
  - uses: findable-page/[email protected]
    with:
      url: https://example.com
      fail-under: 70
      args: -site

The action builds the CLI, uploads failing checks to code scanning as SARIF, then fails the job below fail-under.

Development

git clone https://github.com/findable-page/findable && cd findable
(cd mcp && bun install)
make test

See CONTRIBUTING.md and CHANGELOG.md. testdata/ holds sample pages.

License

MIT

Findable

findable-page3stars

Offline SEO + AEO + GEO auditor for the AI search era: CLI, MCP server, and edge API

Marketing

Install Run on PlugMCP

GitHub Website

Run on PlugMCP

1# Findable

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-27

Stars: 3
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Findable?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Findable need an API key?

No required environment variable is listed on this record.

What transport does Findable use?

Findable runs locally over stdio.

When was Findable last checked?

Last checked 2026-10-27. Offline SEO + AEO + GEO auditor for the AI search era: CLI, MCP server, and edge API

From the publisher

Documentation

Is your site findable by Google AND by ChatGPT/Perplexity?

findable: SEO + AEO + GEO auditor for the AI search era (CLI, MCP, edge API). Scores summarise findable's own checks; they do not measure Google rankings or AI citations.

Live demo: https://findable.page · Learn: https://findable.page/learn · The build story

findable web UI showing a score hero, family cards and a failing-first issue list

Why

Scoring model

One overall score from 0 to 100, built from three families:

Family	Weight	Page checks	What it measures
SEO	50%	98	Title and meta tags, headings, canonical, Open Graph and Twitter cards, mobile, HTTPS and security headers, accessibility landmarks
AEO (answer engine optimization)	25%	35	Structured data, FAQ markup, short direct answers, question headings, lists, tables, steps, readability
GEO (generative engine optimization)	25%	27	Author and organization markup, dates, citations and quotes, passage-ready blocks, trust links, no snippet blocking

Quickstart

go install github.com/findable-page/findable/cmd/findable@latest   # Go 1.26+

Homebrew: planned for first release; use go install.

Then:

findable https://example.com
findable ./page.html          # local file, no server needed

It prints the four scores and the failing checks, and saves a report file in -o (default .).

CLI

findable [-o dir] [-format csv|json|sarif] [-fail-under N] [-q] [-k keyphrase]
         [-site] [-crawl] [-sitemap url] [-limit N] [-serve :port] [-mcp] [-allow-private] <url or file>

Flag	Meaning
`-format csv\|json\|sarif`	Report format. `json` is the same object `/api/scan` returns, `sarif` is SARIF 2.1.0 for GitHub code scanning. Default `csv`.
`-fail-under N`	Exit 1 and name every page whose overall score is below N.
`-sitemap URL`	Audit the pages a sitemap lists. Sitemap indexes are followed.
`-site`	Also run the 7 site checks (robots.txt, AI crawlers, llms.txt).
`-crawl`	Follow internal links, up to `-limit` pages (default 20).
`-k`	Focus keyphrase. Only the edge API scores it today; the offline engine ignores it.
`-o`, `-q`	Report directory; `-q` hides the failing-check list.
`-serve 127.0.0.1:8080`	Local API and web UI. Bind to localhost; `:8080` listens on every interface.
`-mcp`	MCP server over stdio.
`-allow-private`	Allow localhost and private-network targets. Without it every fetch, including crawl and sitemap links and MCP, refuses non-public hosts, ignores `HTTPS_PROXY`/`HTTP_PROXY`, and only connects to ports 80 and 443. With it the CLI uses a plain HTTP client: no address guard, any port, proxy variables honoured. `-serve` is always guarded and ignores this flag.

findable -q -format sarif -fail-under 70 https://example.com
findable -sitemap https://example.com/sitemap.xml -limit 50
findable -site -crawl -limit 10 https://example.com

MCP for agents

Add to Claude Desktop, Cursor or Windsurf:

{ "mcpServers": { "findable": { "command": "findable", "args": ["-mcp"] } } }

No Go toolchain? Build the MCP server from source: (cd mcp && bun install && bun run build), then use { "command": "node", "args": ["/path/to/findable/mcp/dist/index.js"] }.

Tools: audit_page (URL or file), audit_html_content (raw HTML, no network), crawl_site, generate_csv_report. Prompt: seo_audit_prompt.

API

Hosted at https://findable.page (source: findable-page/findable-page), or run your own local server with findable -serve 127.0.0.1:8080.

curl -s -X POST https://findable.page/api/scan \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","keyphrase":"example","site":true}'

/api/scan only fetches public hosts: ports 80 and 443, 5 redirects, 10 seconds, 5 MB, rate limited. See SECURITY.md.

GitHub Action

permissions:
  security-events: write
steps:
  - uses: findable-page/[email protected]
    with:
      url: https://example.com
      fail-under: 70
      args: -site

The action builds the CLI, uploads failing checks to code scanning as SARIF, then fails the job below fail-under.

Development

git clone https://github.com/findable-page/findable && cd findable
(cd mcp && bun install)
make test

See CONTRIBUTING.md and CHANGELOG.md. testdata/ holds sample pages.

License

MIT