Limy

ai.limyPublished by limy.aiOfficial publisherv1.0.0Updated Oct 24, 2026

AI search visibility: brand mentions, citations, rankings, competitors and top cited sources.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Limy is a remote MCP server that lets an assistant check AI search visibility: brand mentions, citations, rankings, competitors and top cited sources.

What you can do
Report brand mentions and citations in AI search results, so you can see how a brand is referenced by assistants and answer engines. Review rankings and top cited sources to understand which pages and domains get surfaced. Compare competitors on the same visibility signals. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want to track or audit how a brand, site or competitor appears in AI-generated search answers and which sources are cited, rather than in classic search rankings.
Requirements
A remote MCP endpoint at mcp.limy.ai over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared. A Limy account is presumably needed to authorize, and network access to the endpoint is required.
Before you install
Access is granted through OAuth, so review the scopes and permissions requested during authorization. Queries about brands, competitors and cited sources are sent to Limy's service, a third party. No write, payment or secret-handling behavior is documented.

Installation

In SourceWeft

  1. Open Limy 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/ai.limy%2Flimy/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": {
    "limy": {
      "type": "http",
      "url": "https://mcp.limy.ai/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

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.