Mcp Website Traffic Rank Estimator

com.mambabuiltPublished by mambabuilt.comv1.2.1Updated Nov 7, 2026

Get a research grade Tranco popularity rank and trend for any company domain.

The publisher's own server: Rank Fast

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Returns a Tranco popularity rank, band and trend for a company domain via an Apify actor, as one flat row.

What you can do
  • Look up a company domain's Tranco popularity rank, with the date of that rank and an honest band from top_1k through beyond_1m
  • Read whether the domain has been rising, falling or stable over roughly forty daily observations
  • Optionally query Cloudflare Radar and Chrome UX Report as extra sources when you supply your own keys
  • Flag rows against a minimum rank threshold and return one flat, join-ready row per company
When to use it
Useful when you need a quick, dated popularity signal for a list of company domains, for example to filter or prioritize accounts in a spreadsheet or enrichment workflow. It is not a traffic measurement tool, so it does not suit anyone who needs visit or session counts.
Requirements
Runs locally as an npm package over stdio, so it needs Node.js 18 or newer. Requires an Apify account and an APIFY_TOKEN environment variable; the lookup runs on Apify and is billed there. Optional Cloudflare API token and Google API key are needed only for the Radar and CrUX sources.
Before you install
Every lookup consumes Apify credits billed to your own account, including not_found results; a max_charge_usd cap can limit spend per call. The APIFY_TOKEN is a secret, and optional Cloudflare and Google keys are passed as tool inputs. Results are ranks, not traffic, and many B2B domains return not_found. Successful lookups are cached for seven days unless skipCache is set.

Installation

In SourceWeft

  1. Open Mcp Website Traffic Rank Estimator 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

Website Traffic Rank Estimator MCP Server

[Glama score] [MCP Registry] [npm version] [npm downloads] [license] [mcpservers.org]

[Website Traffic Rank Estimator MCP server]

An MCP server that returns a research grade Tranco popularity rank and trend for any company domain. It wraps the Mamba Labs Website Traffic Rank Estimator actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

What it does

Give it a company domain and it returns that domain's position on the public Tranco list, the date of that position, a band from top_1k through beyond_1m, and whether the domain has been rising, falling or stable over roughly forty daily observations. One flat row per company.

These are ranks, not traffic. A Tranco rank does not convert to visits, sessions or a monthly number, and this tool will never return a visit count. A lower rank number is better, so the trend is given in words rather than as a signed number. Most B2B domains are not on the list at all and return not_found, which is normal rather than disqualifying. Cloudflare Radar and Chrome UX Report are available as extra sources with your own free keys, and a source you did not supply a key for reports skipped rather than not_found, because nobody looked.

All of the lookup runs on Apify. This package is a thin client that calls the actor and hands back the result unchanged.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

