Aim

com.startaimingPublished by startaiming.comOfficial publisherv1.0.0Updated Oct 24, 2026

Market knowledge layer for AI agents: competitors, opinions and regulations shaping your market.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that gives an assistant a market knowledge layer covering competitors, opinions and regulations.

What you can do
Aim is a hosted MCP endpoint that supplies market knowledge to AI agents. According to its registry description, it covers competitors, opinions and regulations that shape a market. No tool list is published, so the exact operations the assistant can call are not documented here.
When to use it
Consider it when an assistant needs market context — competitive landscape, public opinion or regulatory material — while doing research or business analysis. Because the tool set is undocumented, evaluate it against your own use case before relying on it.
Requirements
A remote streamable HTTP endpoint at Authentication is required and uses OAuth, so the user must complete an OAuth sign-in; no environment variables or headers are declared. Network access to the provider's endpoint is needed.
Before you install
The server is third-party and hosted remotely, so queries and any context you send go to that provider. OAuth grants it access under the scopes you approve, so review those before authorizing. No tool list is published, so what it can read or change is not verifiable from the listing.

Installation

In SourceWeft

  1. Open Aim 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/com.startaiming%2Faim/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": {
    "aim": {
      "type": "http",
      "url": "https://mcp.startaiming.com/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.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 listed15 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.