Compliance and verification with DIDWW MCP#

Use DIDWW MCP to review number-registration requirements, manage supported identities and addresses, upload required documents securely, and submit or review address verifications through a connected MCP client.

Important

The identity and address must represent the actual end user of the phone numbers. The MCP client can explain requirements and validate available information, but it must not decide which person or business should be registered as the end user.

What you can do#

Describe the required result in plain language. When possible, identify the active DIDWW account, country, phone-number type, phone numbers, identity, and address.

Review requirements and records#

Action

What you can request

Review registration requirements

Review the identity type, mandatory fields, address requirements, proof types, document quantities, and other conditions for a supported country and phone-number type.

Review identities

List the personal or business identities available in the active DIDWW account and review their available details and document summary. When a country and phone number type are provided, identify which records are eligible for the applicable requirement and explain any blocking issue.

Review addresses

List addresses associated with the account’s identities and review their verification information. When a country and phone number type are provided, identify which records are eligible for the applicable requirement and explain how an ineligible record can be corrected when remediation is available.

Validate an identity and address

Check whether a selected identity and address satisfy the applicable registration requirement before submitting a verification.

Review address verifications

Review verification statuses and available rejection comments or reasons for submitted address verifications.

Manage identities and addresses#

Action

What you can request

Create an identity

Create a personal or business identity for the actual end user using the fields required by the applicable registration requirement. Check it against the requirement before uploading documents.

Update an identity

Update supported identity fields when information is incomplete or does not satisfy a requirement.

Delete an identity

Permanently delete an eligible identity together with all its addresses, uploaded proof documents, and permanent supporting documents after reviewing the effect and confirming the action.

Create an address

Create an address for an existing identity.

Update an address

Update supported address, postal-code, area, or description information.

Delete an address

Delete an eligible address after reviewing the phone numbers, verifications, and services that may be affected.

Manage supporting documents#

Action

What you can request

Prepare a required-document upload

Create a one-time DIDWW upload link containing the document sections missing from a selected registration requirement.

Upload or replace a specific proof

Create a one-time upload link for selected identity or address proof types, including a replacement for an existing proof.

Check upload status

Check whether a secure upload is pending, completed, or expired.

Delete a stored proof

Delete an eligible proof after reviewing and confirming the effect on related verifications or services.

Submit and review address verifications#

Action

What you can request

Submit an address verification

Submit a verification directly when the selected identity, address, and required proofs are already complete.

Upload documents and submit

Prepare a secure upload that submits the address verification after all required documents have been uploaded successfully.

Review verification status

Review submitted verifications and identify whether they are awaiting review, approved, rejected, or require another action.

Resolve a rejected verification

Review the available rejection information, correct the identity, address, or documents, and prepare a new verification when permitted.

How the verification flow works#

Some phone numbers require end-user verification before they can be activated. Before purchasing a number, ask the MCP client whether registration is required.

When registration is required, the process normally follows this sequence:

  1. Review the requirements for the phone number’s country and type.

  2. Select or create the correct identity and address.

  3. Validate the identity and address against the requirement.

  4. Correct any missing or incompatible information.

  5. Use the secure DIDWW upload page when documents are required.

  6. Submit the address verification.

  7. Review its status and resolve any reported problem.

Requirements depend on the country, phone-number type, end-user type, and selected phone numbers.

A purchased number may remain pending until DIDWW approves the required information. Purchasing the number does not bypass the verification process.

See End-user verification for more information about registration requirements and their effect on number activation.

Choose the correct end user#

  1. Identify the person or business that will actually use the phone numbers.

  2. Ask the MCP client which identity and address records are eligible for the applicable country and phone number type.

  3. Review why any other record is not eligible and whether it can be corrected.

  4. Select the correct end user yourself.

  5. Ask the MCP client to validate the selected records against the registration requirement.

If no suitable record exists, create the correct identity or address rather than using an unrelated record.

Note

An eligible record can still require proof documents. Eligibility means that no blocking identity or address mismatch was found for the selected requirement. It does not mean that the document requirements are complete.

Create an identity#

An identity represents the person or business that will use the regulated phone numbers. For a carrier or reseller, this may be the customer’s own subscriber or end customer rather than the DIDWW account holder.

Before creating an identity:

  1. Review the applicable registration requirement.

  2. Select the required personal or business identity type.

  3. Provide the mandatory identity information returned by the requirement.

  4. Ask the MCP client to check the new identity against the requirement.

A business identity requires a company name. Its first and last name identify the authorized representative of record, not necessarily the person making the request through the MCP client.

Provide only real, verified information. Do not ask the MCP client to invent missing values. When a phone number is included in the identity, enter digits only.

Checking the identity against the requirement during creation can identify missing or incompatible information before the document-upload stage. After creating the identity, provide its required proofs through the secure DIDWW upload page and create the associated address.

Delete an identity#

Deleting an identity permanently removes:

  • the identity

  • all addresses belonging to it

  • all uploaded proof documents

  • all permanent supporting documents

