MCP Server

TGGET Niche Research

            io.tgget/niche-research
        

Marketing & Advertising Search & Research Public & reachable MCP 2025-11-25

What this MCP does

Researches app and SaaS niches using demand, competitor, app-store, advertising, and community data, with reports and recurring monitoring.

compare_research

Compare Research

Puts two to five finished niche scans side by side to help choose between ideas. `items` are the niches with their numbers, the report's positioning and napkin economics, and `wins`: in how many rows the niche holds the better value. `rows` are the ranked measures (verdict, demand, trend, cost per click, weak search results, competitor sites, App Store apps, fresh community signals) with the value of every niche and `best`, the indexes of the items that hold the better value; `better` says which way is better (max or min), null when the row is shown but not ranked. Demand and cost per click are not ranked across different markets (`mixed_markets`). The marks are computed from numbers, not written by a language model. Every scan needs a finished report. `share_url` is a read-only link to this comparison that works without signing in: give it to the person only when they want to share the comparison, it shows the numbers and the conclusions of their researches to whoever holds it.

Read only

Input schema

{'type': 'object', 'required': ['ids'], 'properties': {'ids': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Two to five ids of finished niche scans (or of their reports), as listed by list_research.'}}}

follow_niche

Follow Niche

Starts following the niche of a finished scan that has a report: the scan becomes the first measurement and the niche is scanned anew every month, with a digest of what changed sent to the account. Monthly checks do not spend researches; the plan limits how many niches are followed (FREE 1, Starter 2, Pro 10). Following a niche that is already followed returns its project.

Input schema

{'type': 'object', 'required': ['research_id'], 'properties': {'research_id': {'type': 'string', 'description': 'Id of a finished niche scan, or of its report.'}}}

get_project

Get Project

Returns a followed niche with the history of its checks, newest first: the first measurement (`baseline`) and the monthly checks, each with its numbers, what changed since the previous check and the id of the research it came from. Pass that `research_id` to get_report to read the fresh report of a check. Changes are computed from numbers and lists, not written by a language model.

Read only

Input schema

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Project id listed by list_projects.'}}}

get_report

Get Report

Returns the final niche report of a finished scan (or the report research itself) as Markdown: verdict, what product to build (customer pains with evidence and severity, positioning, MVP with the pain each feature relieves, platform, monetization, competitor matrix), napkin economics (price hypothesis, acquisition cost from the cost per click in paid search, revenue per customer, whether it adds up, assumptions), SEO plan for the site (clusters, pages with title/H1/description, content plan, FAQ), ASO for App Store and Google Play, name options with domain and App Store availability, landing page draft, distribution channels by type with a first step, effort and priority, validation steps and risks. Pass format "json" for structured data (keys: verdict, product, economics, seo, aso, names, landing, channels, validation, risks).

Read only

Input schema

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Id of the scan research (its latest report is returned) or of the report itself.'}, 'format': {'enum': ['markdown', 'json'], 'type': 'string', 'description': 'markdown (default) for reading, json for structured fields.'}}}

get_research

Get Research

Returns the current state and findings of a research by id: status, headline numbers, ranked candidate phrases, competitor overview, child researches (sub-topics, competitor checks, signals) with their ids, and skipped stages. Call repeatedly until status is completed and pending is 0.

Read only

Input schema

{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'Research id returned by start_research or listed by list_research.'}}}

list_projects

List Projects

Lists the niches the account follows. A followed niche (a project) is scanned anew once a month and compared with its previous check. For each project: status, whether the plan serves it, the date of the next check, the latest numbers (verdict, demand, cost per click, competitor sites, App Store, community signals) and what changed at the latest monthly check, as structured `changes` and as `digest` lines of text. Also returns how many niches the plan follows.

Read only

Input schema

{'type': 'object', 'properties': {'limit': {'type': 'integer', 'description': 'How many projects to return, 1-50 (default 20).'}}}

list_research

List Research

Lists the researches the account started itself, newest first: niche scans of a phrase and descriptions of an idea, without the checks they spawned. Use it to find the id of an earlier research before get_research, get_report, compare_research or follow_niche, or to see what is still running. Each item has `id`, `kind`, `phrase`, `status` (queued, running, completed, failed), `mode`, `created_at`, `url` of its page and `total_count`: monthly searches of the phrase, null for a description. `quota` tells how many researches the plan has left. Reads only; spends nothing.

Read only

Input schema

{'type': 'object', 'properties': {'limit': {'type': 'integer', 'maximum': 50, 'minimum': 1, 'description': 'How many researches to return, from 1 to 50. Default 10.'}}}

run_signal

Run Signal

