Mcp Us Business Data

io.github.avabuildsdataPublished by GitHub account avabuildsdatav1.9.240Updated Oct 24, 2026

Official-source US business, permit, and WHOIS evidence via read-only MCP tools.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server giving assistants read-only access to official-source US business, permit and WHOIS evidence.

What you can do
Look up US business records from official sources through read-only tools. Retrieve permit evidence tied to businesses. Query WHOIS registration data as supporting evidence. All access is read-only, so the assistant gathers and cites records rather than changing them.
When to use it
Useful when an assistant needs to verify a US company, check permits or registration details, or gather WHOIS evidence for due diligence, compliance checks or research where official sources matter.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP; no local package or runtime is needed. Authentication is required via OAuth, so the user must complete an OAuth sign-in, and network access is needed.
Before you install
Access requires an OAuth sign-in, so an account is involved; review what the OAuth grant authorizes before connecting. The tools are described as read-only, but records are pulled from third-party official sources, so results may be incomplete or out of date and should be checked against the source.

Installation

In SourceWeft

  1. Open Mcp Us Business Data 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/io.github.avabuildsdata%2Fmcp-us-business-data/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": {
    "us-business-data": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=pink_comic/us-business-entity-search,pink_comic/building-permits-construction-leads,pink_comic/whois-domain-lookup"
    }
  }
}

README

This repository has no README.

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.9.240LatestSep 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.