Callable

io.github.CCSTT-devPublished by GitHub account CCSTT-devv1.0.0Updated Oct 24, 2026

API for AI agents to delegate tasks to real humans.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an AI assistant hand blocked verification steps to a real human operator and collect the result.

What you can do
Submit a verification task to a human operator, such as a KYC check, sign-in, 2FA prompt, CAPTCHA or identity confirmation, with an optional callback URL and a charge per task. Poll a submitted task for its status, result payload and output URLs such as video or screenshot. Optionally approve a completed task to release the operator payout, or dispute it with a reason and acceptance criteria.
When to use it
Use it when an agent is stuck on a step only a real person can finish, such as a CAPTCHA, 2FA prompt or identity check, and you are willing to pay per task for a human operator to complete it.
Requirements
A remote streamable HTTP endpoint at getcallable.dev; no packages, environment variables or headers are declared. Tasks are charged, so a billing arrangement is implied. Network access is required.
Before you install
Submitting a task costs money per task, and approving a task releases the operator's payout. Tasks may involve sensitive verification material such as identity documents or sign-in and 2FA steps, which are passed to a third-party human operator. Approving or disputing changes task state and payment.

Installation

In SourceWeft

  1. Open Callable in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. 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.CCSTT-dev%2Fcallable/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.

{
  "mcpServers": {
    "callable": {
      "type": "http",
      "url": "https://getcallable.dev/api/mcp"
    }
  }
}

README

This repository has no README.

Tools

3

submit_task

Submit an account verification task to a real human operator. Use this when your agent is blocked on something only a real person can complete — a KYC check, a platform sign-in or 2FA prompt, a CAPTCHA, an identity confirmation, or any verification step that requires a human. The task is charged automatically via Stripe ($39). A vetted operator claims it, performs the verification on real hardware, and returns the result (with optional screenshot) to your callback_url or via get_task_status. Typical completion: 30 minutes.

Parameterstask_typerequiredcallback_urlinstructionsrequireddeadline_minutesrequiredpayment_credential

get_task_status

Poll the status and retrieve the result of a previously submitted task. Returns the current status (pending, in_progress, pending_review, completed, disputed), the result payload, and any output URLs (video, screenshot). Use this in a polling loop after submit_task if no callback_url was provided.

Parameterstask_idrequired

review_task

Optional. Approve or dispute a task that is in `pending_review` status. Use this after get_task_status reports the operator has completed the work. Approving releases the operator payout. Disputing requires a reason and a description of what is needed for acceptance; the operator is then allowed to resubmit. If you never call review_task, tasks are auto-approved after the review window expires.

Parameterstask_idrequireddecisionrequireddispute_reasonwhat_is_needed

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% 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 listedRequired15 pts
  • 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.