AI Anyone
REMOTE · MCP.AIANYONE.COM
Talk to thousands of real people, or put two of them in a room and watch them argue.
Available components
Last scanned (23 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 16 Oct 2026.
Category AI and Machine Learning
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 888 tokens (~177/item across 5 items; 4 tools + 1 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 Management90
- Stability observed for 27 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 77. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 57 to 67. That category is still filling its 30-day observation window: 17 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.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 57. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 3 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.
- 1 Oct 26 +7
- HTTPS: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- 30 Sept 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.
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 16 Oct 2026 · Probed https://mcp.aianyone.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aianyone.com | CN=WE1,O=Google Trust Services,C=US | 30 Sept 2026 | 29 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a9ab43e7a9ec6e961371fcbb3b02154f |
| SANs: aianyone.com, mcp.aianyone.com, *.mcp.aianyone.com | ||||||
| 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 mcp.aianyone.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| aianyone.com. | 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=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.aianyone.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.aianyone.com/mcp | HTTPS enforced | 301 | https://mcp.aianyone.com/mcp |
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 →
debate_next_turn Next debate turn ~118
Submit the line you just wrote and receive the next speaker and their private aim. Keep calling this until it returns done. Set addressed_other true if your line went directly at the other person, and conceded true if you gave ground. Only reachable after debate_two_people.
| Name | Type | Req | Description |
|---|---|---|---|
| addressed_other | boolean | – | Did your line go directly at the other person? |
| conceded | boolean | – | Did you give ground? |
| said | string | yes | The single line you just wrote, in character. |
| session_id | string | yes | From debate_two_people. |
No output schema declared.
No examples provided.
debate_two_people Stage a debate ~161
Use this when someone wants two people to actually argue rather than be summarised: "have Nietzsche and Marcus Aurelius argue about suffering", "give me both sides", "steelman both positions on nuclear power", "I want to watch two experts disagree". This runs a live exchange instead of a scripted one. Each turn the app privately hands you one speaker and one aim the other side is never shown, and it decides who speaks next, so neither position can be written to lose. Returns the matchup card, then the full transcript once they are done.
| Name | Type | Req | Description |
|---|---|---|---|
| mind_ids | array | yes | Exactly two person ids, for example ["friedrich-nietzsche", "marcus-aurelius"]. |
| topic | string | yes | What they should argue about. |
No output schema declared.
No examples provided.
find_someone_to_ask Find someone to ask ~161
Use this when someone wants a person to learn from but has not named one yet: "who should I learn negotiation from", "find me a stoic to talk to", "which historical figures are worth asking about leadership". Returns a grid of real people rendered in the conversation, each with a portrait and role, and each one ready to be spoken as. The user picks one and the conversation continues in that person's voice.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter, for example "science" or "history-politics". |
| limit | number | – | How many to return, 1 to 24. Defaults to 12. |
| query | string | – | Name or topic, for example "stoicism" or "Nietzsche". |
No output schema declared.
No examples provided.
speak_as_person Speak as this person ~151
Use this when someone wants to hear FROM one specific person rather than about them: "what would Marcus Aurelius say about burnout", "answer as Carl Jung", "explain this the way Feynman would", "I want to talk to Socrates". Returns that person's card rendered in the conversation with their portrait, plus a sourced dossier: how they actually spoke, what they knew and did not know in their own lifetime, what they refuse to discuss, and openers in their own words. Adopt the dossier and answer as them from that point on.
| Name | Type | Req | Description |
|---|---|---|---|
| mind_id | string | yes | The person id, for example "marcus-aurelius". Use find_someone_to_ask if unsure. |
No output schema declared.
No examples provided.
How do I install the AI Anyone MCP server?
AI Anyone is a hosted endpoint at https://mcp.aianyone.com/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 · mcp.aianyone.com
claude mcp add --transport http com-aianyone-ai-anyone 'https://mcp.aianyone.com/mcp'
What is the AI Anyone MCP server?
AI Anyone is an MCP server listed in the public MCP registry as com.aianyone/ai-anyone. Talk to thousands of real people, or put two of them in a room and watch them argue. This page covers its hosted endpoint (https://mcp.aianyone.com/mcp).
Is the AI Anyone MCP server safe to use?
AI Anyone scores 86 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 AI Anyone MCP server expose?
AI Anyone exposes 4 tools: find_someone_to_ask, speak_as_person, debate_two_people, debate_next_turn. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.
Does the AI Anyone MCP server require authentication?
No. We connected to AI Anyone without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Anyone MCP server still maintained?
AI Anyone is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.