Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Geoa — Get found in ChatGPT

REMOTE · GEOA.APP

Check whether ChatGPT, Gemini and Perplexity recommend a business, and get fixes for its website.

Available components

72 Trust /100

Last scanned (4 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1392 tokens (~107/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 23 Oct 26 +1
    • Tool “geoa_account_status” rewrote its description, which is the text the model reads security
    • Tool “geoa_ai_visibility” rewrote its description, which is the text the model reads security
    • Tool “geoa_draft_from_gap” rewrote its description, which is the text the model reads security
    • Tool “geoa_fix_backlog” rewrote its description, which is the text the model reads security
    • Tool “geoa_pending_fixes” rewrote its description, which is the text the model reads security
    • Tool “geoa_radar_enrich” rewrote its description, which is the text the model reads security
    • Tool “geoa_radar_find_prospects” rewrote its description, which is the text the model reads security
    • Tool “geoa_radar_score_prospects” rewrote its description, which is the text the model reads security
    • Tool “geoa_ready_articles” rewrote its description, which is the text the model reads security
    • Tool “geoa_report_article_published” rewrote its description, which is the text the model reads security
    • Tool “geoa_report_fixes_live” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 22 Oct 26 71

    First indexed and scored.

Diagnostics

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 23 Oct 2026 · Probed https://geoa.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=geoa.app CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 7dceedb1052bf79d13349f5fbce969db
SANs: geoa.app, *.geoa.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of geoa.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
geoa.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' plausible.io cdn.jsdelivr.net unpkg.com cdn.cookiepilot.io www.clarity.ms *.clarity.ms 'unsafe-inline' 'unsafe-eval'; style-src 'self' fonts.googleapis.com 'unsafe-inline'; font-src 'self' data: fonts.gstatic.com; connect-src 'self' plausible.io cookiepilot.io api.cookiepilot.io cdn.cookiepilot.io *.clarity.ms https://c.bing.com; img-src 'self' data: plausible.io cdn.cookiepilot.io *.clarity.ms launchpadly.co; frame-src 'self' https://www.youtube.com https://www.youtube-nocookie.com; media-src 'self'; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://geoa.app/mcp Verified 200
http (plaintext) http://geoa.app/mcp HTTPS enforced 301 https://geoa.app/mcp
MCP tools · 13 exposed · ~1,392 tokens

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 →

Tool Tokens
geoa_account_status ~33

Your geoa plan and usage (articles used/remaining this month). Requires sign-in to a geoa account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

geoa_ai_visibility ~78

Your brand's AI visibility from geoa's stored scans: is your company mentioned when people ask ChatGPT, Claude, Gemini or Perplexity? Returns mention rate per engine, the top visibility gaps, and which competitors are cited instead. Reads stored scan results only (no live engine calls). Requires sign-in to a geoa account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

geoa_draft_from_gap ~142

Create a source-verified article draft from an AI-visibility gap (e.g. a question from geoa_ai_visibility). The draft is generated with the customer's Brand Brain, source-verified by the Gate and scored by the Coach — and lands as a DRAFT in Content Studio; nothing is published automatically. Requires a sign-in to a geoa account; counts against the plan's article quota.

NameTypeReqDescription
cited_insteadarray–Competitor domains cited instead (from geoa_ai_visibility)
languagestring–da (default), no, sv or en
questionstringyesThe question/topic the draft should answer

No output schema declared.

No examples provided.

geoa_fix_backlog ~87

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. Every fix is closed by MEASUREMENT, never by claim. Read-only — act on fixes in the geoa dashboard. Requires sign-in to a geoa account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

geoa_geo_score ~93

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. Returns the total score, a grade, and the 3 weakest dimensions (full 15-dimension report requires a geoa account). Results are cached for 6 hours per domain.

NameTypeReqDescription
domainstringyesThe domain, e.g. 'example.com'

No output schema declared.

No examples provided.

geoa_pending_fixes ~95

The approved geoa fixes that are NOT yet written into this site's code, for sites built or updated with Claude Code. Each item carries the path (url_pattern), the new value to write, and what geoa measured there before, so you can find the right spot in the repo. A human already approved every item in geoa before it appears here. Read-only. Requires sign-in to a geoa account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

geoa_radar_enrich ~124

Enrich a company domain with verified registry data via Nordic Data (CVR/Brønnøysund/Bolagsverket etc.): registered name, company number, industry code, legal form, status. Counts against the plan's monthly lookup quota. Requires sign-in to a geoa account. Company-level data only — never persons.

NameTypeReqDescription
company_namestring–Company name if you know it (improves matching)
countrystring–dk (default), no, se, fi …
domainstringyesCompany domain

No output schema declared.

No examples provided.

geoa_radar_find_prospects ~155

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). Returns a ranked candidate list and a search_id for scoring. Counts against the plan's monthly prospect-search quota. Requires sign-in to a geoa account. Research only — geoa never contacts anyone on your behalf.

NameTypeReqDescription
citystring–City (optional)
countrystring–dk (default), no, se or fi
industrystring–Industry, e.g. 'vvs' or 'revisor'
seed_domainsarray–Your own candidate domains instead of discovery

No output schema declared.

No examples provided.

geoa_radar_score_prospects ~92

GEO-score the prospects in a Radar search (search_id from geoa_radar_find_prospects): healthy company + weak AI visibility = highest sales priority. Scoring runs in the background — call again with the same search_id to fetch results. Requires sign-in to a geoa account.

NameTypeReqDescription
search_idstringyesSearch id from geoa_radar_find_prospects

No output schema declared.

No examples provided.

geoa_ready_articles ~68

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, for sites built or updated with Claude Code. Read-only. Requires sign-in to a geoa account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

geoa_report_article_published ~117

Report that a ready article is now published at a live URL. geoa starts measuring the article's effect on that URL and cross-links the other articles in its cluster to it. Without this, the article stays unpublished in geoa and keeps coming back as ready. Writes to the customer's geoa account. Requires sign-in to a geoa account.

NameTypeReqDescription
article_idstringyesThe article id from geoa_ready_articles
urlstringyesThe live URL the article is published at (https://…)

No output schema declared.

No examples provided.

geoa_report_fixes_live ~183

Report that you have written the given approved fixes into the site and DEPLOYED them. geoa then fetches the public page as an ordinary visitor and confirms the change is really there — a fix is closed by measurement, never by claim, so a report made before the change is live stays unconfirmed. Writes to the customer's geoa account. Requires sign-in to a geoa account.

NameTypeReqDescription
commitstring–Optional commit SHA or reference the change landed in
deployed_urlstring–Optional URL where the change is now live
fix_idsarrayyesThe fix_ids you wrote in and deployed (from geoa_pending_fixes)
rolled_backobject–Optional {fix_id: reason} for changes you reverted instead of keeping
tool_versionstring–Optional client/tool identifier for the report

No output schema declared.

No examples provided.

geoa_verify_claim ~125

Verify a numeric claim against its cited source (geoa's Gate). Fetches the source page and checks mechanically whether the number appears there and whether the source is circular; with a geoa account it also checks SEMANTICALLY whether the source actually supports the claim. Returns a verdict: supported | unsupported | self_referential | unverifiable, plus the matched evidence.

NameTypeReqDescription
claimstringyesThe claim containing the number, e.g. '68% of searches end without a click'
source_urlstring–URL of the source the claim cites

No output schema declared.

No examples provided.

Install

How do I install the Geoa — Get found in ChatGPT MCP server?

Geoa — Get found in ChatGPT is a hosted endpoint at https://geoa.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · geoa.app

# add to Claude Code
claude mcp add --transport http app-geoa-geoa 'https://geoa.app/mcp'
Common questions

What is the Geoa — Get found in ChatGPT MCP server?

Geoa — Get found in ChatGPT is an MCP server listed in the public MCP registry as app.geoa/geoa. Check whether ChatGPT, Gemini and Perplexity recommend a business, and get fixes for its website. This page covers its hosted endpoint (https://geoa.app/mcp).

Is the Geoa — Get found in ChatGPT MCP server safe to use?

Geoa — Get found in ChatGPT scores 72 out of 100 on VerifyMCP. 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 Geoa — Get found in ChatGPT MCP server expose?

Geoa — Get found in ChatGPT exposes 13 tools: geoa_verify_claim, geoa_geo_score, geoa_ai_visibility, geoa_draft_from_gap, geoa_fix_backlog, and 8 more. Their descriptions and schemas cost roughly 1,392 tokens of context every time the server is loaded.

Does the Geoa — Get found in ChatGPT MCP server require authentication?

No. We connected to Geoa — Get found in ChatGPT without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Geoa — Get found in ChatGPT MCP server still maintained?

Geoa — Get found in ChatGPT is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.