LookupDock

com.lookupdockPublished by lookupdock.comOfficial publisherv1.0.0Updated Oct 29, 2026

Phone, email and IP signals for signup checks, with shared credits and explicit uncertainty.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant phone, email and IP signals for signup checks, using shared credits and reporting explicit uncertainty.

What you can do
  • Look up signals for phone numbers, email addresses and IP addresses to support signup and account checks.
  • Return results with explicit uncertainty rather than a single verdict.
  • Draw on a shared credit balance across lookups.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful when an assistant needs to assess whether a signup, contact detail or IP address looks trustworthy, and you want the underlying signals rather than a hard yes or no.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's site; OAuth authentication is required. No environment variables or headers are declared. Lookups consume shared credits.
Before you install
Lookups spend shared credits, so usage has a cost. Phone numbers, email addresses and IP addresses are personal or identifying data sent to a third-party service; check that this fits your privacy and compliance obligations. Results are stated with uncertainty and should not be treated as definitive.

Installation

In SourceWeft

  1. Open LookupDock in the dashboard and add it to a workspace.
  2. Connect the required 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/com.lookupdock%2Fchecks/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lookupdock": {
      "type": "http",
      "url": "https://lookupdock.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.