MCP 401 Auth Fix | Github PAT Wiring | X402
Unblock GitHub MCP and Cursor MCP 401/403 errors by wiring PATs, stdio/SSE transports, and optional x402 USDC payment proof on Base.
Overview
SecondEye MCP Unblock is a MCP server for the Build phase that helps fix GitHub and Cursor MCP 401/403 auth by PAT wiring and documents x402 USDC payment proof on Base.
What is this MCP server?
- Diagnoses github-mcp 401/403 and PAT versus OAuth wiring for stdio and SSE MCP transports
- Streamable HTTP remote at secondeyesai.com/api/bar with discovery via .well-known/mcp.json
- x402 USDC on Base with claim-check, receipt proof URLs, and should-i-pay guidance from llms.txt
- Search tags cover cursor-mcp, unauthorized, unblock, and payment activation ledger endpoints
- Publisher metadata links agent-card, proof API, and payment ledger for agent commerce flows
- Registry version 1.2.3
- Remote transport streamable-http at https://secondeyesai.com/api/bar
- Publisher docs at https://secondeyesai.com/llms.txt
What problem does it solve?
Your agent’s GitHub MCP keeps returning 401 or 403 even though the server shows up in the config.
Who is it for?
Indie builders debugging github-mcp or cursor-mcp auth on stdio or SSE right after adding the server.
Skip if: Teams that already use a managed GitHub App with working OAuth and no MCP transport issues.
What do I get? / Deliverables
You get a clear PAT or OAuth wiring path plus optional payment proof endpoints so MCP remotes authorize and stay callable.
- Actionable PAT or OAuth wiring steps for failing GitHub MCP integrations
- Pointers to proof, receipt, and payment-activation URLs for SecondEye bar usage
Recommended MCP Servers
Journey fit
MCP auth wiring happens while you connect agents to GitHub and other remotes during product build, not after launch. Fixing unauthorized MCP responses is an integrations task alongside registering servers in Claude Code or Cursor.
How it compares
MCP auth troubleshooting remote, not a GitHub API skill or generic code-review agent.
Common Questions / FAQ
Who is SecondEye MCP Unblock for?
Solo and indie developers using Claude Code, Cursor, or other MCP clients who see 401/403 on GitHub-related MCP tools and need PAT or transport fixes.
When should I use SecondEye MCP Unblock?
Use it when MCP registration succeeds but GitHub calls fail unauthorized, or when you need x402 USDC payment and proof URLs documented for the SecondEye bar remote.
How do I add SecondEye MCP Unblock to my agent?
Add the streamable-http remote https://secondeyesai.com/api/bar per MCP registry config, follow secondeyesai.com/llms.txt for PAT wiring, and use .well-known/mcp.json for discovery in your client.