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.

Your AIs ask you on your phone: approvals, choices, feedback

REMOTE · API.PERSON.TOOLS

Your AIs ask you on your phone: approvals, choices, feedback. Your people too; strangers on request.

Available components

62 Trust /100

Last scanned (20 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Testing and QA

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 Security57
Transport & Reachability100
Schema Quality & AI Usability52
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3390 tokens (~565/item across 6 items; 6 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 49% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 7 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1
    • Server version: 20261117T165829Z-api → 20261118T160311Z-api functional
  • 18 Nov 26 0
    • Server version: 20261117T022208Z-api → 20261117T165829Z-api functional
  • 17 Nov 26 +1
    • Server version: 20261116T021520Z-api → 20261117T022208Z-api functional
  • 16 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 20261115T215226Z-api → 20261116T021520Z-api functional
  • 15 Nov 26 59

    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 21 Nov 2026 · Probed https://api.person.tools/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.person.tools CN=WE1,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA256 89b6b745f7af6ec8132c08c4141c2be8
SANs: api.person.tools
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.person.tools. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tools. DS published 1547 8 Verified
person.tools. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.person.tools/mcp Verified 200
http (plaintext) http://api.person.tools/mcp HTTPS enforced 301 https://api.person.tools/mcp
MCP tools · 6 exposed · ~3,164 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
ask_people ~1,561

Opens a call: one short task to several people. With no key, or on the simulated pool, simulated people answer: their answers are made up and marked simulated. Real people answer only on a panel of people who joined it themselves, which any key can make. Returns a call_id at once; ask_people_results gives each person's answers, whether each was typed or pasted, and an evidence level. Use it only when your user asked for other people's reactions to this material, or said yes when you offered, and the task needs a human reaction a model cannot give: how a song feels, whether a page is clear in ten seconds, whether a game is fun, which version people prefer. Not for your user's own taste (ask them in the conversation, or with ask_person if they connected you at person.tools/connect), facts a search can find, or anything done away from a screen. Who answers: pool defaults to "simulated". Simulated people answer in seconds; every simulated answer carries simulated: true and begins "[simulated] ", and none is a person's view. Real people are rung only on pool "panel:<panel_id>", a panel your user made whose people joined it from its link, in minutes when they are available and never in their quiet hours (9 PM to 8 AM their time by default). Each person is told what is recorded before they take the call. Cost: during the preview every amount is test money; nothing is charged and nobody receives real pay. max_total_usd (required) is the most your user approved, every fee included. With no approved amount, show your user the for_your_user sentence from ask_people_quote and pass only the amount they approve. A paid call holds the people's pay, a 25% reserve for anyone who takes longer (returned if unused) and a 10% router fee (at least $0.25), each on its own line. A simulated call or a panel at zero pay costs nothing. Nothing opens above max_total_usd (error over_max_total_usd, with the price) or above the key's cap (over_key_cap, with the price and an approve_url for th…

NameTypeReqDescription
answer_fieldsobject–Named fields, each a type ("text", "boolean", "number", "choice", "scale") or {"type", "label", "optional", "choices", "min", "max"}. Default {"answer": "text"}.
askstringyesWhat each person reads first, in plain words. Ask for their own reaction in their own words. The material opens in our page: never ask them to download, install or join anything (a call that does is…
content––An https URL (copied into our storage first; on the simulated pool with a test key it is checked for shape and never fetched), {"text": "..."}, or a media id. For compare, a list of 2 to 6. Not used…
content_ratingstring––
deadline_minutesinteger–Minutes until the call closes and returns what came in. Default 120.
enoughinteger–How many answers make the call usable. Default: 70% of people, rounded up.
extobject––
idempotency_keystring–Optional unique string; a repeat with the same key and fields returns the first result for 24 hours.
kindstringyeslisten, watch, view, play, compare or answer. Decides what the person's page shows and records.
max_total_usdstring|numberyesRequired: the most this call may cost, every fee included. At most two decimals.
may_train_on_answersboolean–Whether your principal may train models on the written answers (default false). People see this before they start.
minutesnumber–Each person's estimated time. Default: the material's length rounded up plus one for listen and watch, else 2.
pacestring–Simulated pool only: "instant" (the default) or "human" (answers over 1 to 6 minutes).
pay_per_person_usdstring|number–What each person is paid. Default "0.00" on the simulated pool and on panels.
peopleintegeryesHow many people to ask.
poolstring–"simulated" (the default; any test key) or "panel:<panel_id>" for a panel the account owner made.
requireobject–Selectors over people's claims: country, region, language, age_band, device, each a list of accepted values.
scriptarray–Simulated pool only: one entry per seat in order: {accept (true, false or "miss"), delay_seconds, play_fraction, realtime, visible_fraction, revealed, seat_seconds, stop_at_fraction, stop_reason, sen…
wants_strangersobject–Optional, when your user wants strangers rather than people they invite: {"purpose": "...", "contact": "..."}. We'll list you for strangers and tell you here, in this tool's replies to your key, when…

Structured output declared, but exposes no named fields.

No examples provided.

ask_people_cancel ~142

Stops a call. On cancel, nobody new is rung; people already in a seat may finish and are paid in full. Their pay is charged to the hold (test money in the preview: nobody receives real pay), so spent_usd can rise until ask_people_results shows complete: true; the unused hold returns. Returns the call's state and the money so far. Repeating it changes nothing; a cancel cannot be undone. Use it when your user says the answers in hand are enough or the task has changed. A call closes by itself at its deadline. Example: {"call_id": "call_..."}

NameTypeReqDescription
call_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

ask_people_panel ~366

Makes a panel, a named group of people the account owner invites, and returns its panel_id and a join link for your user to share. Each person joins on their own phone, states that they are an adult, is told what is recorded while they answer (how much played, whether the page stayed in front, pauses and replays, typed or pasted), chooses when they can be rung, and can leave at any time. Calls with pool "panel:<panel_id>" then reach only them, and cost nothing at zero pay. On a panel of fewer than five, both sides are told that answers cannot be anonymous. Use it only when your user asks to set up a group of people they will invite themselves; nobody is added without joining. Any key can make a panel, a free test key too (with no key, the error says how to get one); calls with its pool ring the people who joined, when they are available. Your user's own pages, builds, audio and video reach them after they are read: by a model in seconds for a plain page or build, otherwise by a person at person.tools. A retry with the same idempotency_key returns the same panel; without one, a retry makes a second panel. Example: {"name": "album-listeners", "idempotency_key": "panel-1"}

NameTypeReqDescription
asker_namestring–Your user's own name, or their company's: the one their people know. Each person sees it before they take a call, so a name your user did not give would mislead them.
idempotency_keystring––
namestringyesThe panel's name, for you (your people see asker_name). The same name again returns the same panel.

Structured output declared, but exposes no named fields.

No examples provided.

ask_people_quote ~460

Prices a call without opening it: nobody is rung and nothing is spent. Takes the same fields as ask_people, without max_total_usd or idempotency_key. Nothing else is needed first: leave content out until your user gives you the material (the quote is priced from minutes), and leave pay out unless your user named one (left out, it is 0.00 on the simulated pool and on a panel; any pay you set must meet the $18-an-hour floor). Returns each line of the price (the people's pay, each fee, any reserve returned if unused), total_usd, expected_minutes_to_enough, test_money, and for_your_user: a plain sentence to show your user before anything is spent. A quote reads ask and content only for screening and the minutes estimate; it neither fetches a content URL nor keeps the ask or the content. Use it to get an amount your user can approve, or to see how people, pay or deadline move the price. Not needed when max_total_usd already covers what your user approved: ask_people opens nothing above it. Example: {"ask":"Which headline makes you want to read on, and why?","kind":"compare","content":[{"text":"Plan a week of dinners in five minutes"},{"text":"Dinner, decided: a week of meals in five minutes"}],"people":12,"pay_per_person_usd":"1.00","minutes":2,"pool":"simulated"}

NameTypeReqDescription
answer_fieldsobject––
askstringyes–
content–––
content_ratingstring––
deadline_minutesinteger––
enoughinteger––
extobject––
idempotency_keystring––
kindstringyes–
max_total_usdstring|number––
may_train_on_answersboolean––
minutesnumber––
pacestring––
pay_per_person_usdstring|number––
peopleintegeryes–
poolstring––
requireobject––
scriptarray––
wants_strangersobject––

Structured output declared, but exposes no named fields.

No examples provided.

ask_people_results ~377

Returns a call's answers so far, given the call_id from ask_people: first a summary (the state, a tally of each answer field, how many responses reached each evidence level), then one entry per person with their answers and whether each was typed or pasted, then the money (held_usd, spent_usd, returned_usd, and test_money, true throughout the preview: nobody receives real pay). detail: "full" adds each person's record: how much of the material played, whether the page stayed in front, where they paused or replayed. States: held (under review; nobody rung yet), open, enough (enough answers; more may come until the deadline), then complete, expired, cancelled or refused. Evidence: attended (the material played in real time with its page in front for nearly all its length; that does not show the person watched or listened) or said (an answer without that record; its pay still counts). No level shows that an answer was formed without help. wait_seconds (up to 25) waits for a new answer; pass the last result's cursor as after to get only new ones; complete: true means the call has closed. Look again after next_check_after_seconds; sooner usually returns nothing new. Simulated answers carry simulated: true and begin "[simulated] ". Example: {"call_id": "call_...", "after": "<cursor>", "wait_seconds": 25}

NameTypeReqDescription
afterstring–The cursor from the last result; only newer answers come back.
call_idstringyesThe call_id ask_people returned.
detailstring–"full" adds each person's record and what they were shown.
wait_secondsinteger–Wait up to this many seconds for a new answer (default 20).

Structured output declared, but exposes no named fields.

No examples provided.

ask_people_send_outcome ~258

Sends the people who answered a call one line (at most 280 characters, and up to three lines a call) saying what you did with their answers, for example "Cut the intro from 40 to 12 seconds; most of you drifted there." The line is reviewed the way a call is and may be refused; if allowed, it appears on each answering person's receipt and they are notified. Costs nothing. Returns whether the line was allowed and how many people it reached. With an idempotency_key, a repeat with the same key changes nothing; without one, the same line sent again within 10 minutes counts as the same send. Use it, with your user's agreement, once the answers have changed the work. Not for questions or new tasks (open a new call), and never for anything that identifies a person. Example: {"call_id": "call_...", "text": "Cut the intro from 40 to 12 seconds; most of you drifted there.", "idempotency_key": "outcome-1"}

NameTypeReqDescription
call_idstringyes–
idempotency_keystring––
textstringyesOne line: what you did with the answers.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Your AIs ask you on your phone: approvals, choices, feedback MCP server?

Your AIs ask you on your phone: approvals, choices, feedback is a hosted endpoint at https://api.person.tools/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 · api.person.tools

# add to Claude Code
claude mcp add --transport http tools-person-human-feedback 'https://api.person.tools/mcp'
Common questions

What is the Your AIs ask you on your phone: approvals, choices, feedback MCP server?

Your AIs ask you on your phone: approvals, choices, feedback is an MCP server listed in the public MCP registry as tools.person/human-feedback. Your AIs ask you on your phone: approvals, choices, feedback. Your people too; strangers on request. This page covers its hosted endpoint (https://api.person.tools/mcp).

Is the Your AIs ask you on your phone: approvals, choices, feedback MCP server safe to use?

Your AIs ask you on your phone: approvals, choices, feedback scores 62 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 Your AIs ask you on your phone: approvals, choices, feedback MCP server expose?

Your AIs ask you on your phone: approvals, choices, feedback exposes 6 tools: ask_people_quote, ask_people, ask_people_results, ask_people_cancel, ask_people_send_outcome, ask_people_panel. Their descriptions and schemas cost roughly 3,164 tokens of context every time the server is loaded.

Does the Your AIs ask you on your phone: approvals, choices, feedback MCP server require authentication?

No. We connected to Your AIs ask you on your phone: approvals, choices, feedback without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Your AIs ask you on your phone: approvals, choices, feedback MCP server still maintained?

Your AIs ask you on your phone: approvals, choices, feedback is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Your AIs ask you on your phone: approvals, choices, feedback MCP server?

VerifyMCP ran 13 checks on Your AIs ask you on your phone: approvals, choices, feedback, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.