_ registry / mcp streamable-http · checked 1h ago

tgden

https://tgden.com

Registry code: ef02efdf367ef851

api record

Live Telegram intelligence from tgden.com — the open catalog of what exists ON Telegram. Unlike other Telegram MCP servers, this one needs NO Telegram account, no API credentials and no login: it answers questions about public channels, group chats and bots that the user does not already belong to. Search 1.8M+ catalogued channels, 456k+ group chats and 228k+ bots with subscriber counts, categories and trust scores; full-text search over classified marketplace listings from the AE·TR·TH·VN·US·RU storefronts; get the best channels for any category. telegram_demand is the weekly index of real…

endpoint
https://tgden.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tgden live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is tgden free to use?
Yes — the hub reached it with no key and no payment.
What tools does tgden have?
9 tools: search_posts, fetch, search, best_channels_by_category, search_telegram, channel_stats, market_listings, market_stats, ….
Is tgden safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.1%· all time 99.1%

latency
186ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 425 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
_ what it is for
used for
  • search public telegram channels
  • get telegram channel stats
  • search telegram posts
  • find top channels by category
takes → gives
text → data
tools
6 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
3 open 6 never probed 3 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • market_listings reads open 15h ago

    Fresh classified listings extracted from Telegram groups across the OTC network — Thailand (th), UAE (ae), Turkey (tr), Vietnam (vn), USA (us), Russia (ru): rent, sale, services, jobs, exchange. Filter by country and listing type.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "type": {
          "enum": [
            "rent",
            "sale",
            "service",
            "job",
            "exchange",
            "wanted"
          ],
          "type": "string",
          "description": "Listing type filter ('wanted' = demand: сниму/куплю/ищу, any kind)"
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "country": {
          "enum": [
            "th",
            "ae",
            "tr",
            "vn",
            "us",
            "ru"
          ],
          "type": "string",
          "description": "OTC country code"
        }
      }
    }
    arguments 35 lines
  • market_stats reads open 15h ago

    Listing totals by country and type for the OTC marketplace (th·ae·tr·vn·us·ru).

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • telegram_demand open 15h ago

    Live weekly index of REAL buyer requests posted in public Telegram group chats — what people are looking for / asking for in a country right now. Use it for questions like 'what are people looking for in Telegram in <country>' or 'is there demand for <service> in <city>'. Ads, sellers, bots and mass mailings are excluded, so every number is actual demand from real people, counted per weekly index. Pass `topic` in the asker's own words (any language), `country` as an ISO-2 code, and optionally `query` to also get recent example requests (anonymised: contact details and links to the message are redacted).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "query": {
          "type": "string",
          "description": "Optional phrase — also returns recent example requests (contacts redacted)"
        },
        "topic": {
          "type": "string",
          "description": "What to look for, in the asker's own words, any language (e.g. 'недвижимость', 'rent')"
        },
        "country": {
          "type": "string",
          "description": "ISO-2 country code (e.g. 'ae', 'th')"
        }
      }
    }
    arguments 17 lines
  • search_posts reads unknown never probed

    Full-text search over marketplace listings published on tgden's public Telegram storefronts across Thailand, UAE, Turkey, Vietnam, USA and Russia: what sellers offer and what people seek, with price, place and date. Returns listing snippets with dates. For Telegram channels use search_telegram; for what people ask for in chats use telegram_demand.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "query": {
          "type": "string",
          "description": "Search query"
        }
      }
    }
    arguments 18 lines
  • fetch unknown 8h ago

    Read one result of `search` by its id as a document: title, description, audience size, categories and the tgden.com page

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Id of a `search` result, e.g. 'channel:durov'"
        }
      }
    }
    arguments 12 lines
  • search unknown 8h ago

    Search the tgden Telegram catalog (channels, group chats, bots). ChatGPT deep-research compatible; for counts, categories and trust scores use search_telegram

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Search query, any language"
        }
      }
    }
    arguments 12 lines
  • best_channels_by_category reads unknown 11h ago

    Top Telegram channels ranked by subscribers for a given category. Use this when someone asks 'best telegram channels for [topic]' or 'top channels about [subject]'. Returns channel name, @username, subscriber count, language and description.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "category": {
          "type": "string",
          "description": "Category slug: crypto, news, tech, ai, finance, entertainment, gaming, marketing, education, sports, music, politics, business, food, travel, health, science, movies, anime, books"
        }
      }
    }
    arguments 18 lines
  • search_telegram reads unknown 11h ago

    Full-text search over the tgden catalog (1.8M+ channels, 456k+ group chats, 228k+ bots) with subscriber/member counts, categories and trust scores. Needs no Telegram account — this is the public catalog, so it finds communities the user has NOT joined. Use type to restrict to one entity kind.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "enum": [
            "all",
            "channel",
            "chat",
            "bot"
          ],
          "type": "string",
          "description": "Entity kind filter (default all)"
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "query": {
          "type": "string",
          "description": "Search query, any language"
        }
      }
    }
    arguments 28 lines
  • channel_stats reads unknown 11h ago

    Full record for one channel by @username: subscribers, category, language, trust score, description.

    mcp-tool

    {
      "type": "object",
      "required": [
        "username"
      ],
      "properties": {
        "username": {
          "type": "string",
          "description": "Channel @username (with or without @)"
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ef02efdf367ef851.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ef02efdf367ef851/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ef02efdf367ef851/badge.svg)](https://brick.blue/agent/ef02efdf367ef851?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.