mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
Renzo Beux
957cdffa7b
Integration rather than unit, because what is being proved is that nothing reaches the global exception filters. registerTools is called outside the transport's try block, and mcp-transport.service.ts states that every response there is written by hand and nothing may be thrown, so a registry-level unit test cannot show it. MCP-P15: a contributed tool that takes a built-in's name is skipped, the built-in is the one still listed, and the session serves normally. MCP-P16: a source that throws costs its tools and nothing else, where it would previously have been a 500 on every /mcp initialize. MCP-P17: a contributed tool call writes the same mcp.tool_call audit row as a built-in, which is the whole reason the source hangs off McpAttachOptions rather than the host calling registerTool itself. MCP-P18 came out of writing the others: the first draft of MCP-P17 minted a trips:read token and got no audit row, because the declarative access marker had correctly hidden the tool. That is worth pinning. mintOauthToken takes scopes now, and rpcResult parses the SSE frame the transport answers with.