# MCP Gateway Test Report

Updated: 2026-07-15

## Result

The current MCP Gateway test suite covers direct Gateway sessions, dynamic tool visibility, safe output presentation, and local/public protocol parity.

- Public Workbuddy access uses `GWS_xxx` Gateway sessions.
- The legacy authorization-code binding path has been retired.
- Public and stdio dynamically expose the 7 locally registered tools only when the backend registry enables them.
- `AuthClient` keeps only token refresh/revoke behavior.
- `query_order` retains its legacy response; the other 6 tools use `OutputPresenter` and do not expose internal result keys.

## Latest Result

- Full suite: `369 tests OK`.
- Coverage: `1423 statements / 538 branches / 100.00%`.
- Strict command: `python -m coverage report -m --fail-under=100`.

## Recommended Verification

```powershell
python -m unittest discover -s tests -p "test_*.py" -v
```

## Important Coverage Areas

- Gateway session parsing from header, bearer token, and cookie.
- Redis Gateway session lookup and invalid-session user message.
- Scoped API forwarding with request-level MCP token.
- Local token refresh/revoke compatibility.
- Query tool registration and JSON-RPC routing.
- Safe `headers/rows` presentation, cross-tool value forwarding, fail-closed errors, and `query_order` compatibility.