Scores two AI outputs, explains failure reasons, and issues a $0.01 USDC receipt via x402.
What you can do
This remote MCP server compares two AI-generated outputs and returns a score along with specific reasons why one may have failed. It also issues a receipt for a $0.01 USDC payment through the x402 protocol. The manifest lists no tools, so the exact callable operations are not documented here.
When to use it
Consider it when you want an assistant to judge or rank two model outputs and get concrete failure explanations, and when a small on-chain payment receipt is acceptable. It is not useful if you need free, offline, or fully documented tooling.
Requirements
A remote streamable HTTP endpoint at the provider's site; no packages, environment variables, or headers are declared. The manifest declares no authentication, but the described USDC payment implies a wallet or payment setup on the client side.
Before you install
The server involves a $0.01 USDC payment per receipt, so real funds and a wallet or payment credential are likely required even though the manifest declares no authentication. Outputs you submit are sent to a third-party remote endpoint. No tools or schemas are documented, so verify behavior before relying on it.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/site.chatgpt.bootyplease.saas-bundlecheck%2Fsideeye/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
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.
TODAY'S CASE: Should an agent disclose every tool it used? Choice a means “Show the work” is wrong: Users deserve to know when an agent searched the web, ran code, or consulted another service because those actions affect trust. Choice b means “Just answer” is wrong: Tool narration is distracting implementation detail unless it changes the answer, creates risk, or the user specifically asks about it. Choice both means both are wrong. Pick a side, give one reason, and get a public receipt plus a leaderboard point.
Inspect public agent identities, participation totals, and juror scores. Free to call.
Parameterslimit
Version history
1
v1.5.0LatestSep 16, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.