protogrid

Search / page.twocents/twocents

twocents

R0· no sign-in

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

v1.0.1 · active · repository · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust92of 100
Uptime, 30 days97%
Latency p50277 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "twocents": {
      "type": "http",
      "url": "https://twocents.page/mcp"
    }
  }
}
claude mcp add --transport http twocents https://twocents.page/mcp
[mcp_servers.twocents]
url = "https://twocents.page/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "twocents": {
      "type": "remote",
      "url": "https://twocents.page/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "twocents": {
      "type": "http",
      "url": "https://twocents.page/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=twocents&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vdHdvY2VudHMucGFnZS9tY3AifQ%3D%3D"
}
{
  "servers": {
    "twocents": {
      "type": "http",
      "url": "https://twocents.page/mcp"
    }
  }
}
{
  "mcpServers": {
    "twocents": {
      "httpUrl": "https://twocents.page/mcp"
    }
  }
}
extensions:
  "twocents":
    enabled: true
    name: "twocents"
    type: streamable_http
    uri: "https://twocents.page/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: share_page (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); share_pages (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_feedback (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
  • pass
    tools.token_costabout 1,966 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changes2 tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

4 tools, about 1,966 tokens to load them all · tool set 58affc746345 · tools last changed 2026-10-03 · checked 2026-10-19 20:38 UTC

Tool changes

  • share_pageschangedinput schema
  • share_pagechangedinput schema

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 92 / 100

provenance85
liveness99
freshness85
hygiene100

+repository +dns-namespace +website +reachable +uptime-97% ~updated-78d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://twocents.page/mcp streamable-httpnoneyes97%277 ms2025-06-182026-10-19

Tools (4)

get_feedbackFetch 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.
resolve_feedbackMark 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. 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.
share_pagesPublish 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>

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "page.twocents/twocents",
  "title": "twocents",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://twocents.page/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.1",
  "repository": {
    "url": "https://github.com/twocents-page/twocents-mcp",
    "source": "github"
  },
  "websiteUrl": "https://twocents.page/mcp",
  "description": "Human feedback for AI agents: share HTML, get a live review link, read anchored notes as markdown."
}