This action cannot be undone and requires DIDWW confirmation.

An identity cannot be deleted when it:

  • is the account’s system identity

  • is assigned to a phone number as its main or porting identity

  • has a new or pending address verification

  • is used by an unfinished emergency calling service

  • is used by an unfinished SMS campaign

When deletion is unavailable, the response identifies the applicable blocker. Resolve the blocker before requesting deletion again.

A user whose access is limited to porting cannot delete an identity that has permanent supporting documents. The appropriate compliance permission is required, as in the DIDWW User Panel.

Upload documents securely#

Important

Do not send identity documents, address proofs, or other supporting files in the AI conversation.

When documents are required, DIDWW provides a separate one-time browser link. The upload page identifies:

  • the purpose of the upload

  • the relevant identity and address

  • the relevant phone numbers, when applicable

  • the documents that must be provided

The link can also be opened on another device using the provided QR option when the MCP client supports it.

Review the information on the DIDWW page before uploading anything. The link is time-limited and cannot be reused after it is completed or expires.

After uploading, return to the MCP client and ask it to check the upload status.

See Privacy and data handling for information about protected data, AI-provider processing, and secure document handling.

Before submitting a verification#

Make sure that:

  • the correct DIDWW account is active

  • the correct end user has been selected

  • the identity type matches the requirement

  • mandatory identity and address fields are complete

  • the address is appropriate for the selected phone numbers

  • all required proofs and supporting documents are available

  • your DIDWW user has the required compliance permission

A verified identity or address does not automatically satisfy every registration requirement. Requirements can differ by country and phone-number type.

Permissions and confirmations#

The MCP client uses the permissions of the DIDWW user who authorized the connection.

DIDWW requires confirmation before destructive actions such as:

  • deleting an identity

  • deleting an address

  • deleting a stored proof

The confirmation preview identifies affected records and known blockers when available.

An identity may not be deleted while it is the account’s system identity, linked to a phone number, used by a new or pending verification, or required by an unfinished emergency calling service or SMS campaign. An address may also be protected by an active verification or service.

Your MCP client may display its own approval request before calling a DIDWW action. This application approval is separate from a DIDWW destructive-action confirmation.

Product requirements#

A compliance request may be unavailable because of:

  • insufficient DIDWW user permissions

  • an incompatible identity or address

  • missing mandatory information

  • missing or incompatible proofs

  • an expired secure upload link

  • a country or phone-number requirement that is not satisfied

  • a pending verification or linked service that prevents deletion

  • phone numbers that require different addresses or requirements

When possible, the response identifies the missing information and the next available action.

Current limitations#

DIDWW MCP does not currently support:

  • selecting the legal end user on the customer’s behalf

  • receiving identity or address documents directly in the AI conversation

  • reusing a completed or expired secure upload link

  • completing number porting document workflows through this compliance flow

Example requests#

Review a registration requirement
Show the number-registration requirements for a personal end user with
a geographic phone number in Germany.
Include mandatory fields and required documents.
Do not create or change anything.
Check registration before purchasing
Check whether end-user registration is required for a geographic phone
number in Berlin, Germany.
Show the applicable identity, address, and document requirements.
Do not purchase anything.
Review available identities and addresses
Show the identities and addresses that are eligible for registering a
geographic phone number in Germany.
For each ineligible record, explain the blocking reason and any available
correction. Do not choose the legal end user or make any changes.
Validate an identity and address
Check whether the selected identity and address satisfy the registration
requirement for +49XXXXXXXX.
Show missing fields, documents, or compatibility problems.
Do not submit a verification.
Prepare a new identity and address
Explain which identity and address fields are required for the actual
end user of +49XXXXXXXX.
Prepare the records using the information I provide.
Wait for my approval before creating them.
Delete an identity
Show the addresses, proof documents, verifications, phone numbers, and
services associated with the selected identity.
Explain anything that prevents deletion and everything that will be
permanently removed.
Do not delete the identity until I confirm the action.
Prepare a required-document upload
Check which documents are missing for registering +49XXXXXXXX.
If documents are required, provide the DIDWW secure upload link.
Do not ask me to send documents in this conversation.
Replace a supporting document
Show the acceptable proof types for the selected identity.
Prepare a secure upload link to replace its current identity proof.
Do not delete any other document.
Submit an address verification
Validate the selected identity and address for +49XXXXXXXX.
If all required information and documents already exist, show the
proposed address verification.
Wait for my approval before submitting it.
Review address-verification status
Show the latest address verification for +49XXXXXXXX.
Include its status and any available rejection information.
Do not make any changes.
Review a pending number
Explain why +49XXXXXXXX is still pending.
Show whether end-user verification is required and the current
verification status.
Do not make any changes.
Review an address before deletion
Show the phone numbers, verifications, and services associated with the
selected address.
Explain the effect of deleting it.
Wait for my confirmation before deleting the address.