The MCP connector limits how many requests it serves in a given window. There are two separate
allowances, and either one can be reached independently:
- Per network address — counted before any agent is identified, so a flood from one address is
capped even before it authenticates.
- Per connected agent — counted after the agent is identified, so several agents sharing a network
address don’t share this allowance, and one agent moving between addresses still has a single
budget.
Both are configured by Sumvin’s operators and can change without notice, so this page doesn’t publish
exact numbers — they aren’t fixed values you can rely on staying the same.
When you’re rate limited
A request over either allowance gets back an HTTP 429 with a Retry-After header, given in seconds.
Wait at least that long before trying again — retrying sooner gets the same refusal.
The two allowances carry different error codes so an agent can tell which one it hit — see
Errors for MCP-429-001-R and MCP-429-002-R.
A 429 on this connector is availability protection, not a judgement about the request. Back off for
the stated time and try again — there’s nothing else to change about the call itself.