MCP Gateway
Feeds category E (MCP gateway).
Starting state from the fast track: Console access and a working API key already exist.
Grade each scenario Pass (2 points), Pass with gaps (1), or Fail (0) against the grading rubric, and carry the subtotal into the summary scorecard.
Scoresheet document
For your convenience, this page can be downloaded as PDF or printed directly. Site navigation is omitted, the scoring table keeps its rows intact with the header repeated on every page, and the Grade and Notes columns leave room for handwriting.
| ID | Scenario | Guide | Grade | Notes |
|---|---|---|---|---|
| 4.1 | Aggregate two or more MCP servers into a profile and connect an MCP client to the single endpoint. Verify: tools from both servers are discoverable and callable through one URL. | Aggregate MCP servers into a profile | ||
| 4.2 | Govern MCP server access, including the OAuth client lifecycle. Verify: a denied server or tool is not reachable from the client. | Govern MCP server access | ||
| 4.3 | Secure MCP secrets and identity. Verify: credentials are not stored in client config, and the end-user identity is visible on the tool call trail. | Secure MCP secrets and identity | ||
| 4.4 | Scope MCP servers and profiles to a project. Verify: another project's client cannot reach the scoped servers. | Scope MCP to a project | ||
| Subtotal | /8 |