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.

io.github.DigitalCurrensy/aio-geo

REMOTE · WWW.AIOGEOPROTOCOL.COM · 2 COMPONENTS

AIO.GEO: audit, dry-run fixes, rescore, doctor. Remote + stdio. Not LLM rankings.

0 this week 88 Trust /100

Last scanned (21 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 16 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 Security83
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 564 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; 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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Sept 26 88
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Aug 26 0
    • Server version: 0.3.5 → 0.3.7 functional
  • 15 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Aug 26 0

    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 16 Oct 2026 · Probed https://www.aiogeoprotocol.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.aiogeoprotocol.com CN=YR1,O=Let's Encrypt,C=US 11 Oct 2026 9 Jan 2027 RSA 2048 SHA256-RSA 5b1bd8a9eee5a4f25af1050f97ebfbf3cf3
SANs: www.aiogeoprotocol.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of www.aiogeoprotocol.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
aiogeoprotocol.com. present 18308, 20716 13, 13 Verified
www.aiogeoprotocol.com. Verified address RRset verified with the apex keys
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=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.aiogeoprotocol.com/mcp Verified 200
http (plaintext) http://www.aiogeoprotocol.com/mcp HTTPS enforced 308 https://www.aiogeoprotocol.com/mcp
MCP tools · 6 exposed · ~515 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
apply_fix ~114

Generate a structural fix pack for a public domain. Public calls stay dry-run (no writes). Set dryRun false only with an operator key.

NameTypeReqDescription
domainstring–Alias of url. Use either url or domain, not both.
dryRunboolean–When true (default) only preview the pack. Writes stay off on the public endpoint.
urlstring–Public domain or https URL to inspect (for example example.com or https://example.com). Localhost and private IPs are blocked.
NameTypeReqDescription
domainstring––
dryRunbooleanyesPublic endpoint always true — no files are written
errorstring––
filesarray–Proposed files in the dry-run pack
okbooleanyes–

No examples provided.

audit_url ~101

Run a structural AI Search Readiness audit for a public URL or domain. Returns pillar scores, recommendations, a brief link, and a CLI command. Not an LLM ranking. No API key required.

NameTypeReqDescription
domainstring–Alias of url. Use either url or domain, not both.
urlstring–Public domain or https URL to inspect (for example example.com or https://example.com). Localhost and private IPs are blocked.
NameTypeReqDescription
briefUrlstring–Shareable public brief URL
clistring–Matching CLI command
confidencenumber–0-1 crawl confidence
disclaimerstring––
domainstringyesNormalized hostname
isSyntheticboolean–True only if the crawl failed closed
methodologystring–Scoring methodology id
okbooleanyesTrue when the audit completed
overallScorenumberyesStructural readiness score 0-100. Not an LLM ranking.
persistedboolean–True if the scan was saved
pillarsarray–Per-pillar structural scores
recommendationsarray–Ranked structural gaps to fix
refusalstring–Ranking-refusal copy

No examples provided.

check_health ~23

Return environment and API health. Never returns secrets. No API key required.

Input schema present but exposes no named parameters.

NameTypeReqDescription
api_keystringyesset or unset — never the raw secret
healthobject–Ops health without secrets
refusalstring––
versionstringyes–

No examples provided.

get_brief ~93

Return an executive structural brief for a domain: score, top gaps, and a shareable brief path. Not an LLM ranking. No API key required.

NameTypeReqDescription
domainstring–Alias of url. Use either url or domain, not both.
urlstring–Public domain or https URL to inspect (for example example.com or https://example.com). Localhost and private IPs are blocked.
NameTypeReqDescription
domainstringyes–
okbooleanyes–
overallScorenumberyes–
pillarsarray––
recommendationsarray––
refusalstring––
sharePathstringyesRelative brief path, for example /brief?domain=example.com

No examples provided.

list_fixes ~90

Return a dry-run structural fix pack (robots, schema, anchors) for a public domain. No files are written. No API key required.

NameTypeReqDescription
domainstring–Alias of url. Use either url or domain, not both.
urlstring–Public domain or https URL to inspect (for example example.com or https://example.com). Localhost and private IPs are blocked.
NameTypeReqDescription
domainstring––
dryRunbooleanyesPublic endpoint always true — no files are written
errorstring––
filesarray–Proposed files in the dry-run pack
okbooleanyes–

No examples provided.

rescore_url ~94

Run a fresh public structural audit (rescore) for a URL or domain. Same engine as audit_url. Not an LLM ranking. No API key required.

NameTypeReqDescription
domainstring–Alias of url. Use either url or domain, not both.
urlstring–Public domain or https URL to inspect (for example example.com or https://example.com). Localhost and private IPs are blocked.
NameTypeReqDescription
briefUrlstring–Shareable public brief URL
clistring–Matching CLI command
confidencenumber–0-1 crawl confidence
disclaimerstring––
domainstringyesNormalized hostname
isSyntheticboolean–True only if the crawl failed closed
methodologystring–Scoring methodology id
okbooleanyesTrue when the audit completed
overallScorenumberyesStructural readiness score 0-100. Not an LLM ranking.
persistedboolean–True if the scan was saved
pillarsarray–Per-pillar structural scores
recommendationsarray–Ranked structural gaps to fix
refusalstring–Ranking-refusal copy

No examples provided.

Install

How do I install the io.github.DigitalCurrensy/aio-geo MCP server?

io.github.DigitalCurrensy/aio-geo is a hosted endpoint at https://www.aiogeoprotocol.com/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 · www.aiogeoprotocol.com

# add to Claude Code
claude mcp add --transport http digitalcurrensy-aio-geo 'https://www.aiogeoprotocol.com/mcp'
Common questions

What is the io.github.DigitalCurrensy/aio-geo MCP server?

io.github.DigitalCurrensy/aio-geo is an MCP server listed in the public MCP registry as io.github.DigitalCurrensy/aio-geo. AIO.GEO: audit, dry-run fixes, rescore, doctor. Remote + stdio. Not LLM rankings. This page covers its hosted endpoint (https://www.aiogeoprotocol.com/mcp).

Is the io.github.DigitalCurrensy/aio-geo MCP server safe to use?

io.github.DigitalCurrensy/aio-geo scores 88 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 io.github.DigitalCurrensy/aio-geo MCP server expose?

io.github.DigitalCurrensy/aio-geo exposes 6 tools: audit_url, list_fixes, apply_fix, rescore_url, check_health, get_brief. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.

Does the io.github.DigitalCurrensy/aio-geo MCP server require authentication?

No. We connected to io.github.DigitalCurrensy/aio-geo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.DigitalCurrensy/aio-geo MCP server still maintained?

io.github.DigitalCurrensy/aio-geo is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.