Why does osFoundry make Codex CLI poll the cursor for every resource instead of pushing changes?
If a client wants to know if anything has changed, the osFoundry's MCP server just gives it that. It was run from the same Mac, without a token: $ uv run --with tiktoken --with jsonschema python3 watch_sim.py == Part 1: live wire, 8 calls each, ms == initialize HTTP 200 median 414.7 p90 757.8 tools/list HTTP 200 median 606.8 p90 716.7 resources/subscribe HTTP 200 median 450.6 p90 550.2 GET (stream) HTTP…
osFoundry's MCP server was tested with a client, revealing limited functionality. The server provides minimal information, and most push channels are closed. A read-only tool, `poll_resource_events`, is available, allowing clients to resume from an event sequence for granted channels. The client uses a sequence cursor, tracking integers for each resource, to poll the server.
Rate-limit headers indicate 2000 requests per 61 seconds. The client discovers pollable resources through `list_granted_resources` and `list_project_resources` calls.
Written by urgent.news from Dev.to's report — not a translation of it. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
