Aiso

io.github.BenUsernamePublished by GitHub account BenUsernamev1.0.0Updated Oct 25, 2026

Inspect AI brand visibility, tracked prompts, competitors, citations and search fan-outs.

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Aiso is a remote MCP server that lets an assistant inspect AI brand visibility, tracked prompts, competitors, citations and search fan-outs.

What you can do
Inspect AI brand visibility across tracked prompts and search fan-outs, including which competitors appear and which citations are surfaced. Discover project IDs with list_projects, then query project-scoped data for a chosen project.
When to use it
Useful when you want an assistant to review how a brand shows up in AI answers, compare it against competitors, or look at tracked prompts and citations without opening the Aiso dashboard.
Requirements
Remote endpoint at app.getaiso.com over streamable HTTP. OAuth authentication is required, plus an Aiso API key sent in the x-api-key header and a project UUID in the x-aiso-project-id header for project-scoped tools.
Before you install
Requires an Aiso account and a personal API key; treat the key as a secret. Project-scoped tools act on the project identified by the x-aiso-project-id header, so confirm the ID before querying. Brand, prompt and citation data is sent to Aiso's service.

Installation

In SourceWeft

  1. Open Aiso 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.BenUsername%2Faiso/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": {
    "aiso": {
      "type": "http",
      "url": "https://app.getaiso.com/api/v1/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 25, 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.