Skip to content

About

Web UI for MCP OAuth diagnosis — companion to mcp-oauth-connect

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

MCP OAuth Connect — web checker

tests

Why Connectors fail when curl works.

Paste the HTTPS MCP URL you put in Claude, Cursor, Desktop, or Grok. This app probes the OAuth discovery path those UIs actually need — not whether curl got a 200.

Live checker check.gfbytes.com
Product gfbytes.com/products/mcp-oauth-connect
Free CLI / plugin GFB2026/mcp-oauth-connect
Demo MCP https://mcp.gfbytes.com
Attach trace $149 — Stripe checkout on the product page

This repo is the web checker (TanStack Start). The public skill repo is the free diagnose.py + marketplace install. Same probe semantics; this UI is the product surface. Live SoT for the free check UI is https://check.gfbytes.com/ (Vercel custom domain). Do not commit .vercel/output.

What this is not

  • Not the CLI / plugin. Clone mcp-oauth-connect for that.
  • Not a completed handshake. Same as the CLI: discovery metadata only. No DCR, no token, no tools/list.
  • Not a hosted MCP. The demo remote is https://mcp.gfbytes.com (ping-only).

Screenshots

Checker verdict

Pitch + handshake

Clone / run

Requires Node ≥22. No secrets needed for local dev — with DATABASE_URL unset, the app falls back to an embedded PGLite database automatically.

git clone https://github.com/GFB2026/mcp-gfbytes.git
cd mcp-gfbytes
npm install
npm run dev          # http://0.0.0.0:8080
npm run typecheck
npm test

CLI diagnose (stdlib Python, no install):

python diagnose/diagnose.py https://mcp.gfbytes.com
cd diagnose && python -m pytest tests/

What it checks

Authorization-server metadata (or OIDC fallback), PKCE S256, RFC 9728 protected-resource metadata (origin and path forms), no cross-host redirect on the MCP path, unauthenticated GET/POST behavior (401/405 vs anonymous discovery), absolute resource_metadata HTTPS URL.

Repo layout

src/           web app (Checker UI + server diagnose)
diagnose/      CLI diagnose.py + tests (mirrors public skill)
screenshots/   product proof shots
scripts/       build / env helpers
server/        Nitro / PWA middleware

Build output (.vercel/, dist/) is gitignored — do not commit deploy artifacts.

For AI assistants / contributors

Safe work: docs, diagnose unit tests (cd diagnose && python -m pytest tests/), npm test, npm run typecheck, and the GitHub Copilot files under .github/ plus .copilotignore. Do not replace .github/workflows/tests.yml.

The free check is discovery metadata only — do not add DCR, token mint, or tools/list. Do not commit secrets, .env* with credentials, a real DATABASE_URL, .vercel/, or dist/.

License

MIT

About

Web UI for MCP OAuth diagnosis — companion to mcp-oauth-connect

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages