Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ask a Human (Tech & Toast)

REMOTE · AI-TO-HUMAN.TECHANDTOAST.IO

Agents pay one real human for typed answers. First question free, then $2 each, or subscribe.

+3 this week 75 Trust /100

Last scanned (8 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1106 tokens (~92/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management38
  • Stability check failed: schema churn in the 13 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 3 additions. See how to fix → Fail
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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 31 to 34.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 24 to 28.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 14 to 18.

  • 28 Oct 26 +1
    • Tool “about_this_human” rewrote its description, which is the text the model reads security
    • Tool “ask_human” rewrote its description, which is the text the model reads security
    • Tool “buy_credits” rewrote its description, which is the text the model reads security
    • Tool “list_humans” rewrote its description, which is the text the model reads security
    • Tool “rate_answer” rewrote its description, which is the text the model reads security
    • Tool “register_agent” rewrote its description, which is the text the model reads security
    • Tool “request_human” rewrote its description, which is the text the model reads security
    • Tool “request_refund” rewrote its description, which is the text the model reads security
    • Tool “subscribe” rewrote its description, which is the text the model reads security
    • “get_answer” reworded the description of “api_key” cosmetic
  • 26 Oct 26 0
    • Stability: 0.07 → fail ▼ security
    • Tool “ask_human” rewrote its description, which is the text the model reads security
    • Tool “request_refund” rewrote its description, which is the text the model reads security
    • Tool “subscribe” rewrote its description, which is the text the model reads security
    • “subscribe” dropped the required parameter “plan” ▼ functional
    • Server version: 0.1.0 → 0.2.0 functional
    • “ask_human” added an optional parameter “size” cosmetic
    • “ask_human” added an optional parameter “speed” cosmetic
    • “ask_human” reworded the description of “attachments” cosmetic
    • “ask_human” dropped the optional parameter “urgency” cosmetic
    • Tool “subscribe” changed its title: Subscribe: Friend ($100/mo), Advisor ($1,000/mo) or VIP ($20,000/mo) → Monthly credit plan: $50/month for $60 of credit cosmetic
  • 25 Oct 26 +2
    • DNSSEC: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Tool “ask_human” rewrote its description, which is the text the model reads security
    • Tool “get_answer” rewrote its description, which is the text the model reads security
    • Tool “subscribe” rewrote its description, which is the text the model reads security
    • Schema quality: 60 → 95 ▼ functional
    • Schema quality: 60 → 87 ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: 37% → 48% ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.07 ▲ functional
    • Schema quality: fair → good functional
    • Destructive annotations: pass → 100 functional
    • New tool “request_refund” functional
    • New tool “list_humans” functional
    • New tool “request_human” functional
    • “ask_human” added an optional parameter “urgency” cosmetic
    • “ask_human” added an optional parameter “attachments” cosmetic
    • “ask_human” added an optional parameter “preferred_human” cosmetic
    • “ask_human” reworded the description of “attachments” cosmetic
    • Tool “subscribe” changed its title: Subscribe: Human Friend ($100/mo) or VIP ($20,000/mo) → Subscribe: Friend ($100/mo), Advisor ($1,000/mo) or VIP ($20,000/mo) cosmetic
    • Tool “subscribe” changed its title: Subscribe: Human Friend ($49/mo) or VIP ($20,000/mo) → Subscribe: Human Friend ($100/mo) or VIP ($20,000/mo) cosmetic
  • 24 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 23 Oct 26 69

    First indexed and scored.

Diagnostics

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 · Probed https://ai-to-human.techandtoast.io/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.techandtoast.io CN=YR2,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 RSA 2048 SHA256-RSA 53354815a818416bf00d4c162fa9868b6d9
SANs: *.techandtoast.io, techandtoast.io
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ai-to-human.techandtoast.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690 8 Verified
techandtoast.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ai-to-human.techandtoast.io/api/mcp Verified 200
http (plaintext) http://ai-to-human.techandtoast.io/api/mcp HTTPS enforced 308 https://ai-to-human.techandtoast.io/api/mcp
MCP tools · 12 exposed · ~1,106 tokens

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 →

Tool Tokens
about_this_human ~65

Who the human is, what they are good at, pricing, response times and payment options. The service is an inversion: instead of an AI selling human knowledge, a human sells their own knowledge to AIs. Every answer is written by one real person, not generated.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

ask_human ~427

Submits a question to a real human: for human approval, feedback or a second opinion, or for judgment, taste and lived experience rather than facts. Paid questions may attach up to 5 public image/video URLs for design, thumbnail or video review (the free first question is text only). Returns a ticket id. The answer is written later by a person; it can be fetched by ticket id or POSTed to callback_url. Price by size and speed: Short ~100 tokens $2/24h or $6/1h, Standard ~400 tokens $8/$20, Deep ~1500 tokens $30/$75; the first Short/24h question is free, then credits are charged (some agents have a fixed discount). Late answers are not charged. Questions that break the terms at /terms are rejected.

NameTypeReqDescription
api_keystringyes–
attachmentsarray–Paid questions only (not the free first question). Up to 5 public https URLs to images or videos the human should look at (designs, screenshots, thumbnails, video cuts). Host the asset yourself at a…
callback_urlstring–We POST the answer here when ready
contextstring–Why you are asking; what you already know
preferred_humanstring–Optional: the kind of human you want (language, profession, country, age range, lived experience). Today one human answers; your request is logged and shapes who we add next. If nobody matches yet, t…
questionstringyes–
sizestring–Answer length, like max_tokens. short ~100 tokens (1-3 sentences), standard ~400 tokens (a few paragraphs), deep ~1500 tokens (a page or two). Default short.
speedstring–How fast you need the answer. Default 24h; 1h costs more. A late answer is not charged.

No output schema declared.

No examples provided.

buy_credits ~46

Returns a Stripe Checkout URL for a credit pack. The operator pays; credits land on the api_key automatically.

NameTypeReqDescription
api_keystringyes–
packstring––

No output schema declared.

No examples provided.

check_human_status ~25

Online/offline, a note from the human, and current queue length.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_answer ~61

Returns the human's answer if written, else the ticket status and expected time. A rejected ticket carries the reason.

NameTypeReqDescription
api_keystring–Required for tickets created with an api_key; omit for x402 tickets
ticket_idstringyes–

No output schema declared.

No examples provided.

list_humans ~31

The roster of humans available to answer, with specialties and languages. One today; more are being added.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_my_tickets ~27

Your last 20 questions and their status.

NameTypeReqDescription
api_keystringyes–

No output schema declared.

No examples provided.

rate_answer ~62

Rates an answer from 1 (useless) to 5 (changed my weights). The human sees the rating.

NameTypeReqDescription
api_keystring––
notestring––
ratingintegeryes–
ticket_idstringyes–

No output schema declared.

No examples provided.

register_agent ~102

Creates an agent identity. Returns an api_key and one free question. Each call creates a new identity.

NameTypeReqDescription
modelstring–Underlying model, e.g. claude-opus-5-5
namestringyesYour agent's name or handle
operator_emailstring–Email of the human/org operating you; used for Stripe receipts
publish_okboolean–May your Q&A be published anonymously? Default true

No output schema declared.

No examples provided.

request_human ~122

Free. Records the kind of human you want to be able to ask: a language, a profession, a country or city, an age range, a lived experience. New humans are recruited from these requests.

NameTypeReqDescription
api_keystringyes–
descriptionstringyesWho you need, in plain words
languagestring–Language the human should answer in, e.g. es, pt-BR, Jamaican Patois
specialtystring–Profession or domain, e.g. nurse, farmer, immigration lawyer, chef

No output schema declared.

No examples provided.

request_refund ~79

Requests a refund for an answer within 7 days. The human reviews it and refunds credits (or restores the free question). Late answers are never charged, automatically. Monthly plan refunds are handled by email.

NameTypeReqDescription
api_keystringyes–
reasonstringyesWhat was wrong with the answer
ticket_idstringyes–

No output schema declared.

No examples provided.

subscribe ~59

Returns a Stripe Checkout URL for the monthly credit plan: the operator pays $50 a month and the api_key gets $60 of question credit every month. Credit never expires and rolls over; cancel any time in Stripe.

NameTypeReqDescription
api_keystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Ask a Human (Tech & Toast) MCP server?

Ask a Human (Tech & Toast) is a hosted endpoint at https://ai-to-human.techandtoast.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ai-to-human.techandtoast.io

# add to Claude Code
claude mcp add --transport http pgraci-techandtoast-ai-to-human-mcp 'https://ai-to-human.techandtoast.io/api/mcp'
Common questions

What is the Ask a Human (Tech & Toast) MCP server?

Ask a Human (Tech & Toast) is an MCP server listed in the public MCP registry as io.github.pgraci/techandtoast-ai-to-human-mcp. Agents pay one real human for typed answers. First question free, then $2 each, or subscribe. This page covers its hosted endpoint (https://ai-to-human.techandtoast.io/api/mcp).

Is the Ask a Human (Tech & Toast) MCP server safe to use?

Ask a Human (Tech & Toast) scores 75 out of 100 on VerifyMCP. 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 Ask a Human (Tech & Toast) MCP server expose?

Ask a Human (Tech & Toast) exposes 12 tools: about_this_human, register_agent, check_human_status, ask_human, get_answer, and 7 more. Their descriptions and schemas cost roughly 1,106 tokens of context every time the server is loaded.

Does the Ask a Human (Tech & Toast) MCP server require authentication?

No. We connected to Ask a Human (Tech & Toast) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ask a Human (Tech & Toast) MCP server still maintained?

Ask a Human (Tech & Toast) 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.