Undesired and confusing logging

Bug description

Starting Spring Boot with Spring AI with 1 @MCPTool annotation gives some unnecessary WARN and INFO messages.

Different buckets of log issues.

These warns are out of my control since I didn't do anything else other than add 1 @MCPTool annotation. These warns should be a "warning" to the framework developers, not us.

2025-10-21T22:00:35.245Z  WARN 79769 --- [...] [  restartedMain] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.ai.mcp.server.common.autoconfigure.annotations.McpServerAnnotationScannerAutoConfiguration' of type [org.springframework.ai.mcp.server.common.autoconfigure.annotations.McpServerAnnotationScannerAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [serverAnnotatedMethodBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-10-21T22:00:35.245Z  WARN 79769 --- [[...] [  restartedMain] trationDelegate$BeanPostProcessorChecker : Bean 'serverAnnotatedBeanRegistry' of type [org.springframework.ai.mcp.server.common.autoconfigure.annotations.McpServerAnnotationScannerAutoConfiguration$ServerMcpAnnotatedBeans] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [serverAnnotatedMethodBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
2025-10-21T22:00:35.246Z  WARN 79769 --- [[...] [  restartedMain] trationDelegate$BeanPostProcessorChecker : Bean 'spring.ai.mcp.server.annotation-scanner-org.springframework.ai.mcp.server.common.autoconfigure.annotations.McpServerAnnotationScannerProperties' of type [org.springframework.ai.mcp.server.common.autoconfigure.annotations.McpServerAnnotationScannerProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [serverAnnotatedMethodBeanPostProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

These below should not be WARN. I don't have them because I don't need them. I shouldn't have to suppress WARN manually.

2025-10-21T22:00:36.114Z  WARN 79769 --- [[...] [  restartedMain] s.m.p.r.SyncStatelessMcpResourceProvider : No resource methods found in the provided resource objects: []
2025-10-21T22:00:36.115Z  WARN 79769 --- [[...] [  restartedMain] s.m.p.r.SyncStatelessMcpResourceProvider : No resource methods found in the provided resource objects: []
2025-10-21T22:00:36.115Z  WARN 79769 --- [[...] [  restartedMain] o.s.m.p.p.SyncStatelessMcpPromptProvider : No prompt methods found in the provided prompt objects: []
2025-10-21T22:00:36.115Z  WARN 79769 --- [[...] [  restartedMain] s.m.p.c.SyncStatelessMcpCompleteProvider : No complete methods found in the provided complete objects: []

Steps to reproduce

Add 1 @MCPTool annotation and start any project.

Expected behavior

Resolve the first bucket of warnings and remove the second bucket of warnings.

In a 3rd bucket, these errors are out of my control. In this case I'm using LM studio to call the MCP Server and the framework is not happy with itself. Expected Behavior would be for the framework to be more tolerant of Client requests and don't dump warnings into our logs which we can't do anything about.

2025-10-21T22:18:30.107Z  INFO 79769 --- [...] [nio-9900-exec-4] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:18:30.144Z  WARN 79769 --- [...] [nio-9900-exec-6] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:19:31.913Z  INFO 79769 --- [...] [io-9900-exec-10] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:19:31.940Z  WARN 79769 --- [...] [nio-9900-exec-2] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:19:44.660Z  INFO 79769 --- [...] [nio-9900-exec-5] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:19:44.686Z  WARN 79769 --- [...] [nio-9900-exec-7] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:19:44.746Z  WARN 79769 --- [...] [nio-9900-exec-3] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:21:15.403Z  INFO 79769 --- [...] [nio-9900-exec-5] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:21:15.442Z  WARN 79769 --- [...] [nio-9900-exec-7] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:21:15.894Z  WARN 79769 --- [...] [nio-9900-exec-3] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:21:23.913Z  WARN 79769 --- [...] [nio-9900-exec-7] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:21:23.938Z  WARN 79769 --- [...] [io-9900-exec-10] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:21:45.359Z  INFO 79769 --- [...] [nio-9900-exec-4] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:21:45.394Z  WARN 79769 --- [...] [nio-9900-exec-3] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:21:45.455Z  WARN 79769 --- [...] [io-9900-exec-10] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:21:49.500Z  WARN 79769 --- [...] [nio-9900-exec-3] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:21:49.525Z  WARN 79769 --- [...] [nio-9900-exec-8] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:22:35.810Z  INFO 79769 --- [...] [io-9900-exec-10] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:22:35.835Z  WARN 79769 --- [...] [nio-9900-exec-2] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:22:35.981Z  WARN 79769 --- [...] [nio-9900-exec-8] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:22:39.439Z  WARN 79769 --- [...] [nio-9900-exec-2] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:22:53.300Z  WARN 79769 --- [...] [nio-9900-exec-6] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:22:55.141Z  WARN 79769 --- [...] [io-9900-exec-10] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:22:55.163Z  WARN 79769 --- [...] [nio-9900-exec-3] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:24:21.666Z  INFO 79769 --- [...] [nio-9900-exec-6] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:24:21.694Z  WARN 79769 --- [...] [nio-9900-exec-8] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:24:21.844Z  WARN 79769 --- [...] [nio-9900-exec-3] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:24:22.932Z  WARN 79769 --- [...] [nio-9900-exec-8] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:26:14.579Z  INFO 79769 --- [...] [nio-9900-exec-4] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:26:14.621Z  WARN 79769 --- [...] [nio-9900-exec-5] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:26:14.676Z  WARN 79769 --- [...] [nio-9900-exec-8] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:26:16.239Z  WARN 79769 --- [...] [nio-9900-exec-5] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:26:16.266Z  WARN 79769 --- [...] [nio-9900-exec-9] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:27:10.686Z  INFO 79769 --- [...] [nio-9900-exec-8] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:27:10.717Z  WARN 79769 --- [...] [nio-9900-exec-4] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:27:10.789Z  WARN 79769 --- [...] [nio-9900-exec-9] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:27:13.161Z  WARN 79769 --- [...] [nio-9900-exec-5] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:27:13.186Z  WARN 79769 --- [...] [nio-9900-exec-9] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:28:17.135Z  INFO 79769 --- [...] [nio-9900-exec-7] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:28:17.257Z  WARN 79769 --- [...] [nio-9900-exec-4] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:28:17.316Z  WARN 79769 --- [...] [nio-9900-exec-9] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:28:20.606Z  WARN 79769 --- [...] [nio-9900-exec-5] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:28:20.633Z  WARN 79769 --- [...] [nio-9900-exec-9] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:29:10.371Z  INFO 79769 --- [...] [nio-9900-exec-8] i.m.server.McpStatelessAsyncServer       : Client initialize request - Protocol: 2025-06-18, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null, elicitation=null], Info: Implementation[name=lmstudio-mcp-server-session, title=null, version=1.0.0]
2025-10-21T22:29:10.397Z  WARN 79769 --- [...] [nio-9900-exec-4] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/initialized
2025-10-21T22:29:10.449Z  WARN 79769 --- [...] [nio-9900-exec-9] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:29:12.709Z  WARN 79769 --- [...] [nio-9900-exec-5] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled
2025-10-21T22:29:12.825Z  WARN 79769 --- [...] [nio-9900-exec-9] i.m.s.DefaultMcpStatelessServerHandler   : Missing handler for notification type: notifications/cancelled