Web reader and Telegram search for agents

io.github.CyberPunk11147Published by GitHub account CyberPunk11147v1.6.0Updated Nov 6, 2026

Read any web page and search public Telegram channels, groups and bots. No API key, pay per call.

VerifiedSTDIODesktop onlyWeb Search & ScrapingCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant read arbitrary web pages and search public Telegram channels, groups and bots, with pay-per-call billing instead of an API key.

What you can do
  • Read the contents of any web page the assistant is pointed at
  • Search public Telegram channels, groups and bots
  • Surface a 402 payment invoice to the agent when a call is unpaid, so its own x402 client can pay and retry
When to use it
Useful when an assistant needs to pull page content or look up public Telegram discussions without registering for an API key, and when the caller is set up to handle x402 pay-per-call payments.
Requirements
Runs as a local stdio process from the published container image, so a container runtime is needed. It calls a hosted service at a default URL that can be overridden with AWA_BASE_URL, so network access is required. No account or API key is declared; an optional AWA_X_PAYMENT secret can carry an x402 payment header.
Before you install
Calls are billed per use through x402, so the assistant can spend money; without AWA_X_PAYMENT the server returns a 402 invoice for the agent to pay. Page content and search queries are sent to the third-party service at the configured base URL. Pointing AWA_BASE_URL at an untrusted host would send requests and any payment header there.

Installation

In SourceWeft

  1. Open Web reader and Telegram search for agents in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

6
  1. v1.6.0LatestNov 6, 2026
  2. v1.5.0Oct 10, 2026
  3. v1.4.0Oct 9, 2026
  4. v1.3.0Oct 9, 2026
  5. v1.2.1Oct 7, 2026
  6. v1.1.0Sep 16, 2026

Score

35% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts