OperStack
Scores whether AI assistants can read, understand and quote a public website. No account.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"operstack": {
"url": "https://oper-stack.com/api/mcp/"
}
}
}Remote endpoints
https://oper-stack.com/api/mcp/streamable-httpWhat it can do
Tool inventory
Tools (11)
🟢audit_site(url, lang)
Scores any public site out of 100 on the five things an answer engine needs before it will quote a page: whether AI crawlers are allowed in, whether there is a map for agents (llms.txt), whether the entity is clear from schema, whether there is anything quotable, and whether pages carry dates and sources. Use it when someone asks whether ChatGPT or another assistant can read and quote a site. Reads up to 10 public pages. A site that turns away automated readers cannot be scored.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "A public site address, for example example.com"
},
"lang": {
"type": "string",
"enum": [
"en",
"ru"
],
"description": "Language of the findings. Default en. Use ru when the site or the person is Russian."
}
},
"required": [
"url"
]
}🟢compare_sites(urls, lang)
Runs the same AI-visibility scoring on two to four sites and returns them side by side, so a score means something. Use it to see where a site is losing answers to a rival, area by area. A site that turns away automated readers is reported as unreadable.
Input Schema
{
"type": "object",
"properties": {
"urls": {
"type": "array",
"items": {
"type": "string"
},
"description": "Two to four public site addresses"
},
"lang": {
"type": "string",
"enum": [
"en",
"ru"
],
"description": "Language of the findings. Default en."
}
},
"required": [
"urls"
]
}🟢check_llms_txt(url)
Reads a site llms.txt, the file that tells an assistant which pages matter, and follows its links to see whether they still lead anywhere. Use it when someone asks about llms.txt or whether their map for AI assistants works.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "A public site address"
}
},
"required": [
"url"
]
}🟢ai_visits(token, days)
Reports how many visits each AI assistant sent to a site that runs the free OperStack counter. Needs the private token from the counter link, which only the site owner has. Returns visit counts per assistant, not individual visitors.
Input Schema
{
"type": "object",
"properties": {
"token": {
"type": "string",
"description": "The private token from your counter link (the part after t=)"
},
"days": {
"type": "number",
"description": "How many days back to report. Default 90."
}
},
"required": [
"token"
]
}🟢check_counter_installed(domain, key)
Looks at a site page and says whether the OperStack visit counter line is really there, including the case where it is there carrying a different key. Use it when a counter reports nothing and the owner does not know why.
Input Schema
{
"type": "object",
"properties": {
"domain": {
"type": "string",
"description": "The site to look at"
},
"key": {
"type": "string",
"description": "The site key from the snippet, starting osv_"
}
},
"required": [
"domain",
"key"
]
}🟢my_visibility(site)
OperStack Watch subscribers, with their key. Whether ChatGPT (and Perplexity, when it answered) named the subscriber in answers to their 10 buyer questions at the last weekly check, the trend week by week, and the share of answers against the competitors named. The same numbers as that week's Watch email.
Input Schema
{
"type": "object",
"properties": {
"site": {
"type": "string",
"description": "Only if you watch more than one site: which one, for example example.com."
}
}
}🟢who_instead(site)
OperStack Watch subscribers, with their key. For each of the 10 buyer questions at the last weekly check: whether ChatGPT (and Perplexity) named the subscriber, and which businesses they named instead. Then the sites these answers were built from and where to get mentioned.
Input Schema
{
"type": "object",
"properties": {
"site": {
"type": "string",
"description": "Only if you watch more than one site: which one, for example example.com."
}
}
}🟢fix_of_the_week(site)
OperStack Watch subscribers, with their key. The fix of the week from the last Watch email: the buyer question it answers, who ChatGPT named instead, what to change, and the text to put on the site, word for word as in the email.
Input Schema
{
"type": "object",
"properties": {
"site": {
"type": "string",
"description": "Only if you watch more than one site: which one, for example example.com."
}
}
}🟢what_changed(site)
OperStack Watch subscribers, with their key. What moved between the last two weekly checks: how many answers named the subscriber in ChatGPT and Perplexity, the share of answers against each competitor, and the buyer questions where they were named or dropped.
Input Schema
{
"type": "object",
"properties": {
"site": {
"type": "string",
"description": "Only if you watch more than one site: which one, for example example.com."
}
}
}🟢check_rival(url, site)
OperStack Watch subscribers, with their key. Scores a competitor site out of 100 on the same rules as the OperStack free check and the Watch email, and puts it next to the subscriber's own score from the last weekly check.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "The competitor site, for example rival.com"
},
"site": {
"type": "string",
"description": "Only if you watch more than one site: which one, for example example.com."
}
},
"required": [
"url"
]
}🟡my_questions(site, number, question, questions)
OperStack Watch subscribers, with their key. Shows the 10 buyer questions Watch asks ChatGPT and Perplexity every week. Can also replace one question (number and new text) or all ten. Only change questions when the person asked for it. Changes apply from the next weekly check, and history starts again for a changed question.
Input Schema
{
"type": "object",
"properties": {
"site": {
"type": "string",
"description": "Only if you watch more than one site: which one, for example example.com."
},
"number": {
"type": "number",
"description": "To replace one question: its number, 1 to 10."
},
"question": {
"type": "string",
"description": "To replace one question: the new question, at least 5 words."
},
"questions": {
"type": "array",
"items": {
"type": "string"
},
"description": "To replace all ten: exactly 10 different questions."
}
}
}Community
Evidence