Adds one check to a finished research and returns the id of the new child research. Use it when the scan skipped a stage, when a person asks about one phrase in particular, or to rebuild the report after new checks. A niche scan already runs the usual checks by itself, so this tool is for what is missing. Checks added this way are free: they do not spend researches of the plan. Checks of a demand research (`kind`): - `competitors`: who holds the search results for a phrase of the research; pass the phrase in `phrase`. - `dynamics`: two years of demand history. - `appstore`: App Store apps for the phrase with ratings and freshness. - `wiki`, `radar`, `youtube`: public interest and community signals. - `paid`: paid search for the phrase and its strongest candidates: volume, advertiser competition, cost per click. - `insight`: a summary of the findings written by the language model. - `report`: the final niche report, written anew from the current data; needs a finished niche scan. Checks of a child research: - `fingerprint`: product sites found by a competitors check, with pricing and app links; the parent is that competitors check. - `reviews`: recent App Store reviews of the leaders; the parent is an App Store research. - `insight` also accepts a competitors check as the parent. The parent must be completed and belong to the account. The check runs in the background: poll get_research with the returned `id` every 20-30 seconds until `status` is `completed`. `insight` and `report` are rebuilt at most once an hour.

Input schema

{'type': 'object', 'required': ['id', 'kind'], 'properties': {'id': {'type': 'string', 'description': 'Id of the completed research the check is added to, as returned by start_research, get_research or list_research.'}, 'kind': {'enum': ['competitors', 'dynamics', 'appstore', 'wiki', 'radar', 'youtube', 'paid', 'fingerprint', 'reviews', 'insight', 'report'], 'type': 'string', 'description': 'Which check to add. competitors, dynamics, appstore, wiki, radar, youtube, paid and report need a demand research as the parent; fingerprint a competitors check; reviews an App Store research; insight a demand research or a competitors check.'}, 'locale': {'enum': ['en'], 'type': 'string', 'description': 'Only for insight and report: language of the text. Defaults to the language the research was started with, then to the language of the account.'}, 'phrase': {'type': 'string', 'description': 'Only for competitors: the phrase whose search results are checked, usually one of the candidate phrases of the parent. Defaults to the phrase of the parent. Ignored by the other checks.'}}}

start_research

Start Research

Starts a niche research from a short search phrase or a plain-language description of an app or service idea. A phrase is scanned directly (demand, sub-topics, competitors, signals); a description is first turned into real search queries, the best one is then scanned automatically. Returns the research id to poll with get_research. Counts as one research of the plan allowance, whether the data comes from the sources or from the shared cache.

Input schema

{'type': 'object', 'required': ['text'], 'properties': {'deep': {'type': 'boolean', 'description': 'Deeper scan with more sub-topics and competitor checks. Available on plans that include it (Pro) and to administrators; counted as two researches.'}, 'text': {'type': 'string', 'description': 'Search phrase (e.g. "expense tracker") or a description of the idea in your own words, up to 400 characters.'}, 'locale': {'enum': ['en'], 'type': 'string', 'description': 'Language of the conclusions and the final report. Defaults to the interface language of the account. Texts meant for the site and the stores are always written in the language of the market.'}}}

update_project

Update Project

Pauses a followed niche (`paused`: no monthly checks, its place in the plan is freed), follows it again (`active`, needs a free place in the plan) or stops following it (`deleted`: the project with its checks and digests is removed for good, the researches stay in the history). Ask the person before deleting.

Destructive

Input schema

{'type': 'object', 'required': ['id', 'status'], 'properties': {'id': {'type': 'string', 'description': 'Project id listed by list_projects.'}, 'status': {'enum': ['active', 'paused', 'deleted'], 'type': 'string', 'description': 'active, paused or deleted.'}}}

Added

                            update_project
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            follow_niche
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            get_project
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            list_projects
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            compare_research
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            run_signal
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            list_research
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            get_report
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            get_research
                        

Sept. 30, 2026, 2:40 a.m.

Added

                            start_research
                        

Sept. 30, 2026, 2:40 a.m.

Server details

Version

1.0.1

Transport

Streamable HTTP

Tools

Latency

1956 ms

Last scan

Oct. 2, 2026, 2:40 a.m.

First seen

Sept. 30, 2026, 2:19 a.m.

Endpoint

https://tgget.io/mcp

Recent scans

Success

Oct. 2, 2026, 2:40 a.m.

Success

Sept. 30, 2026, 2:40 a.m.

TGGET Niche Research

What this MCP does

Tools

Recent tool changes

Similar MCP servers

Heista

rankparse-mcp

VarynForge

AfterLaunch: the agentic growth marketing engine

sonar

Prowlo — Reddit & X for AI agents

AgentSEO

NanoTools