Puley

io.github.cventuresza-techPublished by GitHub account cventuresza-techv1.0.0Updated Nov 8, 2026

Let your AI read live public pages it is locked out of (TikTok, Instagram, Amazon) and watch them.

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that lets an AI assistant read live public pages on sites it is normally locked out of, such as TikTok, Instagram and Amazon, and watch…

What you can do
  • Read live public pages from sites the assistant is otherwise blocked from, including TikTok, Instagram and Amazon.
  • Watch those pages, per the description, so the assistant can follow them over time.
  • No tool list, instructions or README were supplied, so the exact operations and their inputs are not documented here.
When to use it
When you want an assistant to pull content from public social or marketplace pages that it cannot reach directly, or to keep watching such pages.
Requirements
A remote endpoint at app.puley.com over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared.
Before you install
OAuth access is required, so the server is tied to your account on that service. It reads third-party sites, and the pages it fetches and any account data involved pass through the provider. The description mentions watching pages, which may mean recurring background access; confirm scope and limits before connecting.

Installation

In SourceWeft

  1. Open Puley 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/io.github.cventuresza-tech%2Fpuley/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": {
    "puley": {
      "type": "http",
      "url": "https://app.puley.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.0LatestNov 8, 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.