NetBird
verify_verifications_check
Check a passcode a recipient submitted. Identify the verification by the same `to` recipient used to start it; no verification ID is needed. A wrong or expired code returns HTTP 200 with `success: false` and a `reason` (for example `incorrect_code` or `expired`). A verification that has already reached a final state is no longer checkable and returns 404, as does a missing verification; malformed input or rate limiting is also an error status.
Remote bird/mcp
Remote (network-hosted)
Other tools also called verify_verifications_check?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"to": {
"type": [
"null",
"object"
],
"properties": {
"email": {
"type": [
"null",
"string"
]
},
"phone_number": {
"type": [
"null",
"string"
]
}
},
"description": "The recipient to verify. Provide an email, a phone_number, or both; at least one is required. The addresses also identify the verification: a check must supply exactly the set used on the create call, so a verification created with both addresses is not found by either one alone.",
"additionalProperties": false
},
"code": {
"type": "string",
"description": "The passcode the recipient received. Passcodes are numeric; submit the digits exactly as delivered. An incorrect value is a normal 200 outcome with success: false. It does not return an error."
},
"idempotency_key": {
"type": "string",
"description": "Client-supplied deduplication key; a retry with the same key replays the original result instead of acting twice."
}
}
}