max_verify_signature
Verify MAX initData, requestContact phone hashes, or contact hashes locally and get clear reasons when signature checks fail due to wrong formulas, double decoding, or stale auth_date.
Instructions
Verify a MAX signature locally: mini-app initData (two-step HMAC), requestContact phone hash, or the hash of a contact shared through a request_contact button. Explains why a check failed (wrong formula, double decoding, stale auth_date). Available only when the server runs on your machine.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"kind": "<kind>"
},
"name": "max_verify_signature"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hash | No | phone/contact: the hash to check | |
| kind | Yes | init_data — mini-app launch data; phone — Bridge requestContact() result; contact — contact attachment from a request_contact button | |
| lang | No | Answer language: 'en' English, 'ru' Russian. Pick the user's language; default ru (or XONTA_MAX_LANG) | |
| phone | No | ||
| user_id | No | phone: MAX user id | |
| vcf_info | No | contact: vcf_info exactly as received, JSON-decoded | |
| auth_date | No | phone: authDate from requestContact() | |
| bot_token | No | Bot token; defaults to MAX_BOT_TOKEN from the environment | |
| init_data | No | init_data: raw window.WebApp.initData string | |
| max_age_seconds | No | init_data freshness window |