AIsa Technologies & Whois

one.aisaPublished by aisa.oneOfficial publisherv1.0.1Updated Oct 24, 2026

What a domain is built on and who owns it: technology detection and whois records.

The publisher's own server: AIsa Agent Mail

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that lets an assistant look up what technology a domain is built on and who owns it via whois records.

What you can do
It provides domain intelligence through a remote endpoint: technology detection showing what a site is built on, and whois lookups returning ownership registration records. The manifest lists no individual tools, so exact tool names and output formats are not documented here. Access is over streamable HTTP at the provider's hosted endpoint.
When to use it
Useful when you need to check the stack behind a website or find registration and ownership details for a domain, for example during research, competitive checks, or due diligence. Not needed if you only require general web search or browsing.
Requirements
A remote MCP client connecting to the provider's hosted endpoint over streamable HTTP. OAuth authentication is required, so you need an account with the provider and must complete its authorization flow. No environment variables or headers are declared.
Before you install
The server is hosted by a third party, so the domains you query are sent to that provider. OAuth grants it access tied to your account; review the scopes requested during authorization. No tools are listed, so confirm what actions it can take before relying on it.

Installation

In SourceWeft

  1. Open AIsa Technologies & Whois 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/one.aisa%2Fseo-domains/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": {
    "aisa-technologies-whois": {
      "type": "http",
      "url": "https://mcp.aisa.one/seo-domains/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.1LatestSep 16, 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.

Other Aisa integrations