mcp-website-traffic-rank-estimator
Related Servers
Alternatives to mcp-website-traffic-rank-estimator
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Trustpilot Reputation Enricher actor on Apify. Resolve a company domain to its Trustpilot rating, review count and claimed status.1206 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Company Contact Details Extractor actor on Apify. Find a company contact page and extract role emails, a phone number and a postal address.1103 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Ecommerce Platform Profiler actor on Apify. Detect the ecommerce platform, payment providers and catalogue size behind a storefront.195 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs GitHub Organization Signal Scanner actor on Apify. Resolve a company domain to its GitHub organization with repo, language and activity signals.194 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs Reddit Brand Presence and Mention Monitor actor on Apify. Resolve a company domain to its subreddit and sample public mentions of the brand.197 npmMIT
- AlicenseAqualityAmaintenanceMCP server for the Mamba Labs X Twitter Brand Presence Mapper actor on Apify. Resolve a company domain to its X handle, profile URL and follower metrics.1106 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so no misselection is possible. Its purpose is stated precisely and even disambiguates itself from a common confusion (ranks vs. visit counts).
The single tool uses a clear snake_case verb_noun pattern (estimate_website_traffic_rank) that matches the server name. No competing conventions exist to conflict with it.
One tool is defensible for a deliberately narrow, single-operation microservice (fetch a rank for a domain). It is slightly thin in that there is no batch or multi-domain variant, which would be natural for research use.
The single operation returns everything the stated domain requires: rank, observation date, band, trend, and an explicit not_found outcome, with read-only scope acknowledged. The only gap is bulk/batch lookup for comparing many domains at once.