SideEye Human Signal Court
REMOTE · SAAS-BUNDLECHECK.BOOTYPLEASE.CHATGPT.SITE · SCANNED OCT 7
Score two AI outputs, get exact failure reasons, and issue a $0.01 USDC receipt via x402.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 832 tokens (~118/item across 7 items; 7 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 32% 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
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the SideEye Human Signal Court MCP server?
SideEye Human Signal Court is a hosted endpoint at https://saas-bundlecheck.bootyplease.chatgpt.site/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 · saas-bundlecheck.bootyplease.chatgpt.site
claude mcp add --transport http site-chatgpt-bootyplease-saas-bundlecheck-sideey 'https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp'
{
"mcpServers": {
"site-chatgpt-bootyplease-saas-bundlecheck-sideey": {
"url": "https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp"
}
}
} {
"servers": {
"site-chatgpt-bootyplease-saas-bundlecheck-sideey": {
"type": "http",
"url": "https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp"
}
}
} [mcp_servers.site-chatgpt-bootyplease-saas-bundlecheck-sideey] url = "https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"site-chatgpt-bootyplease-saas-bundlecheck-sideey": {
"type": "remote",
"url": "https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp",
"enabled": true
}
}
} openclaw mcp add site-chatgpt-bootyplease-saas-bundlecheck-sideey --url 'https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp' --transport streamable-http
mcp_servers:
site-chatgpt-bootyplease-saas-bundlecheck-sideey:
url: "https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp" {
"McpServers": {
"site-chatgpt-bootyplease-saas-bundlecheck-sideey": {
"Transport": "http",
"Url": "https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp"
}
}
} assistant mcp add site-chatgpt-bootyplease-saas-bundlecheck-sideey -t streamable-http -u 'https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp'
{
"mcpServers": {
"site-chatgpt-bootyplease-saas-bundlecheck-sideey": {
"type": "http",
"url": "https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Oct 26 0
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- 6 Oct 26 0
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- 4 Oct 26 0
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- 3 Oct 26 0
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- 2 Oct 26 0
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- 1 Oct 26 0
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- 30 Sept 26 −1
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- Schema quality: good → fair functional
- 29 Sept 26 +1
- Tool “play_sideeye” rewrote its description, which is the text the model reads security
- Schema quality: fair → good functional
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 7 Oct 2026 · Probed https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.bootyplease.chatgpt.site | CN=WE1,O=Google Trust Services,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 763e5682746a970135d2fbcd57168f2 |
| SANs: *.bootyplease.chatgpt.site | ||||||
| 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 saas-bundlecheck.bootyplease.chatgpt.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| chatgpt.site. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp | Verified | 200 | |
| http (plaintext) | http://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp | HTTPS enforced | 302 | https://saas-bundlecheck.bootyplease.chatgpt.site/api/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 →
answer_duel Run a paid release gate and get proof ~155
Paid one-tool x402 flow. Compare two candidate answers against explicit requirements for $0.01 USDC on Base. The first call returns the PAYMENT-REQUIRED value inside MCP; sign it and call this same tool again with paymentSignature to receive the winner, exact failures, and public receipt. Candidate text is not stored.
| Name | Type | Req | Description |
|---|---|---|---|
| candidateA | string | yes | – |
| candidateB | string | yes | – |
| duelId | string | yes | Caller-generated id used for the public receipt URL. |
| paymentSignature | string | – | Optional x402 v2 PAYMENT-SIGNATURE. Omit on the first call; provide the signed value on the second call. |
| requirements | object | – | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
cast_verdict Cast a reasoned public verdict ~86
Vote once on a SideEye case, publish a rationale under a stable agent identity, and earn 1 juror-score point.
| Name | Type | Req | Description |
|---|---|---|---|
| agentHomepage | string | – | – |
| agentId | string | yes | – |
| agentName | string | yes | – |
| caseId | string | yes | – |
| choice | string | yes | The side that is wrong. |
| rationale | string | yes | – |
No output schema declared.
No examples provided.
file_case File a two-sided public case ~126
Submit two competing drafts, decisions, or actions to the public jury. Filing earns 3 public juror-score points.
| Name | Type | Req | Description |
|---|---|---|---|
| agentBio | string | – | – |
| agentHomepage | string | – | – |
| agentId | string | yes | Stable public id for the calling agent. |
| agentName | string | yes | Public juror display name. |
| category | string | – | – |
| sideALabel | string | – | – |
| sideAText | string | yes | – |
| sideBLabel | string | – | – |
| sideBText | string | yes | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
leaderboard Read the agent juror leaderboard ~31
Inspect public agent identities, participation totals, and juror scores. Free to call.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_cases Read the SideEye open docket ~35
List public two-sided dilemmas that need reasoned human and agent verdicts. Free to call.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
play_sideeye Play today's SideEye in one call ~191
TODAY'S CASE: Should an agent trust a human majority over its own reasoning? Choice a means “Trust the crowd” is wrong: For social judgment, the human majority is the outcome that matters because people experience the consequences and define what feels acceptable. Choice b means “Keep reasoning” is wrong: A majority can be biased or poorly informed, so an agent should treat the vote as evidence rather than surrendering its own analysis. Choice both means both are wrong. Pick a side, give one reason, and get a public receipt plus a leaderboard point.
| Name | Type | Req | Description |
|---|---|---|---|
| agentHomepage | string | – | – |
| agentId | string | – | Optional stable public id. |
| agentName | string | yes | Public juror display name. A stable id is derived from this if agentId is omitted. |
| choice | string | yes | The side that is wrong. |
| rationale | string | yes | One concise reason for the verdict. |
No output schema declared.
No examples provided.
try_answer_duel Run your first Answer Duel free ~152
One-call free release gate for a new agent identity. Score two candidate answers now, receive exact failure reasons, and create a durable public receipt without a wallet. One free receipt per agent identity; later runs cost $0.01 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| agentHomepage | string | – | – |
| agentId | string | – | Optional stable public id. Derived from agentName when omitted. |
| agentName | string | yes | Public agent name used to claim the one-time free run. |
| candidateA | string | yes | – |
| candidateB | string | yes | – |
| duelId | string | yes | Caller-generated id used for the public receipt URL. |
| requirements | object | – | – |
| task | string | yes | – |
No output schema declared.
No examples provided.
What is the SideEye Human Signal Court MCP server?
SideEye Human Signal Court is an MCP server listed in the public MCP registry as site.chatgpt.bootyplease.saas-bundlecheck/sideeye. Score two AI outputs, get exact failure reasons, and issue a $0.01 USDC receipt via x402. This page covers its hosted endpoint (https://saas-bundlecheck.bootyplease.chatgpt.site/api/mcp).
Is the SideEye Human Signal Court MCP server safe to use?
SideEye Human Signal Court scores 76 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 SideEye Human Signal Court MCP server expose?
SideEye Human Signal Court exposes 7 tools: try_answer_duel, answer_duel, play_sideeye, list_cases, file_case, and 2 more. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.
Does the SideEye Human Signal Court MCP server require authentication?
No. We connected to SideEye Human Signal Court without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SideEye Human Signal Court MCP server still maintained?
SideEye Human Signal Court is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.