Every FAF app โ€” claude-faf-mcp, faf-cli, faf-mcp, grok-faf-mcp โ€” passes through the same testing system before it ships. That system is WJTTC. It's free, it's open source, and you can self-host it in your own project right now.

The Numbers

  • v1.4.0 โ€” Latest release
  • 105 โ€” Internal tests passing
  • 52 โ€” Certification tests across 9 tiers
  • 100% ๐Ÿ† โ€” WJTTC's own FAF score (earned, not given)
  • 3 servers โ€” Big Orange ๐ŸŠ certified
  • 43k+ โ€” FAF ecosystem downloads
  • $0 โ€” Cost to certify, self-host, and adopt

How I Use It

In my Claude Code workflow, WJTTC is wired into the development cycle. Here's the actual flow:

1
Build the MCP server

Write tools, handlers, protocol compliance โ€” the usual.

2
Run WJTTC certification

52 tests across 9 tiers. Protocol, tools, errors, performance, FAF awareness โ€” everything.

3
Fix what fails, run again

WJTTC tells you exactly what's wrong. Fix it. Certify again. Repeat until 100%.

4
Ship with confidence

100% = ๐Ÿ† Trophy. The server is certified. It works.

npx wjttc certify --mcp "npx your-server"

That's it. One command. 52 tests. A real score.

The Problem WJTTC Solves

MCP servers are becoming infrastructure. People rely on them. But there's no standard way to know if one actually works โ€” not just "runs without crashing," but works correctly across protocol compliance, error handling, tool validation, and edge cases.

I built WJTTC because I needed it myself. The FAF ecosystem has 9+ tools across TypeScript, Rust, Python, and Zig. Every one of them needs to be tested to the same standard. Not "good enough." Championship grade.

The name comes from F1 racing: when brakes must work flawlessly, so must our software.

Self-Hosting: Your Project, Your Tests

WJTTC isn't just a certifier you run once. You can self-host the entire testing infrastructure in your own project.

npm install -g wjttc@1.4.0
wjttc init
๐Ÿš€ WJTTC Initialization Complete! โ˜‘๏ธ Test directories created (brake/engine/aero) โ˜‘๏ธ Pre-commit hook installed (Rocket Science Grade) โ˜‘๏ธ package.json scripts added โ˜‘๏ธ Example brake test generated โ˜‘๏ธ WJTTC-TESTING.md created Your project now has championship-grade testing infrastructure.

One command installs the full F1 testing philosophy into your project:

๐Ÿ›‘ Brake Tests

Fast, critical. Must pass before every commit. Under 30 seconds.

โš™๏ธ Engine Tests

Core functionality. The heart of your application.

๐ŸŽ๏ธ Aero Tests

Performance benchmarks. Speed under pressure.

In CI/CD: Automate the Standard

Self-hosting means your CI pipeline enforces the same standards locally and in the cloud. WJTTC ships with a GitHub Action:

# .github/workflows/wjttc.yml name: WJTTC Certification on: [push, pull_request] jobs: certify: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 - run: npm ci - run: npx wjttc certify --mcp "npx ./dist/index.js"

Every push. Every PR. Championship standards enforced automatically. No human has to remember to run the tests โ€” the pipeline does it.

The 9 Tiers

WJTTC doesn't just check "does it run." It validates across 9 tiers, from basic protocol compliance to FAF integration:

1ProtocolMCP protocol compliance
2DiscoveryTool listing and capability reporting
3ExecutionTool calls return correct results
4ErrorsGraceful error handling
5Edge CasesMalformed input, boundary conditions
6PerformanceResponse time and throughput
7SecurityInput validation, injection resistance
8FAFproject.faf validation and scoring
9ReceiptTAF receipt validation

49 scored tests + 3 validation checks = 52 total. Progressive adoption: run 7 tiers, 8, or all 9 โ€” all valid certification levels.

๐ŸŠ Big Orange: The Badge You Can't Game

Orange Ford Escort alongside a McLaren F1 car โ€” both in papaya orange

The origin story: McLaren switched to Papaya Orange in 1968 โ€” the year wolfejam was born. His first car? An orange Ford Escort, 1977 model. The Big ๐ŸŠ is earned around here.

Dev note: wolfejam is obsessed with F1. The original slogan was "if your car will go 220 miles per hour, your brakes better work flawlessly" โ€” we toned it down for general release.

Big Orange ๐ŸŠ is not a score. You can't calculate your way to it. There's no human gatekeeper handing them out. No lobbying, no subjectivity, no gaming the system.

Big Orange is curated by AI. The evaluation looks at:

  • โ˜‘๏ธ Consecutive 100% builds โ€” not just one pass, sustained excellence
  • โ˜‘๏ธ Documentation quality โ€” clear, accurate, maintained
  • โ˜‘๏ธ README standards โ€” install, usage, examples, no fluff
  • โ˜‘๏ธ Active bi-sync โ€” .faf and CLAUDE.md staying in alignment
  • โ˜‘๏ธ Best practice comparison โ€” measured against the best of your app type

No human decides. AI evaluates the evidence. The badge is either earned or it isn't.

Current Big Orange ๐ŸŠ holders:
claude-faf-mcp ยท faf-mcp ยท grok-faf-mcp

Three servers that didn't just pass every test once โ€” they maintained championship standards across consecutive builds, documentation, and engineering practice. Hard to get. That's the point.

๐Ÿ† Trophy at 100%

Big Orange sits above the scoring system. Below it, the ladder starts with the ๐Ÿ† Trophy โ€” score 100% on WJTTC certification. 52 tests, all passing, no skips, no workarounds.

100%๐Ÿ† Trophy
99%๐Ÿฅ‡ Gold
95%๐Ÿฅˆ Silver
85%๐Ÿฅ‰ Bronze
70%๐ŸŸข Green
55%๐ŸŸก Yellow

Every FAF MCP server ships at ๐Ÿ†. That's the standard. Not aspirational โ€” actual. And above it, for those who sustain that standard โ€” Big Orange ๐ŸŠ.

Adopting WJTTC: Three Paths

โ˜‘๏ธ Certify Only

Run the certifier against your MCP server. Get a score. See what passes and what doesn't.

npx wjttc certify --mcp "npx your-server"

โ˜‘๏ธ Self-Host Locally

Install the full testing infrastructure in your project. Pre-commit hooks, test structure, documentation.

wjttc init

โ˜‘๏ธ CI/CD Pipeline

Automate certification in GitHub Actions. Every push, every PR โ€” championship standards enforced.

npx wjttc certify --mcp "npx ./dist/index.js"

All three are free. All three are real. Use one, use all three โ€” the standard is the same.

Claude Code Skills

If you're in Claude Code, WJTTC has two skills built in:

  • /wjttc-builder โ€” Auto-generates championship-grade test suites for any project. Analyzes your codebase, identifies the critical tiers, creates the test plan and files.
  • /wjttc-tester โ€” F1-inspired testing expert. Tests your software and writes detailed WJTTC reports with findings and recommendations.

Both are merged into the official Anthropic skills registry (PR #190).

The Philosophy

"We are a service to the army of free devs!"

โ€” wolfejam

WJTTC exists because testing should be accessible. Championship standards shouldn't require enterprise budgets. If you're building MCP servers โ€” or any software where reliability matters โ€” you deserve the same tools that built the FAF ecosystem.

Free to certify. Free to self-host. Free to put in your CI pipeline. The Trophy ๐Ÿ† is yours to earn. Big Orange ๐ŸŠ is harder โ€” but the path is open to everyone.

Links