AIsa Web Search & Research

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

Web search and page extraction across several independent search providers.

The publisher's own server: AIsa Agent Mail

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant web search and page extraction across several independent search providers.

What you can do
Search the web through multiple independent search providers and compare their results. Extract the content of web pages so the assistant can read and work with them. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Useful when an assistant needs current web results or the text of specific pages, and when you want results drawn from more than one search provider rather than a single source.
Requirements
A remote streamable HTTP endpoint at the provider's hosted address; no local package or runtime is needed. Authentication is by OAuth and is required, so the user must sign in and authorize access. Network access is required.
Before you install
Access is tied to an OAuth account with the provider, so review what the authorization grants before signing in. Search queries and requested page addresses are sent to the provider and to the underlying search providers, so avoid submitting sensitive material.

Installation

In SourceWeft

  1. Open AIsa Web Search & Research 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%2Fweb-search/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-web-search-research": {
      "type": "http",
      "url": "https://mcp.aisa.one/search/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