Geoa — Get found in ChatGPT MCP server
app.geoa/geoageoa.appstreamable-httpv1.3.0Scanned
Check whether ChatGPT, Gemini and Perplexity recommend a business, and get fixes for its website.
13 tools: 12 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 8
- Can send data out · 1
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
12 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Geoa — Get found in ChatGPT MCP server can do
The Geoa — Get found in ChatGPT MCP server is published by geoa.app, a domain the MCP Registry verified. It has 13 tools. It can create or change data (12 tools: geoa_verify_claim, geoa_geo_score, geoa_ai_visibility, geoa_draft_from_gap and 8 more), but cannot delete data. 1 tool only reads.
8 tools bring in text other people can write (geoa_verify_claim, geoa_geo_score, geoa_draft_from_gap and 5 more); 1 tool can send data out of your system (geoa_report_article_published).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 8, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
13 tools
Changes things 12Claude Code: ask
geoa_ai_visibilityYour brand's AI visibility from geoa's stored scans: is your company mentioned when people ask ChatGPT, Claude, Gemini or Perplexity?No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: AI Visibility Report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
geoa_draft_from_gapCreate a source-verified article draft from an AI-visibility gap (e.g.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Draft Article from Visibility Gap
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
geoa_fix_backlogYour 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Fix Queue
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
geoa_geo_scoreGEO score for a domain: how ready the site is to be read, understood and cited by AI search engines, measured across 15 technical dimensions.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: GEO Score for Domain
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
geoa_pending_fixesThe approved geoa fixes that are NOT yet written into this site's code, for sites built or updated with Claude Code.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Approved Fixes Not Yet in the Code
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
geoa_radar_enrichEnrich 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.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Registry Enrich (Radar)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
geoa_radar_find_prospectsFind 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…Reads text others write1 finding
Why it is in this group
- The name "geoa_radar_find_prospects" says "find": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "geoa_radar_find_prospects" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "geoa_radar_find_prospects" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find B2B Prospects (Radar)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
geoa_radar_score_prospectsGEO-score the prospects in a Radar search (search_id from geoa_radar_find_prospects): healthy company + weak AI visibility = highest sales priority.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Score Prospects (Radar)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
geoa_ready_articlesContent 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 bui…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Articles Ready to Publish
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
geoa_report_article_publishedReport that a ready article is now published at a live URL.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
Annotations the server declares
- title: Report Article Published
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
geoa_report_fixes_liveReport that you have written the given approved fixes into the site and DEPLOYED them.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Report Fixes Written and Deployed
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
geoa_verify_claimVerify a numeric claim against its cited source (geoa's Gate).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify Claim Against Source
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 1Show 1 read-only tool
geoa_account_statusYour geoa plan and usage (articles used/remaining this month).No findings
Why it is in this group
- The name "geoa_account_status" says "status": a word for reading.
Description, as the server wrote it Your geoa plan and usage (articles used/remaining this month). Requires sign-in to a geoa account.
Annotations the server declares
- title: Account Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 12
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://geoa.app/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://geoa.app
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://geoa.app/mcp: tools/list returned 13 tools to an anonymous client, including geoa_verify_claim (write), geoa_geo_score (write), geoa_ai_visibility (write), geoa_draft_from_gap (write), geoa_fix_backlog (write) and 7 more
Findings
Matches of fixed checks, with the text they matched.
The server marks "geoa_radar_find_prospects" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "geoa_radar_find_prospects" says "find": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools11 changed.~11 changedView diff
- Changed:geoa_account_statusOnly readsdescription
- Changed:geoa_ai_visibilityChanges thingsdescription
- Changed:geoa_draft_from_gapChanges thingsdescription
- Changed:geoa_fix_backlogChanges thingsdescription
- Changed:geoa_pending_fixesChanges thingsdescription
- Changed:geoa_radar_enrichChanges thingsdescription
- Changed:geoa_radar_find_prospectsChanges thingsdescription
- Changed:geoa_radar_score_prospectsChanges thingsdescription
- Changed:geoa_ready_articlesChanges thingsdescription
- Changed:geoa_report_article_publishedChanges thingsdescriptionannotations
- Changed:geoa_report_fixes_liveChanges thingsdescriptionannotations
Tools13 changed.~13 changedView diff
- Changed:geoa_account_statusOnly readstitle
- Changed:geoa_ai_visibilityChanges thingstitle
- Changed:geoa_draft_from_gapChanges thingstitle
- Changed:geoa_fix_backlogChanges thingstitle
- Changed:geoa_geo_scoreChanges thingstitle
- Changed:geoa_pending_fixesChanges thingstitle
- Changed:geoa_radar_enrichChanges thingstitle
- Changed:geoa_radar_find_prospectsChanges thingstitle
- Changed:geoa_radar_score_prospectsChanges thingstitle
- Changed:geoa_ready_articlesChanges thingstitle
- Changed:geoa_report_article_publishedChanges thingstitle
- Changed:geoa_report_fixes_liveChanges thingstitle
- Changed:geoa_verify_claimChanges thingstitle
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http geoa https://geoa.app/mcpclaude mcp add --transport http geoa https://geoa.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__geoa__geoa_account_status"
],
"ask": [
"mcp__geoa__geoa_verify_claim",
"mcp__geoa__geoa_geo_score",
"mcp__geoa__geoa_ai_visibility",
"mcp__geoa__geoa_draft_from_gap",
"mcp__geoa__geoa_fix_backlog",
"mcp__geoa__geoa_pending_fixes",
"mcp__geoa__geoa_report_fixes_live",
"mcp__geoa__geoa_ready_articles",
"mcp__geoa__geoa_report_article_published",
"mcp__geoa__geoa_radar_find_prospects",
"mcp__geoa__geoa_radar_score_prospects",
"mcp__geoa__geoa_radar_enrich"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as geoa. Review it before you use it.
Capability tags behind 8 rules
- mcp__geoa__geoa_verify_claim untrusted-input
- mcp__geoa__geoa_geo_score untrusted-input
- mcp__geoa__geoa_draft_from_gap untrusted-input
- mcp__geoa__geoa_report_fixes_live untrusted-input
- mcp__geoa__geoa_report_article_published untrusted-input, outbound
- mcp__geoa__geoa_radar_find_prospects untrusted-input
- mcp__geoa__geoa_radar_score_prospects untrusted-input
- mcp__geoa__geoa_radar_enrich untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.geoa/geoa/verify?hash=0dd72658899bb13cca01eec29788350c449ca70e0e1c24cf838d40779335dff4" | jq -e '.changed == false'Pinned hash 0dd72658899b, from Nov 8, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.geoa/geoa/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.geoa/geoa)Source: MCP Registry. Synced Oct 22, 2026, 12:17 UTC.
Geoa — Get found in ChatGPT MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Geoa — Get found in ChatGPT MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 12 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Geoa — Get found in ChatGPT MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Geoa — Get found in ChatGPT MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Geoa — Get found in ChatGPT MCP server have?
- 13 tools: 12 write, 1 read. geoa_verify_claim, geoa_geo_score, geoa_ai_visibility, geoa_draft_from_gap, geoa_fix_backlog, geoa_pending_fixes, geoa_report_fixes_live, geoa_ready_articles and 5 more.
Does the Geoa — Get found in ChatGPT MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Geoa — Get found in ChatGPT MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): geoa_report_article_published.
Has the Geoa — Get found in ChatGPT MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.