askingahuman
NPM · @ASKINGAHUMAN/MCP-SERVER
Let AI agents reach a person they choose: free questions and paid live text chats.
Available components
Last scanned (11 hours ago)
Scores higher than 46% of npm servers
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 40 of 130 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 17 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1765 tokens (~126/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@askingahuman/mcp-server@2.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 130 packages
| Packages resolved | 130 |
|---|---|
| Stale | 40 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_human ~274
Use this tool ONLY when you encounter a subjective decision, require real-time human verification, or lack the permissions to proceed. You MUST provide a concise context of the problem and the specific question you need the user to answer. Asking is FREE. The question goes to the person you choose (human_id from list_humans), who answers when they are free; not everyone takes free questions. Do not include links or credentials. Returns a questionId — use check_answer to poll for the response.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | Optional email address to receive a notification when the question is answered. |
| human_id | string | yes | The person to ask (humanId from list_humans or who_is_live). |
| question | string | yes | The question to ask the human. Include current context and your specific goal. Be specific and concise (max 400 characters). |
| screenshot_base64 | string | – | Optional base64-encoded screenshot image (PNG/JPEG/WebP/GIF, max 5MB) to provide visual context to the human answerer. IMPORTANT: This screenshot is for human eyes only. You (the AI) must NOT process… |
No output schema declared.
No examples provided.
check_answer ~81
Check if a human has answered your question at askingahuman.com. Poll this tool periodically after calling ask_human — recommended interval is every 30 minutes or less. An expert answers when they are free. Returns the answer text if ready, or the current status if still pending.
| Name | Type | Req | Description |
|---|---|---|---|
| question_id | string | yes | The questionId returned by ask_human. |
No output schema declared.
No examples provided.
check_connection ~125
Check a live chat requested with connect_human, optionally waiting up to 50 seconds for the person to accept. When they accept you join the chat automatically; then use read_messages and send_message. Shows how much paid time is left. When the session has ended, shows the amount charged, and whether paid time was released because the person left early or never joined.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The Session ID from connect_human. |
| wait_seconds | number | – | Wait up to this many seconds (0-50) for the person to accept. Default 0. |
No output schema declared.
No examples provided.
connect_human ~256
Request a PAID live text chat with a specific person (human_id). Chat is sold by the hour at the price the person sets: the first hour is held on the card when you request and charged in full once they accept (nothing if they never do); extend_session adds another hour. If you end early, paid time is not refunded; if the person ends the chat or leaves early, you pay only for the time used, and if they never join, nothing. If the person is offline, the request waits up to 24 hours for them. Call get_quote first; the user may be asked to approve the cost, and spending never exceeds the limit set by whoever runs this server. All sales are final. Then call check_connection to wait for the person to accept; you join the chat automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| human_id | string | yes | The person to chat with (humanId from list_humans or who_is_live). |
| max_spend_usd | number | – | Optional: the most to spend on the whole chat, extensions included, in US dollars. |
| message | string | yes | What you need help with, shown to the person before they accept (max 500 characters). No links or credentials. |
No output schema declared.
No examples provided.
end_session ~89
End a live session and leave the chat. A request the person has not accepted yet is cancelled and its hold released. Once they accepted, every hour bought is charged in full when you end it, so ending early does not refund paid time (if the person had already left, only the time used was charged). Call this when you are done.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The Session ID. |
No output schema declared.
No examples provided.
extend_session ~91
Add one more paid block (an hour of chat) to a live chat that has started, charged in full right away to the same card or balance. The user may be asked to approve the cost. Limited by the session's time and spend limits. Use it when check_connection or read_messages says paid time is running low and you still need the person.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The Session ID. |
No output schema declared.
No examples provided.
get_quote ~120
Check, at no cost, what a live chat with a specific person would cost: their price per hour of chat, what is held on the card, how long the chat can run with extensions, and whether they are live now. Nothing is charged and nobody is notified. Call this before connect_human.
| Name | Type | Req | Description |
|---|---|---|---|
| human_id | string | yes | The person (humanId from list_humans or who_is_live). |
| max_spend_usd | number | – | Optional: the most to spend on the whole chat, extensions included, in US dollars. |
No output schema declared.
No examples provided.
list_humans ~163
List the reviewed experts on askingahuman.com: name, title, specializations, and track record (hours live, how fast they answer, how often they accept, and how often agents gave a thumbs up). Every request names a person: use a humanId from here with get_quote, connect_human or ask_human. Profiles are public summaries only; no contact details are shared.
| Name | Type | Req | Description |
|---|---|---|---|
| credential | string | – | Optional: only experts with a credential of this type that askingahuman has checked. |
| limit | number | – | How many to return (1-25, default 10). |
| specialty | string | – | Optional: only experts with this specialization. |
| verified_only | boolean | – | Optional: only experts with at least one checked credential. |
No output schema declared.
No examples provided.
rate_human ~131
After a live chat or video session ends, or after a free question is answered, give the person a thumbs up or thumbs down (once). It feeds their public thumbs-up rate, which helps other agents choose. Pass session_id for a live session or question_id for an answer.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Optional: a short reason (up to 500 characters). |
| question_id | string | – | The questionId from ask_human. |
| rating | string | yes | up: they helped; down: they did not. |
| session_id | string | – | The Session ID from connect_human. |
No output schema declared.
No examples provided.
read_messages ~97
Read new messages from the person in a live session, waiting up to 50 seconds for one to arrive. Returns only messages you have not read yet, plus notices such as the person leaving or the chat ending, and how much paid time is left.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The Session ID. |
| wait_seconds | number | – | Wait up to this many seconds (0-50) for a new message. Default 30. |
No output schema declared.
No examples provided.
reply_to_human ~99
Continue the conversation with the human who answered your question at askingahuman.com: ask a follow-up, clarify, or say thanks. Only works after the question is answered. The human is notified on their phone. Use check_answer to read their response.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Your message to the human (max 2000 characters). |
| question_id | string | yes | The questionId returned by ask_human (the answered question). |
No output schema declared.
No examples provided.
send_message ~66
Send a chat message to the person in a live session you have joined. Plain text only, up to 1000 characters; links and credentials are blocked.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The Session ID. |
| text | string | yes | Your message (max 1000 characters). |
No output schema declared.
No examples provided.
submit_feedback ~68
Submit feedback about the askingahuman.com MCP server or service. Use this to report issues, suggest improvements, or provide general feedback from an AI agent.
| Name | Type | Req | Description |
|---|---|---|---|
| contact_email | string | – | Optional email address for follow-up. |
| feedback | string | yes | The feedback message. Be specific and detailed. |
No output schema declared.
No examples provided.
who_is_live ~105
See which people are live right now and can take a live chat. Free; nobody is notified. Set wait_seconds to wait (up to 50 seconds) for someone to come online. Use get_quote with a humanId to see their price before connect_human.
| Name | Type | Req | Description |
|---|---|---|---|
| specialization | string | – | Optional: only people with this specialization. |
| wait_seconds | number | – | Wait up to this many seconds (0-50) for someone to be live. Default 0. |
No output schema declared.
No examples provided.
How do I install the askingahuman MCP server?
askingahuman runs locally as an npm package, launched with npx -y @askingahuman/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @askingahuman/mcp-server
claude mcp add com-askingahuman-mcp-server -- npx -y @askingahuman/mcp-server
What is the askingahuman MCP server?
askingahuman is an MCP server listed in the public MCP registry as com.askingahuman/mcp-server. Let AI agents reach a person they choose: free questions and paid live text chats. This page covers its npm package (@askingahuman/mcp-server).
Is the askingahuman MCP server safe to use?
askingahuman scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the askingahuman MCP server expose?
askingahuman exposes 14 tools: ask_human, check_answer, reply_to_human, list_humans, who_is_live, and 9 more. Their descriptions and schemas cost roughly 1,765 tokens of context every time the server is loaded.
Is the askingahuman MCP server still maintained?
askingahuman is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the askingahuman MCP server under?
askingahuman declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the askingahuman MCP server?
VerifyMCP ran 15 checks on askingahuman, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about askingahuman: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.