Skip to main content
Every error Sumvin returns carries a short code, so an agent or a person can tell one failure from another without parsing prose. This page covers the codes you can actually meet on the paths this documentation covers — the MCP connector and the account setup it depends on. It isn’t the full list Sumvin’s systems use internally.

Reading a code

A code has three parts, and sometimes a fourth: DOMAIN-STATUS-SEQUENCE, then -R if the failure is worth retrying.
  • MCP-401-001 — the area (MCP), the HTTP status it came with (401), and which failure in that area (001). No -R, so it’s terminal: sending the same request again gets the same answer. Something has to change first — the credential, the input, a setting.
  • MCP-429-001-R — ends in -R, so it’s retryable: the same request, sent again after a short wait, can succeed without anything changing. Honour Retry-After when the response carries one, and back off between attempts.
That’s the whole rule, so a client can decide without a lookup table: retry when the code ends in -R, stop otherwise.
A code starting MCP-4 or MCR-4 names something about this specific request (wrong credential, wrong tool, rate limit). The two -503-001 codes above mean the service isn’t configured here — they have no -R, because retrying won’t help until someone sets it up.