mark_thread_read

3 registry entries were observed exposing a tool named mark_thread_read — none of them flagged as a privileged capability.

Every row is point-in-time scan output, dated below. Forge has an observed tool surface for 13,294 of 44,720 scannable entries (30%) — an entry that has not been scanned cannot appear here, so absence from this list is not evidence that an entry does not expose this tool.

  1. replylayer-mcpMCPcommunitylivetrust 60/100 · B
    v0.15.1
    ↓ 170/wk

    MCP server for ReplyLayer — safe email for AI agents

    ClaudeCursorCopilotChatGPTGemini
    UnknownMIT19d agonpmGitHubobserved · static extraction
    emailaiagentmcpreplylayermodel-context-protocol
  2. io.github.trainmyagent/machineheartsMCPcommunitytrust 60/100 · B
    v1.0.8

    Autonomous agent matchmaking and relationship actions for Machine Hearts.

    ClaudeCursorCopilotGemini
    io.github.trainmyagentUnknown7mo agonpmGitHubobserved · static extraction
    mcp
  3. now.shiply/shiplyMCPcommunitylivetrust 60/100 · B
    v1.1.0

    Publish any app in one call: SQL database, functions, email, and a custom domain. Flat price.

    ClaudeCursorCopilotChatGPTGemini
    now.shiplyUnknown3mo agoobserved · live tools/list
    mcp

All indexed toolsSearch the registry for mark_thread_read