FetchLayer

dev.fetchlayerPublished by fetchlayer.devOfficial publisherv1.0.0Updated Nov 4, 2026

226 tools for Reddit, X, TikTok, Instagram, YouTube, reviews, ads, shopping and search data

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote MCP endpoint offering 226 tools for pulling social media, review, ads, shopping and search data from Reddit, X, TikTok, Instagram and YouTube.

What you can do
  • Retrieve Reddit, X, TikTok, Instagram and YouTube data through a large tool set
  • Collect reviews, advertising and shopping data
  • Run search-data queries across these sources
  • No individual tools are documented in the supplied listing, so exact operations are unclear
When to use it
Useful when an assistant needs social media, review, ad or shopping data from the named platforms for research, monitoring or analysis, and you are willing to connect a hosted third-party service via OAuth.
Requirements
A remote streamable HTTP endpoint at mcp.fetchlayer.dev; no local package or runtime. OAuth authentication is required, so an account with the provider is needed. Network access to the endpoint.
Before you install
OAuth grants the server access under your account; review the scopes requested. Data is fetched from third-party platforms through the provider, so queries and results pass through it. Tool behavior and any write or spend actions are undocumented here, and the provider may meter or charge for usage.

Installation

In SourceWeft

  1. Open FetchLayer 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/dev.fetchlayer%2Ffetchlayer/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": {
    "fetchlayer": {
      "type": "http",
      "url": "https://mcp.fetchlayer.dev/"
    }
  }
}

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.0LatestNov 4, 2026

Score

83% 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
  • 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.