# aipozi (remote · aipozi.com)

Daily AI visibility: who ChatGPT, Claude, Gemini and Perplexity name instead of you. Domain tools.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `aipozi.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-aipozi-aipozi/aipozi.md), [page](https://verifymcp.io/servers/com-aipozi-aipozi/aipozi)

## Channel facts

- Endpoint: `https://aipozi.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2413 tokens (~160/item across 15 items; 14 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the aipozi MCP server?

aipozi is a hosted endpoint at https://aipozi.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.

### Claude

```bash
claude mcp add --transport http com-aipozi-aipozi 'https://aipozi.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-aipozi-aipozi": {
      "url": "https://aipozi.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-aipozi-aipozi": {
      "type": "http",
      "url": "https://aipozi.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-aipozi-aipozi]
url = "https://aipozi.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aipozi-aipozi": {
      "type": "remote",
      "url": "https://aipozi.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-aipozi-aipozi --url 'https://aipozi.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-aipozi-aipozi:
    url: "https://aipozi.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-aipozi-aipozi": {
      "Transport": "http",
      "Url": "https://aipozi.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-aipozi-aipozi -t streamable-http -u 'https://aipozi.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-aipozi-aipozi": {
      "type": "http",
      "url": "https://aipozi.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-06 (score 78, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (14)

### `briefing` (~231 tokens)

Today's briefing

The daily aipozi read for all of the person's sites, or one: for each site, how many of today's answers from ChatGPT, Claude, Gemini and Perplexity named it (and gave its address) and the change since yesterday, per AI; the questions it was named for today and by which AI; the questions lost since yesterday; new rivals (name, age, DR, what they do, which questions they took); the site's DR; what changed since a move was shipped; and today's best move. Stamped with the check time. Use it first for "how am I doing", "read me my aipozi briefing", or a scheduled morning briefing (for example a task every weekday at 07:00: "run daily_briefing from aipozi"). Checks run every morning at 05:00 GMT; this tool never runs one.

Input parameters:

- `site` (string): Which of your sites: its domain ("biotree.bio"), its id from list_my_sites ("biotree-bio") or its name. Leave it out when the person has one site.

Output parameters:

- `date` (string): Today (YYYY-MM-DD).
- `drCredit` (string): Domain Rating by Ahrefs (ahrefs.com).
- `message` (string): When view is "none": what to tell the person.
- `sites` (array): One per site.
- `totals` (object): All sites: { named, answers, delta }.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `list_my_sites` (~74 tokens)

My sites

Every site the person watches in aipozi: its id, plan (paid or free), market, last check time, how many answers named it and gave its address, per AI, its DR and the last 7 days. Use it to see which sites exist, or to get a site id for another tool.

Output parameters:

- `message` (string): When view is "none": what to tell the person.
- `sites` (array): { siteId, domain, brand, plan, market, lastCheck, named, linked, answers, perEngine, dr, trend7, freshness }.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `questions` (~153 tokens)

My questions and results

One site's questions (up to 10) and, for each, the result from each AI in the latest check (named with the address, named, address given but not named, not named), how many AIs named the site on each of the last 7 checks, and who was named instead. Use it for "which of my questions did ChatGPT name me for?" or "which questions is Linktree winning?". For an AI's exact words on one question, use ai_answer.

Input parameters:

- `site` (string): Which of your sites: its domain ("biotree.bio"), its id from list_my_sites ("biotree-bio") or its name. Leave it out when the person has one site.

Output parameters:

- `date` (string): The check day.
- `domain` (string): The site.
- `message` (string): When view is "none": what to tell the person.
- `questions` (array): { promptId, question, results: { chatgpt, claude, gemini, perplexity }, namedBy, last7, namedInstead }.
- `siteId` (string): The site id.
- `stamp` (string): "Checked 05:01 GMT".
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `ai_answer` (~197 tokens)

What the AI said

One question and one AI: that AI's answer word for word, exactly as stored, with the pages it cited, from the latest check or a given date. Quote it as that AI's words. Use it for "show me exactly what ChatGPT said" or "who did Perplexity recommend for the Comrades question?".

Input parameters:

- `ai` (string, required): The AI: chatgpt, claude, gemini or perplexity.
- `date` (string): A check day, YYYY-MM-DD. Leave it out for the latest check.
- `question` (string, required): The question: its id ("p03"), its number in the list ("3"), or words from it ("Comrades").
- `site` (string): Which of your sites: its domain ("biotree.bio"), its id from list_my_sites ("biotree-bio") or its name. Leave it out when the person has one site.

Output parameters:

- `aiLabel` (string): ChatGPT, Claude, Gemini or Perplexity.
- `answerText` (string): The answer, word for word.
- `citations` (array): { url, title, domain }.
- `date` (string): The check day.
- `domain` (string): The site.
- `message` (string): When view is "none": what to tell the person.
- `question` (string): The question as asked.
- `result` (string): named, with your address | named | your address given, not named | not named.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `rivals` (~129 tokens)

Who the AIs recommend instead

For one site, or all of them: who ChatGPT, Claude, Gemini and Perplexity recommend instead, from the latest check. Each rival's name and domain, what they do, domain age, DR, how often each AI named them, the questions they won, first seen, the trend and a New flag for young sites. The person's own DR heads the list. Use it for "who are my competitors?" or "which new sites are taking my questions?".

Input parameters:

- `site` (string): One of your sites (domain, id or name). Leave it out for all of them.

Output parameters:

- `drCredit` (string): Domain Rating by Ahrefs (ahrefs.com).
- `message` (string): When view is "none": what to tell the person.
- `sites` (array): { siteId, domain, you: { domain, dr, named, answers }, date, rivals: [{ name, domain, whatTheyDo, ageDays, dr, isNew, namedCount, perEngine, questionsWon, firstSeen, trend }] }.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `rival_detail` (~149 tokens)

One rival up close

One rival from the person's own checks: its age and registrar, DR, what it does, and every question and AI where it was named and the person's site was not, with that AI's words about it. Use it for "how old is that site and what's its DR?" about a rival, or "what did the AIs say about Linktree?". Rivals are seen only through the person's own questions; for any other site use domain_age and domain_rating.

Input parameters:

- `rival` (string, required): The rival's name or domain, e.g. "Linktree" or "heya.page".
- `site` (string): One of your sites, if the rival is in one site's list.

Output parameters:

- `drCredit` (string): Domain Rating by Ahrefs (ahrefs.com).
- `message` (string): When view is "none": what to tell the person.
- `rival` (object): { name, domain, whatTheyDo, ageDays, registeredAt, registrar, dr, namedCount, perEngine, questionsWon, namedOverYou: [{ question, aiLabel, quotes }] }.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `trend` (~106 tokens)

How I've moved

Daily named and linked counts per site and per AI over 7, 30 or 90 days, with the moves marked done on the timeline and what changed since each. Use it for "how have I moved this month?" or "did the comparison page work?".

Input parameters:

- `days` (integer): 7, 30 or 90. Default 7.
- `site` (string): One of your sites (domain, id or name). Leave it out for all of them.

Output parameters:

- `days` (number): The window.
- `message` (string): When view is "none": what to tell the person.
- `sites` (array): { siteId, domain, series: [{ date, named, linked, answers, perEngine }], moves, sinceShipped }.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `domain_rating` (~77 tokens)

Domain Rating

Ahrefs Domain Rating (0 to 100) for up to 25 domains, anyone's. Free, no sign-in. Every answer carries "Domain Rating by Ahrefs (ahrefs.com)"; show it with the numbers.

Input parameters:

- `domains` (array, required): Domains, e.g. ["heya.page", "linktr.ee"].

Output parameters:

- `drCredit` (string): Domain Rating by Ahrefs (ahrefs.com).
- `message` (string): When view is "none": what to tell the person.
- `results` (array): { domain, dr } (dr null when Ahrefs has no rating).
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `action_plan` (~148 tokens)

What to improve

One site's plan from its latest check: why each AI does or doesn't name it (in plain words, from the real answers) and the moves, ranked by how many questions and AIs each can win, with the rivals each move beats and the pages the AIs read instead. Use it for "what should I improve first on biotree.bio?". To hand a move to a coding session, use build_prompt; when it has shipped, mark_move_done.

Input parameters:

- `site` (string): Which of your sites: its domain ("biotree.bio"), its id from list_my_sites ("biotree-bio") or its name. Leave it out when the person has one site.

Output parameters:

- `date` (string): The check the plan comes from.
- `domain` (string): The site.
- `locked` (boolean): True on a free site: move 1 in full, the rest locked.
- `message` (string): When view is "none": what to tell the person.
- `moves` (array): { id, rank, kind, title, locked, detail, impact, targets, rival, evidence, hasBuildPrompt, done }.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).
- `why` (array): { ai, label, why }.

### `build_prompt` (~211 tokens)

Hand a move to my coding session

One move of a site's plan as a complete, self-contained brief for a coding agent (Claude Code, Cursor): the goal, the page or change, the exact questions it targets and which AIs missed them, the rivals recommended, the pages the AIs read (to study, not copy), page anatomy and schema, what not to do (no invented facts, prices or reviews), and how aipozi will measure it. In a coding session opened on the site's repo, implement it, then call mark_move_done. Default: the top move. Paid sites only, as in the app.

Input parameters:

- `move` (string): The move id from action_plan or briefing ("comparison", "page-p03"), or its rank ("1"). Leave it out for the top move.
- `site` (string): Which of your sites: its domain ("biotree.bio"), its id from list_my_sites ("biotree-bio") or its name. Leave it out when the person has one site.

Output parameters:

- `domain` (string): The site.
- `measure` (string): How aipozi measures it and the mark_move_done call to make.
- `message` (string): When view is "none": what to tell the person.
- `move` (object): { id, rank, title, kind, targets }.
- `prompt` (string): The brief, ready to paste or act on.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `mark_move_done` (~176 tokens)

I've shipped it

Records that a move has shipped: today's date and, optionally, the URL of the new page. From the next morning's check, briefing and trend show what changed since. Not destructive; undo with undo: true. The only tool that writes. Use it after the person (or their coding session) has shipped the move.

Input parameters:

- `move` (string, required): The move id ("comparison", "page-p03") or rank ("1").
- `site` (string): Which of your sites: its domain ("biotree.bio"), its id from list_my_sites ("biotree-bio") or its name. Leave it out when the person has one site.
- `undo` (boolean): true to take back a mark made by mistake.
- `url` (string): The shipped page's URL, if there is one.

Output parameters:

- `day` (string): The day it was marked.
- `domain` (string): The site.
- `done` (boolean): Marked done (false after an undo).
- `message` (string): When view is "none": what to tell the person.
- `move` (object): { id, title }.
- `url` (string|null): The page.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `check_domain` (~306 tokens)

Check domain availability

Is a domain name free? Use it whenever someone names an app, product or company, asks "find me a name with a free domain", "is there a .com for…", or "is X taken". Asks each registry for its own record, live (RDAP, else the registry's WHOIS). One name: across .com, .ai, .io, .app, .dev and more, or the extensions given. Brainstorming: pass up to 10 candidates in names and get them on .com, .ai, .io, .app and .dev, free ones first. Each result: available or not registered (with a registrar link), taken (with its registration date and age), or couldn't check. Free, no sign-in. Always use this for availability; never guess from DNS or memory. aipozi doesn't register names.

Input parameters:

- `extensions` (array): Extensions to check, e.g. ["ai", "io", "co.za"].
- `name` (string): One name ("livedot") or a domain ("livedot.ai"). With an extension, only that one is checked unless extensions are given.
- `names` (array): Up to 10 candidate names to compare when naming something, e.g. ["livedot", "dotlive", "followdot"]. Checked on .com, .ai, .io, .app and .dev unless extensions are given (up to 6).

Output parameters:

- `label` (string): The name searched.
- `message` (string): When view is "none": what to tell the person.
- `results` (array): { domain, tld, status: available|premium|unregistered|unavailable|taken|unknown, price, registeredAt, ageDays, registerUrl, checkedAt }.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `domain_age` (~144 tokens)

WHOIS lookup: how old is a website

A WHOIS / RDAP lookup for any domain: registration date and age, registrar, expiry, status (including expired and being deleted, with an estimated drop date), name servers and who hosts it, read live from the registry's own record (RDAP, else WHOIS). Plus its Ahrefs Domain Rating. Never owner details. Free, no sign-in. Use it for "whois heya.page", "how old is this site", "who is it registered with", "when does it expire", "is this domain expiring", "who hosts it".

Input parameters:

- `domain` (string, required): A domain or a link, e.g. "heya.page".

Output parameters:

- `ageDays` (number|null): Days since registration.
- `domain` (string): The registrable domain.
- `dr` (number|null): Ahrefs Domain Rating.
- `drCredit` (string): Domain Rating by Ahrefs (ahrefs.com).
- `expiresAt` (string|null): YYYY-MM-DD.
- `found` (boolean): The registry has a record.
- `message` (string): When view is "none": what to tell the person.
- `nameservers` (array): Name servers.
- `registeredAt` (string|null): YYYY-MM-DD.
- `registrar` (string|null): The registrar.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

### `ai_crawler_access` (~89 tokens)

Can AI read this site

Whether each AI's crawlers (OpenAI, Anthropic, Perplexity, Google, Microsoft; search, user and training bots) are allowed by a site's robots.txt, read live, and the exact lines to add when a search crawler is blocked. Free, no sign-in.

Input parameters:

- `domain` (string, required): A domain or a link, e.g. "biotree.bio".

Output parameters:

- `blocksSearch` (boolean): A search or user bot is blocked.
- `bots` (array): { bot, company, engine, purpose, status: allowed|blocked|partial|unknown, blockedPaths }.
- `domain` (string): The site.
- `finding` (string|null): What is blocked, in plain words.
- `fix` (string|null): The robots.txt lines to add.
- `message` (string): When view is "none": what to tell the person.
- `robotsFound` (boolean): A robots.txt exists.
- `view` (string): What this answer is; "none" for a question back, a plain no, or nothing there yet (see message).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-aipozi-aipozi/aipozi#diagnostics

## Score history

- 2026-11-21: 85
- 2026-11-20: 85
- 2026-11-19: 84
- 2026-11-18: 84
- 2026-11-17: 84
- 2026-11-16: 83
- 2026-11-15: 83
- 2026-11-14: 82
- 2026-11-13: 82
- 2026-11-12: 81
- 2026-11-11: 81
- 2026-11-10: 80
- 2026-11-09: 80
- 2026-11-08: 79
- 2026-11-07: 79
- 2026-11-06: 78
- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 74

## Common questions

### What is the aipozi MCP server?

aipozi is an MCP server listed in the public MCP registry as com.aipozi/aipozi. Daily AI visibility: who ChatGPT, Claude, Gemini and Perplexity name instead of you. Domain tools. This page covers its hosted endpoint (https://aipozi.com/mcp).

### Is the aipozi MCP server safe to use?

aipozi scores 85 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 aipozi MCP server expose?

aipozi exposes 14 tools: briefing, list_my_sites, questions, ai_answer, rivals, and 9 more. Their descriptions and schemas cost roughly 2,190 tokens of context every time the server is loaded.

### Does the aipozi MCP server require authentication?

No. We connected to aipozi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the aipozi MCP server still maintained?

aipozi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the aipozi MCP server?

VerifyMCP ran 14 checks on aipozi, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://aipozi.com/mcp
- Repository: https://github.com/aipozi-Analytics/mcp
- Website: https://aipozi.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-aipozi-aipozi/aipozi.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-aipozi-aipozi/aipozi/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-aipozi-aipozi/aipozi.json
- HTML version of this page: https://verifymcp.io/servers/com-aipozi-aipozi/aipozi
