Inspect the published contracts
Register with your host
Host SDKs use different registration APIs and JSON Schema adapters. The following is intentionally framework-neutral:aura_* tool identifiers. They are stable wire
values even when the host displays Praxa branding.
Preserve the executor boundary
The registration callback should be the only layer that translates an MCP tool call into a Gateway request. It must:- validate the tool input against the published schema;
- interpolate only the declared
pathArgument; - remove the path field from the JSON body when the route expects it in the URL;
- attach a short-lived delegated token with the exact
requiredScope; - preserve one idempotency key for an exact mutation replay;
- map bounded Gateway problems to
isError: truetool results; - return a redacted structured result that the host can verify.