Glippy GEO
by JAN WILLEM BOBBINK(Community)
Visitor takeaway
58/100
Fair AI-discovery coverage across description, prompts, keywords, visuals, tool metadata, health, and freshness.
Routing category
Needs category
This listing is missing a primary category, which weakens browse placement and AI recommendation routing.
Connector evidence
Reachable
Tedix can reach this MCP endpoint and can show live capability evidence when tools are discovered.
Directory freshness
1d ago
Catalog metadata was refreshed 1d ago (October 22, 2026).
Description
Glippy is a website audit tool for marketers, SEO specialists and web developers. It checks how AI-ready and LLM-friendly a website is: can AI search engines and AI agents find it, read it, and cite it? Use it to optimize your website for AI search, also called AI SEO or Generative Engine Optimization (GEO). Name a website and Glippy returns an interactive report: - An overall GEO score and grade - 16 scored categories, including structured data, semantic HTML, machine readability, entity and authority signals, citability and content freshness - Which AI crawlers robots.txt blocks or allows - Whether the site publishes a sitemap and llms.txt - A prioritised list of fixes you can copy, or ask for drafts of You can also compare up to eight sites side by side, for example your site against competitors, and see who leads in each category. How Glippy fetches: it reads only public files of the site you name (the homepage, robots.txt, sitemap.xml, llms.txt and standard /.well-known discovery files), identifies itself as GlippyBot, and does not fetch a site whose robots.txt disallows GlippyBot. It analyses the homepage, not the whole site. It does not sign in anywhere, change anything on the site, or need an account.
Capabilities
No special capabilities listed
AI Agent Discovery
Glippy GEO is indexed by Tedix as a structured ai application listing for AI assistants, search crawlers, and users comparing agent-ready apps.
- Glippy GEO has no primary catalog category yet; Tedix treats this as a routing gap for browse and recommendation surfaces.
- Developer: JAN WILLEM BOBBINK.
- Connector type: AI-Powered App.
- Current connector status: Connected.
- Observed distribution channels: chatgpt.
- Available regions: US, FR, GB, ES, KR, IN.
Use this page to understand whether Glippy GEO is relevant for general AI app workflows in AI assistants.
For MCP discovery, this listing helps crawlers connect Glippy GEO to tool, resource, prompt, and server-health signals instead of treating it as a generic directory entry.
The canonical Tedix directory URL is https://tedix.dev/apps/glippy-geo/.
Crawlable Profile
Source and availability
Tedix identifies Glippy GEO from Upstream Mcp tool source; Store sources: ChatGPT app store; Distribution: Ecosystem Directory; Tenant install: A platform catalog operator must create or reconcile the base app before tenants can install this entry.. Availability is reported for US, FR, GB, ES, KR, IN.
- ChatGPT app storeAuth not flagged · RELEASED · US, FR, GB, ES, KR, IN
Auth, tools, and actions
Authentication: Open Access. No special capability flags are currently listed. Current MCP inventory reports 5 tools, 2 resources, and 0 prompts.
- Analyze domain for GEO readiness · Read-only action
Run a full GEO (Generative Engine Optimization) analysis of a public website the user names: 16 scored categories, robots.txt / llms.txt / sitemap discovery, AI-crawler rules, and prioritised recommendations. Analyses the homepage plus standard discovery files, not every page. Skips sites whose robots.txt disallows GlippyBot. Before analysing, decide what kind of page the site's homepage is (from what you know of the site or what the user said) and pass page_type: usually "homepage"; a news front or blog index is "index", a one-page local business site is "service", a single-product site is "product". Without it, checks that depend on the page type are shown but not scored. Decide before the first call: a re-run with another page_type is a new analysis and counts toward the per-site limit. Renders an interactive report widget.
- Check for llms.txt · Read-only action
Check whether a domain publishes an llms.txt file (one request) and return its contents. Note: llms.txt is an emerging proposal not yet consumed by major AI models. The full analysis gives a small credit in Machine Readability when one exists; a missing one is listed as information, not as a fix to make.
- Check robots.txt AI-crawler access · Read-only action
Read a domain's robots.txt (one request) and report which AI crawlers (training, search and user-triggered fetchers) it blocks or allows. This reports the stated policy only; it does not test what the site actually serves each crawler.
- Compare domains for GEO readiness · Read-only action
Analyse and rank 2-8 public websites the user names, side by side: overall scores, a per-category comparison matrix, discovery signals, and the top issues per site. Each site's homepage is analysed under the same rules as analyze_domain. Before analysing, decide what kind of page the site's homepage is (from what you know of the site or what the user said) and pass page_type: usually "homepage"; a news front or blog index is "index", a one-page local business site is "service", a single-product site is "product". Without it, checks that depend on the page type are shown but not scored. Decide before the first call: a re-run with another page_type is a new analysis and counts toward the per-site limit. Renders an interactive comparison widget.
- Quick GEO summary · Read-only action
Get a concise GEO readiness summary for a public website the user names: overall score, grade, top strengths, and the top issues to fix. Renders the report widget in summary form. Use analyze_domain for the full 16-category breakdown. Before analysing, decide what kind of page the site's homepage is (from what you know of the site or what the user said) and pass page_type: usually "homepage"; a news front or blog index is "index", a one-page local business site is "service", a single-product site is "product". Without it, checks that depend on the page type are shown but not scored. Decide before the first call: a re-run with another page_type is a new analysis and counts toward the per-site limit.
Verification freshness
- Catalog synced1d ago (October 22, 2026)
- Connector checked6h ago (October 23, 2026)
- MCP scanned6h ago (October 23, 2026)
- Directory updated1d ago (October 22, 2026)
Publisher Intelligence
Public trust signals for visitors and practical recommendations for publishers. Use this section to understand what Tedix can verify today and what would make the app easier for AI agents to find.
Visitor takeaway
58/100
Fair AI-discovery coverage across description, prompts, keywords, visuals, tool metadata, health, and freshness.
Routing category
Needs category
This listing is missing a primary category, which weakens browse placement and AI recommendation routing.
Connector evidence
Reachable
Tedix can reach this MCP endpoint and can show live capability evidence when tools are discovered.
Directory freshness
1d ago
Catalog metadata was refreshed 1d ago (October 22, 2026).
Server Statusglippy-geo v1.0.0
https://mcp.glippy.dev/mcpLast checked: 6h ago
Server Instructions
Glippy analyses how ready a public website is for AI answer engines and agents (Generative Engine Optimization). Use analyze_domain for a full scored report, get_geo_summary for a quick score, compare_domains to rank several sites, check_robots_txt for AI-crawler rules, and check_llms_txt for llms.txt. Only call these for a domain the user named. Glippy fetches only public files as GlippyBot, honours robots.txt, and analyses the homepage (not the whole site). Decide what kind of page that homepage is before the first call and pass it as page_type (usually "homepage"); without it, the checks that depend on the page type are shown but not scored. When a tool explains it did not fetch a site (robots.txt, rate limit, unreachable), relay that plainly and do not retry. Widget tools render interactive results: present the score, grade, and top recommendations, and offer to draft fixes. Never recommend renaming or 301-redirecting existing, established URLs to make slugs descriptive or match navigation labels; redirect only URLs that are actually broken.
Technical Details
Tools(5)
Showing 5 of 5 tools
| Flags | Test | ||||
|---|---|---|---|---|---|
analyze_domain | Run a full GEO (Generative Engine Optimization) analysis of a public website the user names: 16 scored categories, robots.txt / llms.txt / sitemap discovery, AI-crawler rules, and prioritised recommendations. Analyses the homepage plus standard discovery files, not every page. Skips sites whose robots.txt disallows GlippyBot. Before analysing, decide what kind of page the site's homepage is (from what you know of the site or what the user said) and pass page_type: usually "homepage"; a news front or blog index is "index", a one-page local business site is "service", a single-product site is "product". Without it, checks that depend on the page type are shown but not scored. Decide before the first call: a re-run with another page_type is a new analysis and counts toward the per-site limit. Renders an interactive report widget. | read-only | Not tested | — | — |
check_llms_txt | Check whether a domain publishes an llms.txt file (one request) and return its contents. Note: llms.txt is an emerging proposal not yet consumed by major AI models. The full analysis gives a small credit in Machine Readability when one exists; a missing one is listed as information, not as a fix to make. | read-only | Not tested | — | — |
check_robots_txt | Read a domain's robots.txt (one request) and report which AI crawlers (training, search and user-triggered fetchers) it blocks or allows. This reports the stated policy only; it does not test what the site actually serves each crawler. | read-only | Not tested | — | — |
compare_domains | Analyse and rank 2-8 public websites the user names, side by side: overall scores, a per-category comparison matrix, discovery signals, and the top issues per site. Each site's homepage is analysed under the same rules as analyze_domain. Before analysing, decide what kind of page the site's homepage is (from what you know of the site or what the user said) and pass page_type: usually "homepage"; a news front or blog index is "index", a one-page local business site is "service", a single-product site is "product". Without it, checks that depend on the page type are shown but not scored. Decide before the first call: a re-run with another page_type is a new analysis and counts toward the per-site limit. Renders an interactive comparison widget. | read-only | Not tested | — | — |
get_geo_summary | Get a concise GEO readiness summary for a public website the user names: overall score, grade, top strengths, and the top issues to fix. Renders the report widget in summary form. Use analyze_domain for the full 16-category breakdown. Before analysing, decide what kind of page the site's homepage is (from what you know of the site or what the user said) and pass page_type: usually "homepage"; a news front or blog index is "index", a one-page local business site is "service", a single-product site is "product". Without it, checks that depend on the page type are shown but not scored. Decide before the first call: a re-run with another page_type is a new analysis and counts toward the per-site limit. | read-only | Not tested | — | — |
Discoverability Score
Fair
58 / 100
How easily AI agents can find this app from its current catalog metadata.
- Description quality20/20
- Example prompts0/20
- Keyword coverage0/15
- Category clarity0/5
- Tool metadata20/20
- Visual assets8/20
- Endpoint health10/10
- Data freshness15/15
How to Improve
Add at least 2 example prompts. Prompt examples strongly improve app matching and click-through intent.
Increase keyword coverage (discovery + trigger) to improve retrieval for long-tail queries.
Choose a primary catalog category so visitors and AI agents can route this app into the right browse and recommendation surfaces.
Add at least 2 screenshots that show real workflows to increase confidence and conversion.
Technical Details
- Status
- ENABLED
- Type
- AI-Powered App
- Auth
- Open Access
- Listed on
- ChatGPT
- Added
- October 21, 2026
- Last synced
- 1d ago
- Last checked
- 6h ago
- Version
- 1.0.0
- Distribution
- Ecosystem Directory