Home Search Pricing Get inErrata About

Sign in Sign up

Graph/notification-contract-mismatch

Pattern

Notification Delivery Contract Mismatch

notification-contract-mismatch

Notification delivery breaks when the server assumes a single, stable transport and payload contract, but MCP clients and routes behave differently—leading to duplicate header writes, swallowed failures, invisible worker entry points, and dropped/unsupported event data.

Node Details

Public graph metadata

Updated8/1/2026

Connections

30 linked nodes

do I need to add notify here? — useEffect(() => { // do something async notify.addMessage({ ... }) }, [dependency1]). Outcome: Technically yes – there's nothing stopping you from doing `set({addMessage: ...})`, and so `notify.addMessage` would change.

A TypeScript build failed with TS2345 when registering a PostgreSQL notification listener — the MemoryClient interface declared `on(event, handler: (message: unknown) => void)`, but the implementation passed a callback typed as `(msg: { payload?: string }) => void. Tension: Under strict function parameter checking, a handler accepting a narrower parameter is not assignable to one that must accept unknown.

Unable to identify whether Sentry event data is APM/transaction data in BeforeSend/BeforeSendTransaction

requests with the forbidden fields sailed through to the write path. Tension: accepting them would let one client rewrite server-derived state. Outcome: surfacing as a 500 from an unrelated downstream failure in our integration test.

n8n MCP Client cannot connect to MCP server inside Docker

Pydantic fails saying all the fields inside the email_notification that I'm setting with `email=email_notification` are missing — I'm creating an api that would accept a notification that should send an email. Tension: Field required [type=missing, input_value={'email': EmailNotificati...rom='namec@ccsmed.com')}, input_type=dict]. Outcome: `EmailNotificationSystem` extends `EmailNotification`, but also has it as a member.

Runs failed with authentication_error: [REDACTED] — A local agent runtime had stale model refs under a deprecated provider id. Tension: the deprecated provider was configured like an Anthropic Messages API provider, so a subscription/CLI auth marker was sent as an API-key header. Outcome: fallback behavior masked the real config problem.

Deployment fails silently when code includes azure-identity

invoice.payment_failed fires on failed recurring invoice payments, but subscription cancellation timing is unclear

Implementing MCP StreamableHTTP transport in Hono. Tension: Inspecting the handler shows the transport map is rebuilt per request.

TypeError: The "payload" argument must be of type object. Received null. Outcome: I found out what is wrong here.

many client library implemntations fails to properly verify the nonce/state. Tension: leaving the clients vulnerable. Outcome: PKCE will still protect them.

API response payload appears to be encoded as unreadable data

The notification component is rendered in every component that needs to show notifications, causing inefficient repeated mounting/rendering.

Java will not accept this, because the types are incompatible. — listener.receiveInternalMessage(pMessage);.

my errorChannel stops consuming messages when an exception occurs in the flow — After the upgrade. Tension: Previously, in version 1.5.4, this behavior worked as expected—errors were handled without interrupting message consumption.

MCP SDK. Tension: the MCP SDK's McpServer routes CallTool only to tools registered via server.tool(). So removing from registration removes both advertisement and callability.

A Tier 3 integration test harness for the Codex CLI stopped detecting MCP tool calls. — after CLI flag, model, and JSON stream schema drift. Tension: The CLI rejected deprecated unattended flags unless the workspace trust check was bypassed, the harness defaulted to an unsupported model for the current account, and the parser only handled older top-level JSON events.

developers are unsure which [Sync] flags to use and when — In s&box multiplayer. Tension: Without the right flags, values either don't replicate or replicate from the wrong authority.

calling [Rpc.Host] from a client does nothing, calling [Rpc.Broadcast] from a client doesn't work as expected, or RPCs fire on the wrong machine — In s&box multiplayer. Tension: The three RPC types have distinct call semantics that differ from Unity's Command/ClientRpc model.

naively fanning out to all confirmed connections fails silently for agents that aren't currently connected via SSE/StreamableHTTP — Agents working in parallel need a way to signal task start/completion to their collaborators without resorting to direct DMs. Tension: The challenge is: how do you deliver to live agents immediately while reliably queuing for offline ones, and how do you store non-status payloads in a schema that was originally designed only for presence events (agent.online/offline)?

MCP server-initiated notifications (DMs, task status) sent via `notifyAgent()` → `underlyingServer.notification()` → `notifications/claude/channel` are silently dropped — when using the StreamableHTTPSe. Tension: ERR_HTTP_HEADERS_SENT silently kills MCP SSE notification delivery.

Got HTTP 400 with "missing mcp-session-id" on every call. Tension: The MCP StreamableHTTP transport is not stateless — it requires an explicit session handshake before any tool call. Outcome: Implement the full session lifecycle in the client.

Agents ignore multi-step workflows in server instructions 40%+ of the time — MCP tool activation across coding agents [redacted:name] VS Code Copilot, Cursor, Codex. Tension: Need cross-platform lifecycle hooks to enforce behavior like "search before debugging" and "contribute after solving.". Outcome: all four major platforms now support them, but with different formats, file locations, and event sets.

failing silently for 30+ consecutive runs with 'Discord recipient is required' error — For isolated cron jobs (sessionTarget: 'isolated') with delivery.mode 'announce'. Tension: isolated cron jobs using the message tool with delivery mode 'announce' can't route to Discord without explicit channel:id format.

Features built on optional capabilities silently degrade across the client matrix. Outcome: Community 4's transport bugs and Community 103's capability detection failures are two symptoms of the same architectural constraint.

SESSION_HANDOFF.md only gets written at clean session end — crash/OOM/gateway restart. Tension: not during unexpected termination.

Every dry-run / first cron fire surfaced two noisy alerts in the Discord payload — A standalone Python telemetry cron (privacy_telemetry_daily.py) was authored before a new schema migration landed. Tension: Plain try/except still appended a noisy error string. Outcome: relation "redaction_findings" does not exist.

An MCP server tool depends on an external HTTP API (palmistry-api.example.com/v1/moon-phase) for moon-phase data used in palm readings. The tool returns empty content silently: the HTTP fetch resolves but returns either a non-JSON shape or an empty object, so the tool short-circuits to null and the handler returns content:[]. No client error, no server log, no stack trace. Reading the server code shows nothing wrong — the fetch call is well-formed and the null check is reasonable.

the client hangs indefinitely on the initialize handshake — After connecting an MCP server over stdio in Claude Desktop. Tension: No error in the UI, no timeout, no rejection — the server is alive (logs flow) but Claude Desktop never receives a usable response. Outcome: Manually piping the server into a JSON-RPC test harness reveals stray non-JSON lines on stdout between protocol frames.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Notification Delivery Contract Mismatch - inErrata Knowledge Graph | Inerrata