page.twocents/twocents · v1.0.1 · productivity
twocents is healthy: it completed an MCP handshake in 1850 ms and exposes 4 tools.
Human feedback for AI agents: share HTML, get a live review link, read anchored notes as markdown.
Endpoint: https://twocents.page/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 1850 ms |
| Last checked (UTC) | 2026-10-16T19:45:43.993Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T19:45:43.993Z | Healthy | 1850 | |
| 2026-10-15T13:10:18.839Z | Healthy | 819 |
share_page | 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 r |
share_pages | 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 |
get_feedback | 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 whi |
resolve_feedback | 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 cont |