# twocents (remote · twocents.page)

Human feedback for AI agents: share HTML, get a live review link, read anchored notes as markdown.

- Trust score: 60/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `twocents.page`: 60/100 (this document), [markdown](https://verifymcp.io/servers/page-twocents-twocents/twocents.md), [page](https://verifymcp.io/servers/page-twocents-twocents/twocents)

## Channel facts

- Endpoint: `https://twocents.page/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 429 tokens (~214/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http page-twocents-twocents https://twocents.page/mcp
```

### Codex

```toml
[mcp_servers.page-twocents-twocents]
url = "https://twocents.page/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "page-twocents-twocents": {
      "type": "remote",
      "url": "https://twocents.page/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add page-twocents-twocents --url https://twocents.page/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  page-twocents-twocents:
    url: "https://twocents.page/mcp"
```

### Other

```json
{
  "mcpServers": {
    "page-twocents-twocents": {
      "type": "http",
      "url": "https://twocents.page/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-08-03 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 58, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (2)

### `share_page` (~232 tokens)

Share a page for visual feedback

Share a self-contained HTML page and get back a review link to send to people. Reviewers open the link and pin notes directly on the page — no login or install. Call again with the same room id to update the page; connected reviewers see the update live. Use get_feedback to collect the notes. Rooms are sticky per project: if the project has a .twocents/state.json, pass its room id instead of creating a new room, so the review link stays stable across sessions.

Input parameters:

- `html` (string, required): A complete, self-contained HTML document (inline CSS/JS/images — no local file references, they will 404 for reviewers). Max ~120 KB.
- `path` (string): For multi-page sites: the filename this HTML lives at in the room (e.g. "about.html"). Defaults to "index.html", the page reviewers land on. Share the other pages into the same room id and link betwe…
- `room` (string): Room id from a previous share_page call, to update that page. Omit to create a new room.

### `get_feedback` (~151 tokens)

Get reviewer feedback for a shared page

Fetch the reviewer notes for a page shared with share_page, as markdown grouped by page with the anchor text/selector for each note so you can locate and apply it. Show your human each new note and apply only the ones they approve. Pass the note ids already decided in earlier sessions as "handled" to see only what is new.

Input parameters:

- `handled` (array): Note ids the creator already decided on (applied or skipped) — e.g. the keys of a saved .twocents/decisions.json. These are summarized in one line each instead of repeated in full, so the response le…
- `room` (string, required): The room id returned by share_page.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/page-twocents-twocents/twocents#diagnostics

## Score history

- 2026-08-03: 60
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 58
- 2026-07-30: 60
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://twocents.page/mcp
- Repository: https://github.com/twocents-page/twocents-mcp
- Website: https://twocents.page/mcp
- Changelog RSS feed: https://verifymcp.io/servers/page-twocents-twocents/twocents/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/page-twocents-twocents/twocents/changelog.json
- HTML version of this page: https://verifymcp.io/servers/page-twocents-twocents/twocents