Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
aipozi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Daily AI visibility: who ChatGPT, Claude, Gemini and Perplexity name instead of you. Domain tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aipozi-mcp https://aipozi.com/mcp
# 2 — ask your agent for something these tools do
# briefing, list_my_sites, questions and 11 more
aipozi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AIAll 1 server
aipozi1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http aipozi-mcp https://aipozi.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
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.
No parameter schema on file.
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_
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| question | string | yes | The question: its id ("p03"), its number in the list ("3"), or words from it ("Comrades"). |
| ai | string | yes | The AI: chatgpt, claude, gemini or perplexity. |
| date | string | no | A check day, YYYY-MM-DD. Leave it out for the latest check. |
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?
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | One of your sites (domain, id or name). Leave it out for all of them. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rival | string | yes | The rival's name or domain, e.g. "Linktree" or "heya.page". |
| site | string | no | One of your sites, if the rival is in one site's list. |
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?".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | One of your sites (domain, id or name). Leave it out for all of them. |
| days | integer | no | 7, 30 or 90. Default 7. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domains | array | yes | Domains, e.g. ["heya.page", "linktr.ee"]. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| move | string | no | The move id from action_plan or briefing ("comparison", "page-p03"), or its rank ("1"). Leave it out for the top move. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | no | 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. |
| move | string | yes | The move id ("comparison", "page-p03") or rank ("1"). |
| url | string | no | The shipped page's URL, if there is one. |
| undo | boolean | no | true to take back a mark made by mistake. |
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, .i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | One name ("livedot") or a domain ("livedot.ai"). With an extension, only that one is checked unless extensions are given. |
| names | array | no | 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). |
| extensions | array | no | Extensions to check, e.g. ["ai", "io", "co.za"]. |
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 wit
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | A domain or a link, e.g. "heya.page". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | A domain or a link, e.g. "biotree.bio". |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install aipozi or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.1 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 2 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest21868b286c50632987b21bd6fbe84882954b7f87fcfc32b88a1f95e6f6bed8b2
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| briefing | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| list_my_sites | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| questions | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ai_answer | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| rivals | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| rival_detail | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| trend | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| domain_rating | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| action_plan | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| build_prompt | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| mark_move_done | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| check_domain | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| domain_age | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| ai_crawler_access | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest21868b286c506329
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish aipozi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.