json
{  "mcpServers": {    "mamba-website-traffic-rank-estimator": {      "command": "npx",      "args": ["-y", "@mambalabsdev/mcp-website-traffic-rank-estimator"],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The estimate_website_traffic_rank tool will be available.

Prerequisites

  • Node.js 18 or newer
  • An Apify account with an API token
  • Optional: your own Cloudflare API token, free at dash.cloudflare.com, if you want the Radar source
  • Optional: your own Google API key with the Chrome UX Report API enabled, free at console.cloud.google.com, if you want the CrUX source

Example prompts

  • "What is the Tranco rank for stripe.com, and is it rising or falling?"
  • "Give me the popularity band for this domain and skip the trend."
  • "Rank these domains and flag the ones inside the top 100,000."
  • "Look up figma.com on Tranco and Cloudflare Radar. Here is my Cloudflare token."

Inputs

  • company_domain (optional): bare company domain, for example stripe.com. This is the lookup key and the join key for every other actor in the fleet.
  • company_name (optional): carried through to the output row for joining. Rank lookup is keyed on the domain alone, so the name does not change the answer.
  • sources (optional): which rank sources to query. One of tranco, tranco_radar, tranco_crux or all. Tranco is free and needs no key. Cloudflare Radar and Chrome UX Report each need your own free key, and a source you did not supply a key for reports skipped rather than not found.
  • includeTrend (optional): when true (the default) the rank history Tranco already returns is used to say whether the domain is rising, falling or stable. It costs nothing extra, because the history arrives in the same response.
  • minRank (optional): one of none, 1000, 10000, 100000 or 1000000. It sets rank_meets_threshold on the row, so you can filter a list to established sites without writing the comparison yourself. It never drops a row and never changes the rank returned.
  • cloudflareApiToken (optional): your own Cloudflare API token, free to create at dash.cloudflare.com. Used only when sources includes Radar.
  • cruxApiKey (optional): your own Google API key with the Chrome UX Report API enabled, free at console.cloud.google.com. Used only when sources includes CrUX.
  • skipCache (optional): when false (the default) a successful lookup is cached for seven days and reused. Set true to force a fresh fetch.
  • max_charge_usd (optional): spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged.

Output

The tool returns the actor's flat JSON row for the company, with 20 snake_case fields and no nested objects. tranco_rank comes with tranco_rank_date, because a rank without a date has no shelf life. rank_band gives an honest band rather than false precision, rank_trend is a word, and radar_status and crux_status say whether those sources ran. See the Apify Store page for the full output schema.

Example output

json
{  "degraded": false,  "degradation_reason": null,  "company_domain": "stripe.com",  "company_name": "Stripe",  "tranco_rank": 238,  "tranco_rank_date": "2026-08-21",  "rank_band": "top_1k",  "rank_trend": "stable",  "rank_change": 1,  "rank_observations": 40,  "rank_meets_threshold": null,  "radar_rank": null,  "radar_bucket": null,  "radar_status": "skipped",  "crux_has_data": null,  "crux_lcp_p75_ms": null,  "crux_status": "skipped",  "coverage": 0.67,  "fetch_status": "ok",  "run_date": "2026-08-22T19:23:52.998Z"}

Features

  • Tranco popularity rank for any company domain, with the date of that rank
  • Trend over roughly forty daily observations, given as rising, falling or stable
  • An honest band such as top_1k, rather than false precision
  • Optional Cloudflare Radar and Chrome UX Report sources with your own keys
  • Never returns a visit count, because a rank is not traffic
  • 20 flat snake_case fields, one row per company

Pricing

You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:

EventPrice per event (USD)Fires when
apify-actor-start$0.00005Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
company-checked$0.0025 on the Free plan, down to $0.00175 on higher Apify plansOnce per company for which the rank lookup completed and a non degraded row was produced, whether or not anything was found. A not_found row fires this event, because looking and finding nothing is a real answer and it is the work you asked for. A degraded row, where the lookup could not run at all, fires nothing.
rank-resolved$0.002 on the Free plan, down to $0.0014 on higher Apify plansOnce per company where a numeric rank was returned by at least one source and banded. Does not fire when the domain is absent from every source queried, which is a real answer and is covered by the check event.

The actor's Apify page carries the current prices. Running this server consumes Apify credits.

Full actor documentation

This server is a thin client and holds no lookup logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:

https://apify.com/mambalabs/website-traffic-rank-estimator


Mamba Labs GTM Suite

This server is one of the Mamba Labs GTM Suite MCP servers. Every actor in the suite takes a domain or a company and returns one flat row, so they stack in the same Clay table without reshaping anything. The actor behind this server is the Website Traffic Rank Estimator, immutable Apify actor ID GnOFUzlNVIoXgeJjH.

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Source: README.md at commit 6c3b075

Tools

1

estimate_website_traffic_rank

Estimate Website Traffic Rank

Return a research grade popularity RANK for a company domain from the public Tranco list, with the date of that rank, an honest band (top_1k through beyond_1m) and a rising, falling or stable trend over roughly forty daily observations. Returns one flat Clay ready row. THESE ARE RANKS, NOT TRAFFIC: a rank does not convert to visits and this tool will never return a visit count. A lower rank number is better, so the trend is given in words rather than as a signed number. Most B2B domains are not on the list at all and return not_found, which is normal rather than disqualifying. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

ParametersminRanksourcesskipCachecruxApiKeycompany_nameincludeTrendcompany_domainmax_charge_usdcloudflareApiToken

Version history

5
  1. v1.2.1LatestNov 5, 2026
  2. v1.2.0Oct 16, 2026
  3. v1.1.1Oct 6, 2026
  4. v1.1.0Oct 6, 2026
  5. v1.0.0Sep 16, 2026

Score

90% 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
  • 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Rank integrations