LookupLab

io.github.PpiNeaPpLePublished by GitHub account PpiNeaPpLev1.0.0Updated Oct 24, 2026

Phone carrier, email domain, IP network and DNS checks using your LookupLab account.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

LookupLab is a remote MCP server that lets an assistant run phone carrier, email domain, IP network and DNS checks against your LookupLab account.

What you can do
  • Check a phone number for carrier and line type, with optional US/CA caller-name data
  • Verify an email address for syntax, MX records, disposable-domain and role-address indicators
  • Look up approximate IP location and network/provider indicators
  • Inspect a domain's MX, SPF, DMARC or DKIM records and report issues
When to use it
Useful when you need quick contact-data hygiene or deliverability checks inside a chat: validating an email list, sanity-checking a phone number, geolocating an IP, or auditing a domain's mail authentication records. Each check draws on paid LookupLab credits, so it suits occasional verification rather than bulk processing.
Requirements
A remote endpoint at lookuplab.io using Streamable HTTP; no local package. A LookupLab account with credit balance and an API key, supplied as the X-API-Key header or as a Bearer token, or via OAuth sign-in in Claude. Claude Code setups use a LOOKUPLAB_API_KEY environment variable. DKIM checks need a selector.
Before you install
Every tool spends account credits (phone lookups cost 1 to 5 depending on line type and caller name; other checks cost 1), and the balance must cover the maximum charge before a lookup runs. Duplicate calls may charge again unless the client sends a stable Idempotency-Key header. Results are not proof of identity, ownership, consent to contact, deliverability or precise location, and privacy flags may be missing. Only submit data you are authorized to check, and keep the API key out of shared…

Installation

In SourceWeft

  1. Open LookupLab in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.PpiNeaPpLe%2Flookuplab/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lookuplab": {
      "type": "http",
      "url": "https://lookuplab.io/api/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

LookupLab integrations

[M8ven Score]

Phone carrier, email-domain, IP-network and DNS checks through LookupLab.

Find LookupLab on Smithery and in the official MCP Registry.

Claude web and Desktop

  1. Open Customize > Connectors > Add custom connector. Name it LookupLab and use https://lookuplab.io/api/mcp.
  2. Choose Sign in now and Register automatically if Claude shows authentication options. Leave a custom client ID and secret blank.
  3. On LookupLab's consent page, enter your LookupLab key and approve. Enable the connector in your chat. Try: "Check the mail records for example.com."

Your key goes only to LookupLab; Claude receives a revocable OAuth connection. On Team and Enterprise plans, an owner first adds the connector, then each member connects their account. See Claude's connector setup.

Claude Code

Set LOOKUPLAB_API_KEY privately in your environment, then merge claude-code.mcp.json into your project's .mcp.json. Start Claude Code in that project, approve LookupLab when prompted, and check /mcp. Keep the variable reference in the file; never replace it with a real key in a shared repository.

The config uses Claude Code's HTTP transport and environment expansion. Try: "Check the mail records for example.com."

Gemini CLI

Install with gemini extensions install https://github.com/PpiNeaPpLe/lookuplab-integrations. Supply your existing LookupLab API key in the extension's sensitive setting. Gemini stores this setting in its system keychain when available. Never put a key in a chat message.

Other MCP clients

Connect to https://lookuplab.io/api/mcp with Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY in the client's secure connection settings. The server uses Streamable HTTP with JSON responses and no SSE stream.

ChatGPT and Codex

The openai/ directory is the portable plugin package. OAuth needs an exact callback registered by LookupLab before the platform connection can run. This source package is not a claim of directory approval or publication.

Tools and costs

ToolChecksAccount credits
phone_lookupCarrier, line type; optional caller name1 for landline/VoIP/toll-free, 3 mobile/unknown; caller name adds 2
email_verifySyntax, MX and domain indicators1
ip_lookupApproximate location and network1
dns_checkMX, SPF, DMARC or DKIM1

The account needs enough balance for the maximum charge before the lookup runs. Failed/invalid results are not charged. Tools debit credits, so they are marked as operations with side effects. Duplicate calls may charge again unless your client sends a stable Idempotency-Key header for retries.

Data is not proof of a person's identity, ownership, consent to contact, guaranteed email delivery or precise location. Privacy flags can be unavailable. Supply only data you are authorized to check.

Privacy · Terms · Support

Source: README.md at commit 1efa49a

Tools

4

phone_lookup

Check phone carrier and line type

Check a user-provided phone number for carrier and line type. Optional US/CA caller-name data is a carrier listing, not identity verification. Uses existing account credits: 1 for landline/VoIP/toll-free, 3 for mobile or unknown; caller name adds 2. Reserves up to 5 credits before execution. Does not place calls or send messages.

Parametersnumberrequiredcaller_name

email_verify

Check email syntax and domain

Check an email address supplied by the user for syntax, MX records, disposable-domain and role-address indicators. Does not prove mailbox ownership or guarantee delivery. Uses 1 existing account credit for a successful check; does not send email.

Parametersemailrequired

ip_lookup

Check IP location and network

Look up approximate IP location and network/provider indicators for an IP address supplied by the user. IP location is not a person's precise location or identity; privacy flags may be unavailable. Uses 1 existing account credit for a successful check.

Parametersiprequired

dns_check

Inspect email DNS records

Inspect a user-provided domain's MX, SPF, DMARC or DKIM record and report issues. Does not change DNS. DKIM requires a selector. Uses 1 existing account credit for a successful check.

Parameterscheckrequireddomainrequiredselector

Version history

1
  1. v1.0.0LatestOct 12, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.