OperStack
REMOTE · OPER-STACK.COM
Scores whether AI assistants can read, understand and quote a public website. No account.
Available components
Last scanned (16 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1193 tokens (~108/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://oper-stack.com/api/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=oper-stack.com | CN=YR1,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 6ee3311fc58c65bb0021616cbf668ca2ab2 |
| SANs: oper-stack.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of oper-stack.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| oper-stack.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://oper-stack.com/api/mcp/ | Verified | 200 | |
| http (plaintext) | http://oper-stack.com/api/mcp/ | HTTPS enforced | 308 | https://oper-stack.com/api/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ai_visits Read your own AI visit counter ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | How many days back to report. Default 90. |
| token | string | yes | The private token from your counter link (the part after t=) |
No output schema declared.
No examples provided.
audit_site Score a site for AI visibility ~152
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the findings. Default en. Use ru when the site or the person is Russian. |
| url | string | yes | A public site address, for example example.com |
No output schema declared.
No examples provided.
check_counter_installed Is the visit counter actually on the site ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The site to look at |
| key | string | yes | The site key from the snippet, starting osv_ |
No output schema declared.
No examples provided.
check_llms_txt Check the map a site offers to machines ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A public site address |
No output schema declared.
No examples provided.
check_rival Score a competitor by the same rules (Watch) ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | Only if you watch more than one site: which one, for example example.com. |
| url | string | yes | The competitor site, for example rival.com |
No output schema declared.
No examples provided.
compare_sites Compare sites on the same scale ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the findings. Default en. |
| urls | array | yes | Two to four public site addresses |
No output schema declared.
No examples provided.
fix_of_the_week This week's fix, ready to paste (Watch) ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | Only if you watch more than one site: which one, for example example.com. |
No output schema declared.
No examples provided.
my_questions See or change our 10 buyer questions (Watch) ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | number | – | To replace one question: its number, 1 to 10. |
| question | string | – | To replace one question: the new question, at least 5 words. |
| questions | array | – | To replace all ten: exactly 10 different questions. |
| site | string | – | Only if you watch more than one site: which one, for example example.com. |
No output schema declared.
No examples provided.
my_visibility Does ChatGPT name us this week (Watch) ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | Only if you watch more than one site: which one, for example example.com. |
No output schema declared.
No examples provided.
what_changed What changed since last week (Watch) ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | Only if you watch more than one site: which one, for example example.com. |
No output schema declared.
No examples provided.
who_instead Who ChatGPT names instead of us (Watch) ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | – | Only if you watch more than one site: which one, for example example.com. |
No output schema declared.
No examples provided.
How do I install the OperStack MCP server?
OperStack is a hosted endpoint at https://oper-stack.com/api/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.
remote · oper-stack.com
claude mcp add --transport http com-oper-stack-operstack 'https://oper-stack.com/api/mcp/'
What is the OperStack MCP server?
OperStack is an MCP server listed in the public MCP registry as com.oper-stack/operstack. Scores whether AI assistants can read, understand and quote a public website. No account. This page covers its hosted endpoint (https://oper-stack.com/api/mcp/).
Is the OperStack MCP server safe to use?
OperStack 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 OperStack MCP server expose?
OperStack exposes 11 tools: audit_site, compare_sites, check_llms_txt, ai_visits, check_counter_installed, and 6 more. Their descriptions and schemas cost roughly 1,089 tokens of context every time the server is loaded.
Does the OperStack MCP server require authentication?
No. We connected to OperStack without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OperStack MCP server still maintained?
OperStack is still listed as active in the MCP registry. We last reached this channel on 5 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 OperStack MCP server?
VerifyMCP ran 13 checks on OperStack, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.