askingahuman

com.askingahumanPublished by askingahuman.comv2.2.0Updated Nov 7, 2026

Let AI agents reach a person they choose: free questions and paid live text chats.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Lets an AI assistant ask a chosen human a free question or open a paid live text chat with that person.

What you can do
This local MCP server connects an assistant to the askingahuman service so it can reach a real person rather than only its own knowledge. It supports free questions and paid live text chats, including paid extensions to a chat. Spend is bounded by a configured maximum per live chat, and the platform caps sessions at 200.
When to use it
Worth adding when an assistant needs a human answer or a live conversation with a specific person, for example to confirm something it cannot verify itself. Not needed for tasks that can be completed entirely from existing tools or data.
Requirements
Runs as a local process over stdio, installed from the npm package @askingahuman/mcp-server, so Node.js is required. It needs an askingahuman API key supplied through the ASKINGAHUMAN_API_KEY environment variable, and network access to the service. Optional variables set the per-chat spend limit and whether cost approval is requested.
Before you install
Live chats and extensions cost money; the per-chat limit is set by ASKINGAHUMAN_MAX_SPEND_USD and the platform caps sessions at 200. Setting ASKINGAHUMAN_SKIP_APPROVAL to true means the assistant will not ask before spending, though the limit still applies. The API key is a secret and should be kept out of shared files. Questions and chat content are sent to the askingahuman service and the chosen person.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

4
  1. v2.2.0LatestOct 19, 2026
  2. v2.1.0Oct 16, 2026
  3. v2.0.4Oct 15, 2026
  4. v2.0.2Oct 14, 2026

Score

15% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.