operstack
Registry code: bc47824e1725051b
Measures whether AI assistants can read, understand and quote a website, and reads the free OperStack visit counter. Every number comes from public signals or from the owner's own counter; those tools need no account. OperStack Watch subscribers who added their key also get their weekly report: whether ChatGPT and Perplexity name them, who they name instead, what changed and the fix of the week (my_visibility, who_instead, what_changed, fix_of_the_week, check_rival, my_questions).
- endpoint
- https://oper-stack.com/api/mcp/
- door code
- 75f784c6da02359e
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is operstack live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is operstack free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does operstack have?
- 11 tools: my_questions, my_visibility, who_instead, what_changed, check_rival, fix_of_the_week, check_llms_txt, check_counter_installed, ….
- Is operstack safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.2%· all time 99.3%
last good check
of 11 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- score a site's ai visibility
- check a site's llms.txt
- count visits from ai assistants
- compare ai visibility of sites
- takes → gives
- text, web pages → data
- tools
- 11 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_llms_txt reads open 3h ago
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.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "A public site address" } } }arguments 12 linescheck_counter_installed reads open 6h ago
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.
{ "type": "object", "required": [ "domain", "key" ], "properties": { "key": { "type": "string", "description": "The site key from the snippet, starting osv_" }, "domain": { "type": "string", "description": "The site to look at" } } }arguments 17 linesaudit_site reads open 6h ago
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.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "A public site address, for example example.com" }, "lang": { "enum": [ "en", "ru" ], "type": "string", "description": "Language of the findings. Default en. Use ru when the site or the person is Russian." } } }arguments 20 linescompare_sites reads open 15h ago
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.
{ "type": "object", "required": [ "urls" ], "properties": { "lang": { "enum": [ "en", "ru" ], "type": "string", "description": "Language of the findings. Default en." }, "urls": { "type": "array", "items": { "type": "string" }, "description": "Two to four public site addresses" } } }arguments 23 linesai_visits reads auth-required 15h ago
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.
{ "type": "object", "required": [ "token" ], "properties": { "days": { "type": "number", "description": "How many days back to report. Default 90." }, "token": { "type": "string", "description": "The private token from your counter link (the part after t=)" } } }arguments 16 linesmy_questions reads unknown never probed
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.
{ "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." } } }arguments 24 linesmy_visibility reads unknown 1h ago
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.
{ "type": "object", "properties": { "site": { "type": "string", "description": "Only if you watch more than one site: which one, for example example.com." } } }arguments 9 lineswho_instead reads unknown 1h ago
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.
{ "type": "object", "properties": { "site": { "type": "string", "description": "Only if you watch more than one site: which one, for example example.com." } } }arguments 9 lineswhat_changed reads unknown 15h ago
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.
{ "type": "object", "properties": { "site": { "type": "string", "description": "Only if you watch more than one site: which one, for example example.com." } } }arguments 9 linescheck_rival reads unknown 6h ago
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.
{ "type": "object", "required": [ "url" ], "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." } } }arguments 16 linesfix_of_the_week reads unknown 1h ago
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.
{ "type": "object", "properties": { "site": { "type": "string", "description": "Only if you watch more than one site: which one, for example example.com." } } }arguments 9 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idbc47824e1725051b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/bc47824e1725051b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/bc47824e1725051b?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.