Skip to content

twocents MCP server

page.twocents/twocentstwocents.pagestreamable-httpv1.0.1Scanned

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

4 tools: 1 do something that can't be undone, 2 change things and 1 only read.

Tools: 0 delete, 1 irreversible, 2 write, 1 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the twocents MCP server can do

The twocents MCP server is published by twocents.page, a domain the MCP Registry verified. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (share_pages) and create or change data (2 tools: share_page and resolve_feedback), but cannot delete data. 1 tool only reads.

2 tools read private data (get_feedback and resolve_feedback); 1 tool can send data out of your system (share_pages).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Can't be undone 1Claude Code: ask
  • share_pagesPublish a multi-page set — an entry page plus the pages it links to — into one room as a single atomic operation.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "publish": a word for a change that another call does not undo.

    What it can reach

    • outboundThe description's first verb is "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publish a multi-page set — an entry page plus the pages it links to — into one room as a single atomic operation. Either the whole set lands or nothing changes, so a reviewer never opens a page whose links point at pages that were never stored. Use this instead of calling share_page N times whenever you have more than one page. Note the ceiling: a room is a review set, not a host — it holds 200 pages and 6 MB total. For a large generated corpus, share the entry points a human would actually read and link out to the rest; nobody pins notes on four hundred pages. If the pages are already files on disk, prefer the uploader — it reads them from the folder instead of making you emit every byte: curl -fsSL <origin>/agent.mjs -o .twocents/agent.mjs && FBL_ROOM=<room> node .twocents/agent.mjs --publish <dir>
Changes things 2Claude Code: ask
  • resolve_feedbackMark notes resolved once you have actually applied them.Reads private dataNo findings

    Why it is in this group

    • The name "resolve_feedback" says "resolve": a word for reading.
    • The description's first verb is "mark": a word for a change.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    Description, as the server wrote it
    Mark notes resolved once you have actually applied them. This is what closes the loop: the note leaves the active list for every later get_feedback, and the reviewer who wrote it sees it marked resolved on the page — live, if they have it open — instead of finding their old note sitting next to content you already fixed. Pass "what" you changed; that sentence is shown to the reviewer, so write it for them, not for the log. Requires the creatorKey that share_page returned when the room was created — the review link alone cannot resolve, or any reader could clear feedback that was not theirs. Nothing is deleted: call again with resolved:false to reopen a note.
  • share_pageShare a page or document and get back a review link to send to people.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Share a page or document and get back a review link to send to people. Pass "html" for a self-contained page, or "markdown" for a plan, spec, PR description or report — markdown is rendered to a styled, readable document for you, so prefer it whenever the thing you want a human to approve is prose rather than a built page. Reviewers open the link and pin notes directly on it — 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.
Only reads 1Show 1 read-only tool
  • get_feedbackFetch the reviewer notes for a page shared with share_page, as markdown grouped by page.Reads private dataNo findings

    Why it is in this group

    • The name "get_feedback" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "fetch" and "note": it reads notes.
    Description, as the server wrote it
    Fetch the reviewer notes for a page shared with share_page, as markdown grouped by page. Each note carries the anchored text, the element and its markup as the reviewer saw it, so you can locate and apply it; each page heading carries a URL to read the whole page back, so you never have to guess which file it is. 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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://twocents.page/mcp: tools/list returned 4 tools to an anonymous client, including share_pages (irreversible), share_page (write), resolve_feedback (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__twocents__get_feedback"
    ],
    "ask": [
      "mcp__twocents__share_page",
      "mcp__twocents__share_pages",
      "mcp__twocents__resolve_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as twocents. Review it before you use it.

Capability tags behind 3 rules
  • mcp__twocents__share_pages outbound
  • mcp__twocents__get_feedback private-data
  • mcp__twocents__resolve_feedback private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/page.twocents/twocents/verify?hash=50483c72d04470119ec9153ea3e77b079bcdf88e7f0a7ffdc07df7097719d2ff" | jq -e '.changed == false'

Pinned hash 50483c72d044, from Nov 18, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/page.twocents/twocents/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for page.twocents/twocents
[![Anlyon Radar](https://radar.anlyon.com/badge/page.twocents/twocents.svg)](https://radar.anlyon.com/servers/page.twocents/twocents)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

twocents MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the twocents MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the twocents MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the twocents MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: share_pages.

What tools does the twocents MCP server have?

4 tools: 1 irreversible, 2 write, 1 read. share_pages, share_page, resolve_feedback and get_feedback.

Does the twocents MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the twocents MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): share_pages.

Has the twocents MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.