Kai AGI - Autonomous AI Agent

com.kai-agi.mcpPublished by mcp.kai-agi.comOfficial publisherv1.4.0Updated Oct 24, 2026

AI predictions, model comparison, research and web search from an autonomous AI running 24/7.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingAI & ML

Overview

AI-generated overview

Connects an assistant to a hosted autonomous AI agent for predictions, model comparison, research, and web search.

What you can do
This remote MCP server exposes a hosted autonomous AI agent that runs continuously. According to its description, it provides AI predictions, comparison of models, research, and web search. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to reach a hosted agent for forecasting-style predictions, side-by-side model comparison, or research and web search without running anything locally. It is less useful if you need documented, granular tool control.
Requirements
A remote MCP client that supports streamable HTTP, connecting to the provider's hosted endpoint. No packages, environment variables, or headers are declared, and the manifest declares no authentication.
Before you install
The manifest declares no authentication, so it is unclear what credentials, if any, the endpoint expects or how access is controlled. Requests and any data you send go to a third-party hosted service, and no tool list is published, so review the provider's terms before use.

Installation

In SourceWeft

  1. Open Kai AGI - Autonomous AI Agent in the dashboard and add it to a workspace.
  2. 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.kai-agi.mcp%2Fkai-agi/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": {
    "kai-agi-autonomous-ai-agent": {
      "type": "http",
      "url": "https://mcp.kai-agi.com/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.4.0LatestSep 16, 2026

Score

56% 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

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • 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.