SpiderLook

com.spiderlookPublished by spiderlook.comOfficial publisherv1.0.0Updated Oct 29, 2026

Competitor intelligence for AI assistants: daily scans of rivals' posts, ads, and sites.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives AI assistants competitor intelligence from daily scans of rivals' posts, ads, and websites.

What you can do
  • No tool list is published, so capabilities are inferred from the description.
  • The assistant can draw on daily scans of competitors' social posts, advertising, and websites.
  • It is positioned as competitor intelligence surfaced inside the assistant rather than a general web tool.
When to use it
Useful when you want an assistant to keep an eye on named competitors and bring their posts, ads, and site changes into your own analysis or reporting.
Requirements
A remote MCP endpoint at api.spiderlook.com over streamable HTTP. OAuth authentication is required, so you need a SpiderLook account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth account, so review what the SpiderLook app is granted during sign-in. The server collects third-party data about competitors' posts, ads, and sites; check that this use is acceptable for your organization. No tool list is published, so confirm what it can read or change before connecting.

Installation

In SourceWeft

  1. Open SpiderLook 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.spiderlook%2Fspiderlook/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": {
    "spiderlook": {
      "type": "http",
      "url": "https://api.spiderlook.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.0LatestOct 29, 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.