looktwice-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOOKTWICE_API_KEY | Yes | Your LookTwice API key from the dashboard. | |
| LOOKTWICE_BASE_URL | No | Base URL for the LookTwice API. | https://api.looktwice.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| email_checkA | Validate an email address: syntax, MX records, disposable-domain, role-account, and free-provider signals. Does not probe the mailbox; mailbox_status is always not_checked. Costs 2 LookTwice API units. |
| vat_checkA | Validate an EU VAT number against the official European Commission VIES service. Returns validity at request time, registered name/address when the member state provides them, and request evidence. Costs 1 LookTwice API unit. |
| iban_checkA | Validate an IBAN's country structure, expected length, and MOD-97 checksum, and extract the public bank identifier. Does not verify that the account exists or who owns it. Costs 1 LookTwice API unit. |
| domain_checkA | Check a registrable domain's DNS, MX, TLS certificate, and RDAP registration state. Free within a daily fair-use quota. |
| cpsc_recall_matchA | Match one product against U.S. CPSC recalls and Product Safety Warnings using brand, model, or UPC plus the product title. Returns evidence-backed candidates with official notice links. A result is a screening candidate, not a safety or compliance decision. Costs 3 LookTwice API units. |
| credits_balanceA | Show the current LookTwice workspace credit balance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct entity type—email, IBAN, VAT, domain, product recall, and credits—so there is no overlap or ambiguity in purpose. An agent can clearly differentiate them without confusion.
Most tools follow a consistent [entity]_check pattern (email_check, iban_check, vat_check, domain_check), but cpsc_recall_match and credits_balance deviate from this verb convention. The naming is still mostly predictable and readable.
With six tools, the set is well-scoped for a validation/lookup server. Each tool serves a specific, justified function without redundancy or excessive specialization.
The set covers the main validation types a user would expect (email, IBAN, VAT, domain, product recall) and includes a balance check for the API. Minor gaps exist, such as phone or IP validation, but these are not critical to the core purpose.