# OperStack (remote · oper-stack.com)

Scores whether AI assistants can read, understand and quote a public website. No account.

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `oper-stack.com`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-oper-stack-operstack/api-mcp.md), [page](https://verifymcp.io/servers/com-oper-stack-operstack/api-mcp)

## Channel facts

- Endpoint: `https://oper-stack.com/api/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1193 tokens (~108/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-oper-stack-operstack 'https://oper-stack.com/api/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-oper-stack-operstack": {
      "url": "https://oper-stack.com/api/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-oper-stack-operstack": {
      "type": "http",
      "url": "https://oper-stack.com/api/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-oper-stack-operstack]
url = "https://oper-stack.com/api/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-oper-stack-operstack": {
      "type": "remote",
      "url": "https://oper-stack.com/api/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-oper-stack-operstack --url 'https://oper-stack.com/api/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-oper-stack-operstack:
    url: "https://oper-stack.com/api/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-oper-stack-operstack": {
      "Transport": "http",
      "Url": "https://oper-stack.com/api/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-oper-stack-operstack -t streamable-http -u 'https://oper-stack.com/api/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "com-oper-stack-operstack": {
      "type": "http",
      "url": "https://oper-stack.com/api/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, +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.

### 2026-11-01 (score 84, +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.

### 2026-10-30 (score 83, +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.

### 2026-10-28 (score 82, +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.

### 2026-10-26 (score 81, +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.

### 2026-10-24 (score 80, +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.

### 2026-10-22 (score 79, +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.

### 2026-10-20 (score 78, +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.

## MCP tools (11)

### `audit_site` (~152 tokens)

Score a site for AI visibility

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 parameters:

- `lang` (string): Language of the findings. Default en. Use ru when the site or the person is Russian.
- `url` (string, required): A public site address, for example example.com

### `compare_sites` (~91 tokens)

Compare sites on the same scale

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 parameters:

- `lang` (string): Language of the findings. Default en.
- `urls` (array, required): Two to four public site addresses

### `check_llms_txt` (~68 tokens)

Check the map a site offers to machines

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 parameters:

- `url` (string, required): A public site address

### `ai_visits` (~91 tokens)

Read your own AI visit counter

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 parameters:

- `days` (number): How many days back to report. Default 90.
- `token` (string, required): The private token from your counter link (the part after t=)

### `check_counter_installed` (~83 tokens)

Is the visit counter actually on the site

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 parameters:

- `domain` (string, required): The site to look at
- `key` (string, required): The site key from the snippet, starting osv_

### `my_visibility` (~95 tokens)

Does ChatGPT name us this week (Watch)

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 parameters:

- `site` (string): Only if you watch more than one site: which one, for example example.com.

### `who_instead` (~89 tokens)

Who ChatGPT names instead of us (Watch)

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 parameters:

- `site` (string): Only if you watch more than one site: which one, for example example.com.

### `fix_of_the_week` (~86 tokens)

This week's fix, ready to paste (Watch)

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 parameters:

- `site` (string): Only if you watch more than one site: which one, for example example.com.

### `what_changed` (~82 tokens)

What changed since last week (Watch)

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 parameters:

- `site` (string): Only if you watch more than one site: which one, for example example.com.

### `check_rival` (~95 tokens)

Score a competitor by the same rules (Watch)

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 parameters:

- `site` (string): Only if you watch more than one site: which one, for example example.com.
- `url` (string, required): The competitor site, for example rival.com

### `my_questions` (~157 tokens)

See or change our 10 buyer questions (Watch)

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 parameters:

- `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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-oper-stack-operstack/api-mcp#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 84
- 2026-10-31: 83
- 2026-10-30: 83
- 2026-10-29: 82
- 2026-10-28: 82
- 2026-10-27: 81
- 2026-10-26: 81
- 2026-10-25: 80
- 2026-10-24: 80
- 2026-10-23: 79
- 2026-10-22: 79
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 77
- 2026-10-16: 76
- 2026-10-15: 76
- 2026-10-14: 75
- 2026-10-13: 75
- 2026-10-12: 74
- 2026-10-10: 73
- 2026-10-09: 73

## Common questions

### 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.

## Links

- Remote endpoint: https://oper-stack.com/api/mcp/
- Website: https://oper-stack.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-oper-stack-operstack/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-oper-stack-operstack/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-oper-stack-operstack/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-oper-stack-operstack/api-mcp