← Registry

Marketing

geoa.app

An AI search visibility (GEO) toolkit that audits domains, verifies claims, tracks brand mentions across AI assistants, and generates source-verified content and prioritized fixes.

1 endpoint13 known toolsFirst detected October 22, 2026Last detected October 22, 2026

ENDPOINT 1

https://geoa.app/mcp

No auth detected

MCP server metadata

Name
geoa
Version
1.2.0
Capabilities
tools

Known tools 13

geoa_verify_claim

Verify a numeric claim against its cited source (geoa's Gate).

Inferred read-only
geoa_geo_score

GEO score for a domain: how ready the site is to be read, understood and cited by AI search engines, measured across 15 technical dimensions.

Inferred read-only
geoa_ai_visibility

Your brand's AI visibility from geoa's stored scans: is your company mentioned when people ask ChatGPT, Claude, Gemini or Perplexity?

Inferred read-only
geoa_draft_from_gap

Create a source-verified article draft from an AI-visibility gap (e.

Potential side effects
geoa_fix_backlog

Your current geoa fix queue: the 5 highest-priority GEO fixes served right now (title, effort, impact, delivery channel) plus how many wait in the backlog and how many are verified done.

Inferred read-only
geoa_account_status

Your geoa plan and usage (articles used/remaining this month).

Inferred read-only
geoa_pending_fixes

The approved geoa fixes that are NOT yet written into this site's code — use this when you build or update the customer's website with Claude Code.

Potential side effects
geoa_report_fixes_live

Report that you have written the given approved fixes into the site and DEPLOYED them.

Inferred read-only
geoa_ready_articles

Content Studio articles that are approved and ready to go into the site: title, body (markdown and HTML), meta description, FAQ, JSON-LD and the EU AI Act disclosure.

Inferred read-only
geoa_report_article_published

Report that a ready article is now published at a live URL.

Inferred read-only
geoa_radar_find_prospects

Find B2B prospect companies for a workspace via geoa Radar: discovery by industry+city (or your own seed domains), registry-qualified with Nordic Data (official business registries).

Inferred read-only
geoa_radar_score_prospects

GEO-score the prospects in a Radar search (search_id from geoa_radar_find_prospects): healthy company + weak AI visibility = highest sales priority.

Inferred read-only
geoa_radar_enrich

Enrich a company domain with verified registry data via Nordic Data (CVR/Brønnøysund/Bolagsverket etc.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.geoa]
url = "https://geoa.app/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "geoa": {
      "type": "http",
      "url": "https://geoa.app/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: geoa
Remote MCP URL: https://geoa.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "geoa": {
      "url": "https://geoa.app/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "geoa": {
      "type": "http",
      "url": "https://geoa.app/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "geoa",
  "transport": "streamable-http",
  "url": "https://geoa.app/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.