2o

io.github.russellshen1992Published by GitHub account russellshen1992v1.0.0Updated Oct 24, 2026

Human intelligence API — AI agents verify facts with human domain experts via MCP

VerifiedSSEWeb executableKnowledge & Memory

Overview

AI-generated overview

A human intelligence API that lets an AI assistant verify facts with human domain experts through MCP, available as a remote endpoint or a local npm package.

What you can do
Connect an assistant to a human intelligence service so it can submit facts for verification by human domain experts and receive their responses. The manifest lists no individual tools, so the exact operations are not documented here. It can be reached either as a hosted remote endpoint or as a local process started from an npm package.
When to use it
Use it when an assistant needs facts checked by people rather than by another model, for example when accuracy matters more than speed and a human expert's confirmation is acceptable.
Requirements
OAuth authentication is required. It can run as a remote endpoint or as a local process from the npm package, which needs Node.js. No environment variables or headers are declared.
Before you install
OAuth credentials are requested, so review what access is granted. Facts submitted for verification are sent to a third-party service and its human experts, so avoid sending confidential or personal data. No tools are listed, so confirm what data is transmitted before relying on it.

Installation

In SourceWeft

  1. Open 2o in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.russellshen1992%2F2o/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "2o": {
      "type": "sse",
      "url": "https://www.2oapi.xyz/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.