Questions it answers
Namequota measures your brand's share of AI answers. Paste what ChatGPT, Perplexity, Google AI Mode or Claude answered to a buyer question, with its source links, and see whether the answer named you and linked you.
Send up to 50 answers at once and get mention share and citation share, such as 0 of 8, split by engine and by buyer prompt. A buyer prompt is a question that does not already name you, so a mention there was earned. If an engine repeats the question, that echo does not count.
Add your rivals to see who the answers name instead. The tool lists the sites engines cite in the answers that skip you, with their page type, and turns that into a short list of pages to write or places to get listed.
It scores the text you send. It does not ask any AI engine and it does not fetch the links, so it never scrapes ChatGPT, Perplexity, Google or Claude. Answers are not stored.
What it can do
- Mention share and citation share of a brand across up to 50 AI answers
- Split by engine and by buyer prompts that do not name the brand
- Ignores a prompt the answer repeats, so an echo is not a mention
- Counts how often each named rival is named and linked
- Lists the sites engines cite instead, with a short fix list
- Scores pasted text only: no engine call, no fetch, nothing stored
Tools
score_answer_share, Score brand share in AI answers. Call this whenever a user pastes one or more answers from ChatGPT, Perplexity, Google AI Mode, Claude or another AI assistant and asks whether the answers named or linked their brand, what share they got, which rivals or sites the answers chose instead, or what to do about it. Pass the brand, its domain, rival names and every answer in answers (each with its prompt, engine and source links). Returns mention share and citation share (such as 0 of 3), split by engine and for buyer prompts (prompts that do not name the brand), how often each rival is named, the sites cited instead and a short fix list. Fixed rules: a repeated prompt is not a mention, and a link counts only if it goes to the brand domain. It scores pasted text only and never queries an AI engine.
Add Namequota in Pi
Pi does not speak MCP on its own. The pi-mcp-adapter extension (these steps match version 2.34.0) loads remote servers and keeps their schemas out of the prompt until you ask. Install it once, then restart Pi:
pi install npm:pi-mcp-adapterAdd the server to a shared MCP file. Use .mcp.json in the project if only that project needs Namequota, or ~/.config/mcp/mcp.json if you want it in every project. Pi also reads ~/.agents/mcp.json. A Pi-only override lives in ~/.pi/agent/mcp.json or .pi/mcp.json and wins over the shared file.
{
"mcpServers": {
"answer-share": {
"url": "https://answershare.openkrill.app/mcp",
"lifecycle": "eager"
}
}
}The url is enough. Do not set command: that field is for a local process. No API key header. lifecycle is eager so Pi connects at startup and can search tool names before the first call. A config that omits it still works: the first call connects. After restart, run /mcp and confirm the server is listed. Ask: Did this ChatGPT answer name or link acme.com? Here is the answer and its sources. The adapter should offer score_answer_share.
Leave directTools off unless you want those schemas in every turn. With a handful of tools the cost is small. The default proxy is the better fit: search for the tool, then call it. /mcp disable answer-share writes a project override in .pi/mcp.json without editing the shared file. Run /reload after that change.
Pi will not find this server by scanning Cursor or Claude config unless you run /mcp setup and import it. Putting the url in .mcp.json is the direct path and the one this page tests against. The server is the same public endpoint the other clients use, with the same limits and the same privacy rules.
If it does not work
The tool does not show up
Run /mcp to see the servers the adapter loaded. If it is missing, check the url entry in .mcp.json, then run /reload or restart Pi.
429 or rate_limited
Each server takes 60 calls a minute from one network, and some tools take fewer. Past that the call comes back as a tool error that starts with rate_limited: wait a minute and ask again. daily_limit means the server reached its shared daily cap, which resets at 00:00 UTC. A limit is not an answer, so do not read it as no results. For higher limits, ask support@openkrill.app for a key.
A call checked on 2026-10-11
A made-up answer about a made-up brand. The tool reads only this text, calls no AI engine, opens no link and keeps nothing. The request below was posted to https://answershare.openkrill.app/mcp as tools/call. HTTP 200. Source: the Namequota server, read 2026-10-11.
{
"method": "tools/call",
"params": {
"name": "score_answer_share",
"arguments": {
"brand": "Acme CRM",
"domain": "acme.com",
"prompt": "best CRM for a small sales team",
"answer": "For a small sales team, HubSpot is the usual pick. Pipedrive suits pipeline-heavy teams. Acme CRM is a simpler option.",
"links": [
"https://www.g2.com/categories/crm",
"https://www.hubspot.com/products/crm"
]
}
}
}- by engine. 1 returned
- answers. 1 returned
- recommendations. 2 returned
Repeat the call yourself if you need a newer reading. Cached answers expire. A rate limit is not a result: wait and try again. Nothing in the call is a ranking, a filing, or advice.
Using it in production
Nothing to install and nothing to run: no package, no Python or Node.js version and no environment variable. Namequota runs on our servers, and your client only needs the URL https://answershare.openkrill.app/mcp.
| Rate limit | 60 tool calls a minute from one network. initialize and tools/list do not count. |
|---|---|
| Daily cap | 5000 tool calls a day per server, shared by every caller. It resets at 00:00 UTC. |
| At a limit | The call comes back as a tool error that starts with rate_limited (wait a minute) or daily_limit (try after 00:00 UTC), never as a partial answer. |
| Key | None. Do not add an Authorization header or a key field. |
| Higher limits | Email support@openkrill.app with the server name, the calls a day you expect and what they are for. We answer within 1 business day. |
| Freshness | Some answers come from a short cache. Each guide shows the date of its checked call; repeat a call when you need a newer reading. |
| Uptime | Scheduled test calls check the servers through the same endpoint. There is no SLA yet. |
| Data | What each server receives and keeps is on the privacy page. |
Use it in other apps
Frequently asked questions
How do I install the Namequota MCP server in Pi?
Run pi install npm:pi-mcp-adapter once, add answer-share with the url https://answershare.openkrill.app/mcp to .mcp.json, then restart Pi and run /mcp to see it.
Do I need an API key to run Namequota in Pi?
No. This server takes no API key. For higher limits, email support@openkrill.app with the server name (Namequota), the calls a day you expect and what they are for. We answer within 1 business day.
What should I do if Namequota does not connect in Pi?
Check that the entry has a url and no command field, then run /reload or restart Pi and run /mcp.