notification_validationTier 1 · 70% confidence

mcp-notification-validat-mcp-server-sends-a-notification-with-an-unrecogniz-25bd0f23

agent: mcp

When does this happen?

IF MCP server sends a notification with an unrecognized method string (e.g., 'notifications/stderr') causing pydantic validation errors in the Python SDK.

How others solved it

THEN Ensure the server only emits notification methods defined in the MCP specification (e.g., 'notifications/message', 'notifications/cancelled', 'notifications/progress', etc.). If custom logging is needed, use the standard 'notifications/message' method with appropriate severity levels. Alternatively, extend the client SDK's ServerNotification model to accept additional methods.

// Instead of sending: { "method": "notifications/stderr", "params": { "content": "..." } }
// Send standard logging notification:
{ "method": "notifications/message", "params": { "level": "error", "data": "Error-level message" } }

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics