Aim MCP Server

by startaiming Your server? Claim it

answering

Aim is answering right now. Last checked 13 min ago.

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

Uptime history 48 days of history

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

122 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Aim every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add aim --transport http https://mcp.startaiming.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "aim": {
      "url": "https://mcp.startaiming.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.aim]
url = "https://mcp.startaiming.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "aim": {
      "url": "https://mcp.startaiming.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "aim": {
      "url": "https://mcp.startaiming.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.startaiming.com/mcp	streamable-http	sign-in	138 ms	13 min ago

Alternatives to Aim

same job, measured the same way

Firekeep

by kapella-hub

Self-hosted operating layer for AI agents: knowledge, continuity, coordination, and governance.

1 608 installs/wk local only

Dyer MD

by srishesh-archik

Access your dyer.md Markdown vault as a knowledge source for AI agents.

29 installs/wk local only

mFlow

by m-flow

Shared task board and knowledge base for AI coding agents

answering

OpenRush

by openrushdata

The Marketing Data Layer for AI Agents - SEO, Search Console, and Analytics

answering

Blck Alpaca Knowledge Base

by blckalpaca

Search Blck Alpaca's knowledge base on SEO, GEO, AI agents and marketing automation.

4 tools answering

Aieph

by aieph

Shared knowledge cache for AI coding agents — reuse an answer once it exists.

1 tools answering

Sekichi

by surp-renz

Knowledge accumulation for AI coding agents. Records decisions, problems, and insights as context.

answering

Central Intelligence

by alekseimarchenko

Persistent memory for AI agents. Store, recall, and share knowledge across sessions.

71 installs/wk local only

Aim — questions

Answers built from our own checks of this server.

Why is there no tool list for Aim?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Aim working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 122 ms. The bar chart above shows every period we have measured.

How do I connect Aim?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Aim?

No API key is involved. Aim answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Aim?

It answers our handshake in 122 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.