Network
Parse a raw HTTP request or curl command, estimate client↔server clock skew from the response Date header (NTP-style midpoint formula), inspect timestamp credentials (X-Amz-Date, x-ms-date, X-Timestamp, JWT iat/nbf), replay with ±skew offsets and diff the results against real tolerance windows (AWS SigV4 ±15 min, Azure, OAuth, JWT leeway).
Call this tool from your code in three languages.
curl -X POST 'https://api.elysiatools.com/en/api/tools/request-replay-clock-skew-correction-distributed-systems' \
-H 'Content-Type: application/json' \
-d '{"rawRequest":"POST /v1/orders HTTP/1.1\nHost: api.example.com\nX-Amz-Date: 20260101T000000Z\nAuthorization: AWS4-HMAC-SHA256 Credential=AKIA.../20260101/us-east-1/execute-api/aws4_request, SignedHeaders=host;x-amz-date, Signature=abc123\nContent-Type: application/json\n\n{\"sku\": \"A-1\", \"qty\": 2}","mode":"analyze","capturedServerDate":"Thu, 01 Jan 2026 00:16:00 GMT","capturedReceivedAt":"Thu, 01 Jan 2026 00:00:10 GMT","offsets":"e.g. -950,0 or leave empty for the auto ±skew sweep","timeoutMs":10000}'Send a POST request with your inputs as JSON. File parameters require a separate upload first.
POST https://api.elysiatools.com/en/api/tools/request-replay-clock-skew-correction-distributed-systems| Name | Type | Required | Description |
|---|---|---|---|
| rawRequest | textarea | Yes | — |
| mode | select | Yes | — |
| capturedServerDate | text | No | — |
| capturedReceivedAt | text | No | — |
| offsets | text | No | — |
| timeoutMs | number | No | — |
HTML result
{
"result": "<div>Processed HTML content</div>",
"error": "Error message (optional)",
"message": "Notification message (optional)",
"metadata": {
"key": "value"
}
}Add this tool to your Model Context Protocol server so AI agents can list and call it.
Add this block to your MCP client configuration:
{
"mcpServers": {
"elysiatools-request-replay-clock-skew-correction-distributed-systems": {
"name": "request-replay-clock-skew-correction-distributed-systems",
"description": "Parse a raw HTTP request or curl command, estimate client↔server clock skew from the response Date header (NTP-style midpoint formula), inspect timestamp credentials (X-Amz-Date, x-ms-date, X-Timestamp, JWT iat/nbf), replay with ±skew offsets and diff the results against real tolerance windows (AWS SigV4 ±15 min, Azure, OAuth, JWT leeway).",
"baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=request-replay-clock-skew-correction-distributed-systems",
"command": "",
"args": [],
"env": {},
"isActive": true,
"type": "sse"
}
}
}After connecting to the SSE endpoint, list the exposed tools:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}Invoke the tool by its id, passing arguments built from its parameters:
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "request-replay-clock-skew-correction-distributed-systems",
"arguments": {
"rawRequest": "POST /v1/orders HTTP/1.1\nHost: api.example.com\nX-Amz-Date: 20260101T000000Z\nAuthorization: AWS4-HMAC-SHA256 Credential=AKIA.../20260101/us-east-1/execute-api/aws4_request, SignedHeaders=host;x-amz-date, Signature=abc123\nContent-Type: application/json\n\n{\"sku\": \"A-1\", \"qty\": 2}",
"mode": "analyze",
"capturedServerDate": "Thu, 01 Jan 2026 00:16:00 GMT",
"capturedReceivedAt": "Thu, 01 Jan 2026 00:00:10 GMT",
"offsets": "e.g. -950,0 or leave empty for the auto ±skew sweep",
"timeoutMs": 10000
}
}
}Questions or issues? Contact [email protected]